Monolists

The easiest way to think about an individual service code is rip write anything that you would store in a single codripo night. If it's a single repo, it's probably one team, and it can be tested in isolation as well. Monolists do kind of require their own a principles of operations and monitring,. But then going into how we monitor those a, when an tested right? We can and should do both. The ability to know throuput arrorates latencies on a per service basis, and those are independent. Thereis no reason to muddy those across multiple services. And when you have a production failure, figuring out where that is requires the entire