Article URL: https://arnoldgalovics.com/microservices-in-production/ Comments URL: https://news.ycombinator.com/item?id=29576352 Points: 44
Comments: 14
Connectez-vous pour ajouter un commentaire
Autres messages de ce groupe
Share your information if you are looking for work. Please use this format:
Location:
Remote:
Willing to relocate:
Technologies:
Résumé/CV:
Email:
Article URL: https://www.josh.ing/hn-slop
Comments URL: https://news.ycombinator.com/item?
I keep running in the same problem of each AI app “remembers” me in its own silo. ChatGPT knows my project details, Cursor forgets them, Claude starts from zero… so I end up re-explaining myself d
Hi HN — we're the team behind Arch (https://github.com/katanemo/archgw), an open-source proxy for LLMs written in Rust. Today we're releasing Arch-
I just launched JS1024 — a creative coding challenge with a strict limit: 1024 bytes of JavaScript.
No libraries. No frameworks. Just raw code.
You can submit visual effects, generative art, t
Article URL: https://blog.greg.technology/2025/06/30/fastly.html
Article URL: https://www.figma.com/blog/s1-public/
Comments URL: https://news.yco
4y | 16 déc. 2021, 12:35:46
Can be said, that each time start with monolith, because it easier. If you grow, you can set up required microservices, which is highly optimized for current task.
Problem with microservices, when you are starting is communication, separation and you dont clearly see, which function should that microservice really do. Because usually each service must have access to database layer, then you dont know if databases should be separated or not.
Problem with monolith is basically harder horizontal scaling, but you can, in these days, scale vertically, server configurations are pretty powerful these days. Then if your website will work, you can start thinking of microservices.
So starts small, if project grows, just try to separate services.