> There's a difference between a microservices architecture and putting in services where they make sense. We build mostly monoliths at work but we still split

> There's a difference between a microservices architecture and putting in services where they make sense. We build mostly monoliths at work but we still split things into services where necessary. It seems that your problem has more to do with semantics than with what microservices are. Arguably, the definition of a microservices architecture is "not a monolith", in the sense that it's a distributed system not only with regard to support and infrastructure services but also with regards to business logic.