Recently I came to the conclusion, that actually only two issues bothers me in relation to the monolith pattern:
- necessity to pull the whole application:
– extremely sub optimal in case if you need to take care for some tiny feature or a bug
– potential risk of an access to a fragile or confidential part of a code by a programmer who could potentially use it without accordance with our intentions
- resources overload needed to engage even for some tiny requests
- huge scalability issues
But what if…
we build a monolith that consist of specialized modules, being able to operate both as integrated parts of a monolith an at the same time (when needed) as independent standalone services?
This approach allows to solve mentioned at the beginning issues and some time ago I started to work on the solution with I thing quite a success thanks to SLIM.
I wonder if anyone has some similar experience, attempts with this kind of approach.