1. Monolithic app and VCS mono-repo are orthogonal and can be mixed in different combinations (with different tradeoffs). 2. How about an old way of blocking d

1. Monolithic app and VCS mono-repo are orthogonal and can be mixed in different combinations (with different tradeoffs). 2. How about an old way of blocking deployments less: parts of this monolithic apps developed as libraries with a stable API, a new version of a library released only after its own tests has passed, next you can increment dependency version in the monolith and run integration tests, if they failing you can revert to the old library version and still go ahead with the deployment (if you don't depend on something added in the latest library release). If you depend on this new feature and a component providing it is broken micro-services would not help you. > If you are only a few hundred engineers, monorepo with monolithic deployments and tests work fine. And here lies a very important problem IMHO - many (if not majority) of organizations (which do at least some software development) have less than 100 software developers but the industry best practices (which include micro-service architecture) are defined by FAANG-sized organizations and at least some of these practices are sub-optimal for small shops.