News for hackers. Stuff that matters.
Re:How big should a microservice be? (2013) by pageandrew on Wednesday July 07, 2021 @10:33PM (#27767941)
I don't really care about service size. I care about service division across logical boundaries, namely encapsulated responsibilities. A properly architected service should be responsible for a particular domain, say payments, messaging, image processing, etc.

It's up to each team to decide where to draw those lines. I think that for most teams, domain-specific services are superior to task-specific microservices, since it strikes the best balance between the benefits of separate services and the infrastructural overhead required to run a distributed system.

That said I agree that you should start with a monolith.

Re:How big should a microservice be? (2013) by dgb23 on Thursday July 08, 2021 @04:14AM (#27769421)
> domain-specific services are superior to task-specific microservices

Can you elaborate on that? Isn't "messaging" or "image processing" a task?

Re:How big should a microservice be? (2013) by konschubert on Thursday July 08, 2021 @05:47AM (#27769957)
If you go all in on micro-services, image processing may have an ingress service and a scaling service, and a conversion service, and, and, and...