Hacker News new | past | comments | ask | show | jobs | submit login

This reads like someone who spent a lot of time using one particular framework (maybe two) and now wants to justify their inability to survive without said framework(s). Not sure at all why it's also about monoliths and microservices; I've written microservices in Django, for example.

Sometimes a monolith makes sense. Other times, a microservice architecture makes sense. Sometimes a "just right" sized repo makes the most sense, neither a monolith nor a microservice.

Why does it have to be so tribal? Why is there a #monoteam and a #microteam?




> Why does it have to be so tribal?

I think it's just a symptom of "When the only tool you have is a hammer, everything looks like a nail."




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: