actually you would only have to change the one reader and the one writer. The services themselves do not differ, but are fanned out. E.G. so 100 workers watch

actually you would only have to change the one reader and the one writer. The services themselves do not differ, but are fanned out. E.G. so 100 workers watch your pdf queue to generate pdfs. If your zip code is really used by many services, the question is how you want to communicate those objects and there are really a lot of choices out there. GRPC / Soap / Shared model package / and the list goes one. On the other hand i have obsverved that people push full blown models around just to end up reading one field of it in their monolith. I believe the PHP frameworks of the past where the biggest offenders like that. When i was working with sugarcrm for instance, it was not uncommon to pass huuuuge objects between functions because you needed 1 field. It's PHP so by default, function arguments are passed by value, so you can already see where the fun begins.