After the adoption of a microservice architecture is agreed upon, it is wise to have the following prerequisites in place:
- Requirements become more demanding with a quicker turnaround from development. It requires you to deploy and test as quickly as you can. If it is just a small number of services, then it is not a problem. However, with the number of services going up this could very quickly challenge the existing infrastructure and practices. For example—your Q/A and staging environment may no longer suffice to test the number of builds that are coming back from the development team.
- As the application goes to the public domain, it won't be long before the age-old script of development versus Q/A is played out again. The difference this time is that the business is at stake. So, you need to be prepared to respond quickly in an automated manner to identify the root cause when required.
- With an increasing number of microservices, you will quickly need a way to monitor the functioning and health of the entire system for any possible bottlenecks or issues. Without a means of monitoring the status of the deployed microservices and the resultant business function, it is impossible for any team to take a proactive deployment approach.