Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Microservices Design Patterns in .NET
  • Table Of Contents Toc
Microservices Design Patterns in .NET

Microservices Design Patterns in .NET - Second Edition

By : Trevoir Williams
close
close
Microservices Design Patterns in .NET

Microservices Design Patterns in .NET

By: Trevoir Williams

Overview of this book

Are you a developer seeking practical, up-to-date insights into designing scalable and resilient microservices? Microservices Design Patterns in .NET, Second Edition provides a comprehensive exploration of modern microservices using C# 14 and .NET 10. This edition expands on core patterns such as CQRS, event sourcing, and Saga, while introducing advanced concepts such as observability with OpenTelemetry, zero-trust security, and container-based workflows. You’ll explore both synchronous and asynchronous communication, apply domain-driven design to define service boundaries, and manage data consistency using proven persistence strategies. The book also guides you through container hosting, serverless functions, and production-ready deployment pipelines. By the end of this book, you’ll know how to design and deploy secure, maintainable, and resilient microservices that fit perfectly in modern cloud ecosystems. Free with your book: DRM-free PDF version + access to Packt's next-gen Reader*
Table of Contents (24 chapters)
close
close
Lock Free Chapter
1
Understanding Microservices and Design Patterns
9
Database and Storage Design Patterns
12
Resiliency, Security, and Infrastructure Patterns
17
Cloud Development Strategies
22
Index
23
Other Books You May Enjoy

Exploring the Saga pattern

As discussed previously, your microservices application is best implemented using the Database-Per-Service pattern. The major drawback to this pattern choice is that we cannot guarantee that our databases will always remain in sync if one of the operations fails.

We need a mechanism that spans multiple services and can implement transactions across the various data stores, such as a two-phase commit, which requires all data stores to commit or roll back transactions simultaneously. This would be perfect, except that some NoSQL databases and message brokers are incompatible with this model.

Imagine a new patient being registered with our healthcare center. This process will require the patient to provide their information and some essential documents and book an initial appointment, which requires payment. These actions require four different microservices to get involved; thus, four different data stores will be affected.

We can refer to an operation...

CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Microservices Design Patterns in .NET
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist download Download options font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon