Replicability or changeability
Innovation and speed are of foremost importance in IT delivery. Microservice boundaries should be identified in such a way that each microservice is easily detachable from the overall system, with minimal cost of rewriting. If part of the system is just an experiment, it should, ideally, be isolated as a microservice.
An organization may develop a recommendation engine or a customer ranking engine as an experiment. If the business value is not realized, then that service should be thrown away, or replaced with another one.
Many organizations follow the startup model, where importance is given to meeting functions and quick delivery. These organizations may not worry too much about the architecture and technologies, ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access