4 ms·
Yes it is. This makes no sense at all if you are a solo developer working on a smallish project. Here is the agressive part: People who can't see that shouldn'
by Walkman 9y ago
Yes it is. This makes no sense at all if you are a solo developer working on a smallish project.
Here is the agressive part: People who can't see that shouldn't be software developers.
- Moncefmd 9y agoExcept that it is just a showcase that a microservices in a microservices architecture can be language agnostic.
- Walkman 9y agoYou are right, my comment might not make much sense for this specific project.
- notajerk123 9y agoThat’s a bad argument. But, hey, you’re the expert who decides who can and cannot be in this industry.
- Walkman 9y agoUnfortunately not, but if I were the one to decide, I would not be good enough either. :D I was a bit agressive here because too much unnecessary complexity is probably the mistake I hate the most.
- randallsquared 9y agoA solo developer might well have the most reason for a polyglot architecture: they won't have time to write everything personally, but the best or most convenient libraries might be in different languages. Maybe the SaaS provider you want to use wrote libs for their complex API, but only in languages you hadn't chosen. Or whatever. As long as it's not something you'd need to call dozens of times per request, you can quickly spin up an microservice using almost any language to front-end that must-have library.
- Walkman 9y agoWorking with a microservice architecture will always be more work at the beginning, because you have to build the infrastructure before you even begin.