@rails,
By "Make decisions easy to change later", do you mean, 1. Getting the Module structure of the system correct with well defined contracts between them so that they can be changed, updated independently of each other.
Thanks for your inputs.
By "Make decisions easy to change later", do you mean, 1. Getting the Module structure of the system correct with well defined contracts between them so that they can be changed, updated independently of each other.
Thanks for your inputs.
Because of this you should design for change and build a flexible architecture. My goto technique for this is to encapsulate everything regarding this decision into a module and put an interface around it. The interface stays the same, the implementation can adapt. How this interface looks like is not that important. You can build a library, it could be a REST API or some gRPC thing, whatever. So yes, the main idea is to create well defined contracts or interfaces (call them whatever you like), which will be be flexible enough to adapt to different implementations.