Wednesday, July 31, 2019

Approach on what pages to move first in a microservices journey

Every microservices journey is different for different organizations based on their core competency. However, few of the basic elements of where to start and where to end are more or less similar. Came across this below diagram on multiple websites which illustrates the typical migration model. Read only pages or static pages with content are much more easier to move to newer platforms especially on cloud services like SaaS than core business components.  



  1. Always try starting with Separating Transactional and Non Transactional Pages
  2. Start separating the Front end and back heavy pages based on functional boundaries
  3. Redirecting heavy traffic pages reduces burden off the monolithic application and also results in possible decommissioning of infrastructure and license cost savings.
  4. Target Read Only pages first especially the once that are business centric and that change very often
  5. Target Product specific pages next 
  6. Target semi transaction pages and pages and that are performance heavy 
  7. Target the Order related pages at last.

No comments:

Post a Comment

Building Microservices by decreasing Entropy and increasing Negentropy - Series Part 5

Microservice’s journey is all about gradually overhaul, every time you make a change you need to keep the system in a better state or the ...