Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Building Microservices with .NET Core

You're reading from   Building Microservices with .NET Core Develop skills in Reactive Microservices, database scaling, Azure Microservices, and more

Arrow left icon
Product type Paperback
Published in Jun 2017
Publisher Packt
ISBN-13 9781785887833
Length 274 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (4):
Arrow left icon
Soumya Mukherjee Soumya Mukherjee
Author Profile Icon Soumya Mukherjee
Soumya Mukherjee
Gaurav Aroraa Gaurav Aroraa
Author Profile Icon Gaurav Aroraa
Gaurav Aroraa
Lalit Kale Lalit Kale
Author Profile Icon Lalit Kale
Lalit Kale
Manish Kanwar Manish Kanwar
Author Profile Icon Manish Kanwar
Manish Kanwar
Arrow right icon
View More author details
Toc

Table of Contents (11) Chapters Close

Preface 1. What Are Microservices? FREE CHAPTER 2. Building Microservices 3. Integration Techniques 4. Testing Strategies 5. Deployment 6. Security 7. Monitoring 8. Scaling 9. Reactive Microservices 10. Creating a Complete Microservice Solution

DDD and its importance for microservices


Domain-Driven Design (DDD) is a methodology and a process of designing complex systems. In this section, we will briefly discuss DDD and how it is important in the context of microservices.

Domain model design

 The main objective of domain design is to understand the exact domain problems and then draft a model that can be written in any set of language/technologies. For example, in our Flix One bookstore application, we need to understand Order Management and Stock Management.

Here are a few characteristics of the domain-driven model:

  • A domain model should focus on a specific business model and not across multiple business models
  • It should be reusable
  • It should be designed in a way that it should be called in the loosely coupled way, unlike the rest of the system
  • It should be designed independently of persistence implementations.
  • It should be pulled out from a project to another location, so it should not be based on any infrastructure framework.

Importance...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at R$50/month. Cancel anytime