We have just talked about deploying each service individually. Thanks to such an approach, you do not have to push the whole code base at once. I am sure you have had at least one project that was so big that the whole process of delivering it to the production environment was difficult to automate and took really long to finish. In such a scenario, dividing the project into smaller modules can also be beneficial let's say that, in the last month, only one team delivered a new feature; you do not have to go through all your platform tests. What is more, if something is not right after deployment in a part of the system you have not modified, you do not have to bring in another team to investigate ...
Scaling and updating services individually
Get Hands-On Azure for Developers now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
