4 ms·
My approach is to design like microservices and develop like a monolith. Thinking about microservices will force you to define module, their boundary and interf
by blackoil 10y ago
My approach is to design like microservices and develop like a monolith. Thinking about microservices will force you to define module, their boundary and interfaces. A monolith will simplify deployment, refactoring. Once your code matures, you'll know if any microservice has to be taken out and deployed seperately.
- eric_h 10y agoI agree completely. A monolith with service objects has been a boon for our productivity and made it quite easy to extract those pieces of our architecture that benefit the most from running on their own nodes.
- StabbyCutyou 10y agoThis is definitely one of the main takeaways that I wanted to get across.
- duaneb 10y agoThis is what all experience indicates is correct.
- rads 10y agoExactly. This is great advice.
- hliyan 10y agoMy conclusion as well. In my mind, I call them 'air-gapped modules'. https://www.linkedin.com/pulse/maintainable-software-architectures-microservices-vs-air-liyanage https://www.linkedin.com/pulse/maintainable-software-archite...