Microservices

Event-driven architecture

CQRS

(Command Query Responsibility Segregation)

Domain Driven Design

by Eric Evans

I haven't finished it yet...

What I think it is so far?

• Create a knowledge-rich model
• Use ubiquitous language
• Tie your model to your implementation

ubiquitous language

Use the same language with your users that you use in your code

Sounds obvious right?

Too many tokens!

"Audit plans"?

Oh you mean an "assessment progress"!

"Oh, I didn't get why you were doing it that way..."

"...but I thought it was for some technical reason."

Use business jargon, don't hide from it

Why I'm excited about DDD:

• Framework for talking to clients
• Prevent misunderstandings
• Create designs that can change