User Info
Welcome, Guest. Please login or register.
November 19, 2018, 03:39:13 pm

Login with username, password and session length
Search:     Advanced search
Forum Stats
33209 Posts in 4171 Topics by 5911 Members
Latest Member: AaarSego
Home | Forum | Help | Login | Register
Minesworn  |  Sworn Community  |  General Discussion  |  Striking a balance with microservices?
253 Guests, 0 Users


« previous next »
Pages: [1] | Go Down Print
Author Topic: Striking a balance with microservices?  (Read 13412 times)
Power Noob

Karma: +0/-0

Posts: 59
DnD: True Neutral
PlayStyle: Builder
Politics: Moderate


« on: November 09, 2017, 11:05:36 pm »


Striking this balance requires starting with a business process view of an application. Who uses this, how many slightly different ways might the functions of the application be divided based on worker needs, how often is the application likely to be used, and how critical is it that the application's performance be stellar? But also be aware of the logical length of the workflows the application represents, because it's this factor that limits microservice segmentation.  This structure would not contain a series of microservice "tiles" that fed storefronts from other storefronts or daisy-chained components. These will increase application response time through API delays. That means you'll have to balance the division of applications into small components and the need to chain through many such components to process a single request or transaction.

For More Details

video explainer

Pages: [1] | Go Up Print 
« previous next »

Founded 5/19/2011
SMF 2.0.8 | SMF © 2014, Simple Machines
TinyPortal © 2005-2012
| Theme by nesianstyles | Buttons by Andrea
Page created in 0.038 seconds with 27 queries. (Pretty URLs adds 0.011s, 2q)