Article URL: https://arnoldgalovics.com/microservices-in-production/ Comments URL: https://news.ycombinator.com/item?id=29576352 Points: 44
Comments: 14
Login to add comment
Other posts in this group
Get it from here: https://github.com/c3lang/c3c
In 2019, while contributing to the C2 language, I started up "C3" as a pet project whil
Benchi is a CLI tool for running benchmarks and collecting metrics. It's using Docker Compose to orchestrate the infrastructure and tools being benchmarked, making it repeatable and runnable on di
I've been a long-time Cloudflare user, but sometimes I just want a global load balancer without the lock-in and with full configuration control (e.g., some Cloudflare rules require an enterprise p
Article URL: https://ai-2027.com/
Comments URL: https://news.ycombinator.com/item?id=43571851
They've pulled their browser extensions and integrations except for Firefox. The definition of blatant enshitification and anti-competitive. Moz needs to be held accountable by the EU for this kin
3y | Dec 16, 2021, 12:35:46 PM
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.