Article URL: https://arnoldgalovics.com/microservices-in-production/ Comments URL: https://news.ycombinator.com/item?id=29576352 Points: 44
Comments: 14
Creato
3y
|
16 dic 2021, 10:20:03
Accedi per aggiungere un commento
Altri post in questo gruppo

Article URL: https://pudding.cool/2025/04/music-dna/
Comments URL: https://news

A couple of months ago, I built this app to help identify people stuck under rubble.
First responders have awesome tools. But in tough situations, even common folks need to help.
After what ha

Article URL: https://github.com/zobweyt/textcase
Comments URL: https://news.ycombin

Last week was big for open source LLMs. We got:
- Qwen 2.5 VL (72b and 32b)
- Gemma-3 (27b)
- DeepSeek-v3-0324
And a couple weeks ago we got the new mistral-ocr model. We updated our OCR b

3y | 16 dic 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.