Forums Register Login

The Tao of Microservices: Performance aspects

+Pie Number of slices to send: Send
Hi Richard,

How would you justify the performance aspects of a system when you move to MS specially when you consider the latency etc..., invoking separate out of process services as opposed to processes running on the same server?
+Pie Number of slices to send: Send
Hi Vijitha,

Microservices do introduce higher latency. The payoff is that you get more flexible development, and can respond to requirements changes more quickly.

In the early stages of a project, latency is not so important, as your focus will be on correct implementation of the business requirements.

Once you reach the later stages, you can assess where the bottlenecks are, and merge services if necessary to avoid network overhead.
This works because, like most things, performance needs are concentrated on a small number of important process pathways, rather than all of them.

Your messaging layer should make this merging possible without changes to business logic code, as the message transport becomes an internal function call.

I discuss this issue in chapter 6.
Be reasonable. You can't destroy everything. Where would you sit? How would you read a tiny ad?
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com


reply
reply
This thread has been viewed 382 times.
Similar Threads
Microservices architectures
Microservices and authorisation (not authentication)
Keep HTTPSession after the user closed their browser
How we design microservice application?
Need for speed
More...

All times above are in ranch (not your local) time.
The current ranch time is
Mar 29, 2024 08:58:17.