When to stop designing microservices

Designing microservices can often feel more like an art than a science. There is lots of general advice available in the domain, but at times this can be too abstract. Let's quickly list some important points:

  • Microservices should not share their databases with another microservice.
  • They should be limited to a number of database tables.
  • We need to make sure we have either built our microservices as stateful or stateless. Alternatively, we can convert stateful microservices to stateless ones by having common databases or filesystems such as shared RDS, AWS, EFS, or NFS-like systems.
  • We should consider all the required inputs for the microservice before writing the microservice code and running the application.
  • The output should be a single source of truth.
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.21.100.34