> But even experienced architects working in familiar domains have great difficulty getting boundaries right at the beginning. By building a monolith first, you

> But even experienced architects working in familiar domains have great difficulty getting boundaries right at the beginning. By building a monolith first, you can figure out what the right boundaries are, before a microservices design brushes a layer of treacle over them. I think this is one of the most important points. Often it takes time to figure out what the right boundaries are. Very rarely do you get it right a priori.