Choreography. The microservices ballet [eng]

Презентація доповіді

We’ve been using distributed transactions for decades. However, the advent of the cloud posed a critical design challenge: no more distributed transactions.

How do we design a complex software system made of several components interacting with each other and in apparent need of coordination? It seems that some form of orchestration is mandatory. However, that comes with coupling.

Not all hope is lost. Join Mauro and see how we can design complex systems using choreography techniques to reduce coupling, avoid using distributed transactions, and, still, satisfy business needs.

Mauro Servienti
Particular Software, Solution Architect
  • Solution Architect in Particular Software, the makers of NServiceBus
  • He spends his time helping developers build better .NET systems leveraging Service Oriented Architecture (SOA) principles and message-based architectures
  • Mauro usually writes about technology, but not only on his English blog and his Italian blog
  • Passionate about cycling, swimming, classical dance, and music (and skiing in a previous life)
  • Linkedin, GitHub, Twitter
Увійти
Або поштою
Увійти
Або поштою
Реєстрація через e-mail
Реєстрація через e-mail
Забули пароль?