> you have to think about service boundaries and granularity correctly. This is the hardest part.. I'd argue that this is almost impossible to do correctly wit

> you have to think about service boundaries and granularity correctly. This is the hardest part.. I'd argue that this is almost impossible to do correctly without significant domain modeling experience.. also microservices by nature make this hard to refactor these boundaries (compared to monoliths where you'd get compile time feedback) I prefer to make a structured monolith first (basically multiple services with isolated data that are squished together into a single deployable) and pull them out only if I really need to... Also helps with keeping ms sprawl under control