Article URL: https://arnoldgalovics.com/microservices-in-production/ Comments URL: https://news.ycombinator.com/item?id=29576352 Points: 44
Comments: 14
Vytvořeno
3y
|
16. 12. 2021 10:20:03
Chcete-li přidat komentář, přihlaste se
Ostatní příspěvky v této skupině

Article URL: https://thenewstack.io/nvidia-finally-adds-native-python-support-to-cuda/
Comments URL:
For popular threads with a lot of comments, collapsing a top comment leads to high CPU usage and can cause browsers (I tried in Chrome and Vivaldi) to freeze up.
For example, this very popular t

Article URL: https://lyra.horse/css-clicker/
Comments URL: https://news.ycombinator.com


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