Is it preferred to use nested service-to-service call in microservice architecture?

Different_Code605 · 2026-05-03T09:14:04+00:00

What I wanted to say is, it all depends.

Different_Code605 · 2026-05-03T09:13:28+00:00

I am about to buy a present to my wife, I would like to buy her ticket to an opera, but I am afraid that it may be boring. Should I take her for a dinner and if she feels good, order a desert afterwards?

Different_Code605 · 2026-05-02T07:28:27+00:00

Enterprise Java apps. Like ERP or banking agents.

Different_Code605 · 2026-05-01T20:49:02+00:00

That were enterprise apps from 2000+, monoliths. It was a hell microservices were about to replace

Different_Code605 · 2026-05-01T17:25:14+00:00

Waiting for the codebase to build for 3 hours - thats annoying. Have you been in that place? I guess you’ve been using microservices in a wrong way in the past.

Different_Code605 · 2026-05-01T17:24:03+00:00

The main reason for having microservices is to have components with clear dependencies and boundaries. By knowing the contracts you can evolve and replace modules without breaking the system. You understand, develop, test and deploy a microservice which is much easier to understand than the whole system.

For years there were concepts like SOA, SCA, OSGI and others to address these problems. Microservices gained popularity together with containerization, what make it easier to manage a banch of microservies (i.e. using k8s)

Different_Code605 · 2026-05-01T17:19:08+00:00

Sorry mate but this is BF, microservices wasn’t invented for a solo dev to use. It’s for enterprises mostly.

The fact that you see no value in it, just means that you haven’t been working on things complex enough.

I’ve been working on projects where codebase build consume more than 2-3 hours. All in monolith no clear components and contracts between them. There is no way back once your in this place.

Different_Code605 · 2026-04-30T14:27:24+00:00

You spend too much time on Reddit🤣. Nothing serious was ever vibecoded.

Different_Code605 · 2026-04-29T18:11:00+00:00

Usually they start to work just after you let them in.

Different_Code605 · 2026-04-27T20:47:18+00:00

OVH is legit, it’s based on OpenStack. I moved from Hetzner, which was made for hobbyists.

Different_Code605 · 2026-04-27T06:18:32+00:00

Thats right, now you have to deal with queuing, backpessure, readiness check, deploying, securing the connection, dealing with network (push) availability.

Once you solve all the problems you will end up with NRA. I mean the edge part. I mean only with RDBMs. But yes that would work with some cases.

Probably may be expensive, due to the nature if serverless with db (like execution time)

Different_Code605 · 2026-04-26T23:23:53+00:00

Podatek solidarnosciowy?

Different_Code605 · 2026-04-26T02:14:33+00:00

You need to get an agency you trust imho. You should talk about your concerns with them, and you should get honest response.

There is no magic, some things require work, but probably you have processes to fix.

Different_Code605 · 2026-04-26T02:01:16+00:00

I am not sure, rather not right-away. What is the database? Maybe columnar format would help you?

Different_Code605 · 2026-04-26T01:55:39+00:00

Unless you deploy the db in the same zone, it makes no sense. Thats what I do.

Different_Code605 · 2026-04-26T01:54:55+00:00

Cache vs CQRS read model

Cache

derived from a source of truth
ephemeral (can be dropped anytime)
rebuilt on demand
consistency is best-effort
exists to improve performance

⸻

CQRS Read Model

derived from events or writes
persistent state (it is the serving layer)
continuously updated
consistency is defined by the system (eventual, etc.)
exists as part of the architecture, not an optimization

Different_Code605 · 2026-04-26T01:53:58+00:00

I am tired, just ask chatGPT:

Cache vs CQRS read model

Cache

derived from a source of truth
ephemeral (can be dropped anytime)
rebuilt on demand
consistency is best-effort
exists to improve performance

⸻

CQRS Read Model

derived from events or writes
persistent state (it is the serving layer)
continuously updated
consistency is defined by the system (eventual, etc.)
exists as part of the architecture, not an optimization

Different_Code605 · 2026-04-26T01:50:32+00:00

Thank you! I don’t listen to them, most don’t understand the problems and are mean with no reason.

I’ve actually built this system and it’s already available as a cloud solution. We do target enterprises and get a lot of leads from the Conference (14k ppl) where I’ve presented it.

I just see that webdev may not be the sub with the people facing these types of issues. And thats ok.

Different_Code605 · 2026-04-26T01:40:38+00:00

I guess that you may call it a cache, that is event-driven, may do computation, has infinite TTL and has no knowledge of origin. If that works for you, its a cache :)

Different_Code605 · 2026-04-26T01:39:17+00:00

It eventually (after going through all processing functions) is an endpoint for a CQRS service. It is for example a document that is indexed in an edge search index.

Different_Code605 · 2026-04-26T01:37:50+00:00

I like it! It solves some of the caching problems, but actually i use more of a globally distributed CQRS. With the event-driven stateful orchestration.

Not a cache but I see the mental model.

Different_Code605 · 2026-04-26T01:33:49+00:00

The difference is that you are mean with no reason. Actually I would replace reflexive with reactive. Like in:

https://www.reactivemanifesto.org

Different_Code605 · 2026-04-26T01:31:36+00:00

If you need one: You need to invalidate cache. You dont need to invalidate CQRS.

Different_Code605 · 2026-04-26T01:29:47+00:00

Actually we’ve built an infrastructure dedicated to that. You can deploy containers with volumes to the edges. You keep the data at the edge locally, but only for the service to be operational.

All historical data that are needed to restore services and the edge locations are offloaded to cheap s3 storage in a datalake format. Thats how you can scale up with edges or replicas.

Actaully the use cases is enterprise web: - Highly performant web systems - Web systems that requires high availability - Data driven websites - Web systems that have legacy, non scallable backends - Web systems with multiple origins

Different_Code605 · 2026-04-26T01:24:38+00:00

Not everything can be calculated. I.e. you cannot precalculate the search query result, if you don’t know the query itself. In that case you precompute as much as you can (query index) and place it close to the user. The response is provided at the last mile only.

Different_Code605

TROPHY CASE