information hiding is a concept where you don't put information on the interface that are likely to change, thus making your microservice independently deployable and stand alone
-
Information hiding (aka encapsulation aka decoupling): you hide the parts of the application that are most likely to change, thus protecting other parts of the program from extensive modification, if the design decision is changed.
-
Information hiding is the ability to prevent certain aspects of a class or software component from being accessible to its clients (like private variables), thus minimises the blast radius.
-
Information hiding makes your app independently deployable, more modular.
-
Any information (e.g. interface, swagger, function, method, property, object, data structure) that you expose outside of your microservice boundary, an external consumer will make use of that. You try and limit what you expose so that you minimize the affect to your consumer if you ever change the interface to your microservice. O