.NET Fest 2019. Dan Patrascu-Baba. Microservices from the trenches. When buzzwords don’t make your application work

Тема доклада
KYIV 2019
Dan Patrascu-Baba
Microservices from the trenches
.NET CONFERENCE #1 IN UKRAINE

.NET LEVEL UP .NET CONFERENCE #1 IN UKRAINE KYIV 2019
Dan Patrascu-Baba
BIO: Software developer @Amdaris, Founder
@Codewrinkles, Co-organizer @ApexVox
Blog: http://danpatrascu.com
Twitter: @danpdc

.NET LEVEL UP
Agenda
.NET CONFERENCE #1 IN UKRAINE KYIV 2019
• Microservices architecture overview
• The project
• Lessons learned:
Decomposing services
Messaging
The API gateway
• Conclusions

Microservices architecture

.NET LEVEL UP
Possible app architecture

.NET LEVEL UP
Services are…
• small in size
• messaging enabled
• bounded by contexts
• autonomously developed
• independently deployable
• decentralized
• built and released with automated processes

.NET LEVEL UP
Benefits
• Scalability
• Agility
• Availability
• Innovation

.NET LEVEL UP
Drawbacks?
Let's discuss them at the end :)

.NET LEVEL UP
The project
• The customer is a provider of integrated systems
for Contact Centers
• Rich application ecosystem
• Goal: Rebuild the Time and Attendance solution to
meet modern software architecture standards and
business needs
• How? Use Microservices architecture

Lessons learned:
1. Scoping / decomposing services

.NET LEVEL UP
Decomposing models
• By business capability and define services corresponding to business
capabilities
• By DDD bounded contexts
• By verb or use case and define services that are responsible for
particular actions. e.g. a Shipping Service that’s responsible for
shipping complete orders
• By nouns or resources by defining a service that is responsible for all
operations on entities/resources of a given type. e.g. an Account
Service that is responsible for managing user accounts

.NET LEVEL UP
Issues
• How to identify the bounded contexts?
• How to identify business capabilities?
• Which decomposition model is suitable for a given scenario?
• Is it really possible to decompose everything in a meaningful way
following only one model?

DEMO:
Decomposing services

Lessons learned:
2. Messaging

.NET LEVEL UP
Issues
• A microservices architecture is all about communication
• How should services communicate in any given business scenario?
• Should they call each other synchronously?
• Should they communicate via asynchronous messaging?
• What are the pros and cons of the chosen message brokering
technology?

.NET LEVEL UP
Communication patterns
Synchronous Calls if:
• we want to query some data, because a query is not changing any state so we don’t have to
worry about distributed transactions and data consistency across service boundaries
• the call is allowed to fail and we don’t need a sophisticated retry mechanism
Simple Messaging if:
we want to send state-changing commands
• the operation must be performed eventually, even if it fails the first couple times
• we don’t care about potentially complex message structure
Transactional Messaging if:
• we want to send state-changing commands only when the local database transaction has
been successful

.NET LEVEL UP
Message broker concepts
• Producer - User application that sends messages to an exchange.
• Exchange - Pushes messages into queues. Exchange types define what to do
with the message when it’s received, whether. appended to a one queue, to
many queues, or discarded. Example exchange types are direct, topic and
fanout.
• Queue - Each exchange contains a buffer, or queue, that stores messages. A
queue is only bound by the host’s memory & disk limits, it’s essentially a large
message buffer. Many producers can send messages that go to one queue, and
many consumers can try to receive data from one queue.
• Consumer - User application that receives messages.

DEMO:
Messaging infrastructure

Lessons learned:
3. The API gateway

.NET LEVEL UP
What should an API gateway do?
• Proxying
• Service discovery
• Response aggregation
• Header translation
• Protocol translation
• Load balancing
• Authorization
• Rate limiting

.NET LEVEL UP
Available options
• All the major cloud providers offer such services
• Kubernetes has such a functionality
Drawbacks
• Technology debt
• Additional complexity when setting up environments
• Not very flexible

.NET LEVEL UP
A possible solution in the .NET world…
• Meets all discussed requirements
• Easy to configure
• Can be extended with own
functionality

DEMO:
Ocelot

.NET LEVEL UP
Conclusions
• A microservices architecture adds a lot of complexity that we might tend to
oversea in the planning phase
• Are the benefits really outnumbering the complexities?
• A microservices architecture is not only about software architecture, but also
about the organization and how teams are set up

Before deciding on going for a
microservices architecture try to
ask yourself if it’s worth

Questions?

Thank you!

.NET Fest 2019. Dan Patrascu-Baba. Microservices from the trenches. When buzzwords don’t make your application work

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à .NET Fest 2019. Dan Patrascu-Baba. Microservices from the trenches. When buzzwords don’t make your application work

Similaire à .NET Fest 2019. Dan Patrascu-Baba. Microservices from the trenches. When buzzwords don’t make your application work (20)

Plus de NETFest

Plus de NETFest (20)

Dernier

Dernier (20)

.NET Fest 2019. Dan Patrascu-Baba. Microservices from the trenches. When buzzwords don’t make your application work