The thing microservices give is an enforced api boundry. OOP classes tried to do that with public/private but fail because something public for this module is private outside. I've written many classes thinking they were for my module only and then someone discovered and abused it elsewhere. Now their code is tightly coupled to mine in a place I didn't intend to be coupled.
i don't know the answer to this it is just a problem I'm fighting.
i don't know the answer to this it is just a problem I'm fighting.