Walking the wire: Mastering the four decisions in microservices architecture

  • There should be no shared databases. If updates happen only in one microservice, you can use message queues to share data. If updates happen in two services, either merge the two services or use transactions.
  • Handle microservice security by using a token-based approach. It pushes the authentication to the client and does access control at microservice level simplifying dependencies.
  • Handle microservice composition by driving flow from client browser, through orchestration or through a centralised server that runs the workflow.
  • Avoid a spaghetti of dependencies by having a proper & detailed plan of how & when which microservices should call each other. Understand the impact of such an invocation on the overall performance of the system.

Full post here, 9 mins read