The term "Microservice Architecture" has sprung up over the last few years to describe a particular way of designing software applications as suites of independently deployable services. (Martin Fowler).

The term MicroServices describes the componentisation of a complex deployment architecture into smaller independent deployable units that can be independently updated and scaled. The source of each component often winds up in its own repository, leading to what is often described as a repository sprawl with loss of visibility across the whole architecture code base and reduced security.

Another popular trend is the return to monorepos, providing a single repository for all components, exactly to counterbalance the draw-backs of the repository sprawl. Monorepos have their own draw-backs, since they force each developer to pull the entire codebase. Come to this talk how you can solve the conundrum and have your cake and eat it.