This week's book giveaway is in the Cloud/Virtualization forum.
We're giving away four copies of Learning OpenStack Networking: Build a solid foundation in virtual networking technologies for OpenStack-based clouds and have James Denton on-line!
See this thread for details.
Win a copy of Learning OpenStack Networking: Build a solid foundation in virtual networking technologies for OpenStack-based clouds this week in the Cloud/Virtualization forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Knute Snortum
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Ganesh Patekar
  • Stephan van Hulst
  • Pete Letkeman
  • Carey Brown
Bartenders:
  • Tim Holloway
  • Ron McLeod
  • Vijitha Kumara

The Tao of Microservices: Performance aspects  RSS feed

 
Bartender
Posts: 4050
54
Chrome Fedora Hibernate
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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?
 
Author
Ranch Hand
Posts: 31
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!