CamundaCon spurs our ambitions to deliver scalable, on-demand workflows

  • Sizing the entire monolith codebase first: Taking into account any internal and external dependencies amongst the monolith application.
  • Decision on the number of microservices required: If there are a lot of microservices architecture, it can get complex while if there are too few then it remains a monolith application.
  • Partitioning database first: Data received from the front end, data generated by the system and data exchanged by the backend
  • Categorising functionalities: This includes end-to-end business process and domain specific process
  • Define and assign microservice categories: Types of categories can include business process microservice, data microservice, domain specific microservice.
  • Design the communication for microservices: It’s important to design how each of the microservice communicate with each other using API’s.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
6point6

6point6

Leading with strategy, design and architecture, we connect cloud, data, and cyber to engineer and deliver large-scale, complex transformations.