Article URL: https://arnoldgalovics.com/microservices-in-production/ Comments URL: https://news.ycombinator.com/item?id=29576352 Points: 44
Comments: 14
Erstellt
3y
|
16.12.2021, 10:20:03
Melden Sie sich an, um einen Kommentar hinzuzufügen
Andere Beiträge in dieser Gruppe
Article URL: https://research.swtch.com/diffcover
Comments URL: https://news.ycomb

Article URL: https://arxiv.org/abs/2504.17192
Comments URL: https://news.ycombinator.c

Article URL: https://arxiv.org/abs/2504.11651
Comments URL: https://news.ycombinator.c

Article URL: https://curry-lang.org/
Comments URL: https://news.ycombinator.com/item?id=4379721

This project aims to formalize the first volume of Prof. Bertrand Russell’s Principia Mathematica using the Lean theorem prover. Throughout the formalization, I tried to rigorously follow Prof. Ru
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.