News for hackers. Stuff that matters.
Re:How big should a microservice be? (2013) by adrianN on Thursday July 08, 2021 @03:11AM (#27769124)
Write microservices, but link them in one binary and do normal procedure calls. The important part about microservices are the clear interfaces, the lack of global state blobs, and the independent testability, not the 50 cloud services needed to manage containers.
Re:How big should a microservice be? (2013) by konschubert on Thursday July 08, 2021 @05:44AM (#27769942)
One advantage of real microservices is that you get better tooling around rate-limiting HTTP APIs than for simple function calls. And it's much easier to see which services creates the most CPU/Database/Network load.
Re:How big should a microservice be? (2013) by muxator on Thursday July 08, 2021 @08:50AM (#27771262)
In this context, the measuring aspect would be taken care by profiling/instrumenting.
Re:How big should a microservice be? (2013) by dgb23 on Thursday July 08, 2021 @04:10AM (#27769400)
Sounds like modules to me.
Re:How big should a microservice be? (2013) by adrianN on Thursday July 08, 2021 @05:33AM (#27769873)
Modules, but with 100% more hype. Best practices for software engineering haven't changed all that much in the last two decades or so, but the vocabulary keeps changing.