3 ms·
To tell you the truth it has nothing to do with monolith. You think if you write it in microservices because that's what's "hip" now you're very wrong.
by romanovcode 11y ago
To tell you the truth it has nothing to do with monolith. You think if you write it in microservices because that's what's "hip" now you're very wrong.
- Cthulhu_ 11y agoBesides, the microservices architecture doesn't mean you should re-implement features (like the framework / library type of functions). Microservices have the same amount of code, if not more, than the monoliths they're supposed to replace, and likewise should employ code re-use / not re-invent the wheel as much as possible.
- romanovcode 11y agoYea, exactly. Company I'm working with now made the mistake of following the hip. Basically management were crazy about node and microservices. Went from PHP "monolith" with couple of services to Node.js using microservices. Jesus what a mess, our previous stack was 10x cleaner. Not to mention company now spends thousands of dollars every month for all the new/cool AWS stuff. But hey, they pay me so I'm not complaining. :)