You're just declaring more bounded context. You are a linesman? A sewage engineer?
That's not a compelling argument for showing that you understand the difference between the pump station and the treatment center.
Changing the metaphor: in your domain you have local advantages, using your scripting language or Go or what have you. At the treatment center we apply force multipliers at scale. A good example is the actor system, where threads are tamed and bound to cores, and application logic flourishes through work messages and not direct execution.
Asynchronicity, no blocking, and volumetric instrumentation are the force multipliers. On the margin you will complain that it is all too complicated, and with good reason.
You're just manning one pump station.
Moore's Law has been dead for 15 year perhaps, and the pump stations will endure as utilities. Data on the edge will endure forever, because locality is a thing, but computing on the edge is wispy and questionable.
If privacy becomes a thing, will data move to the edges or to the center? If data consistency becomes a thing, if data transformations become a thing with a move to single-payer insurance in the US, will data move to the edges or to the center?
I see no scenarios, except network performance hits a wall, where we are preserving the sensibilities of scripters and writing software that is beautifully single-threaded and synchronous. It is a pipe dream to think that your execution stacks will be anything but tiny 10 years from now.
Hammer and hew your sewer pipes, and keep them "clean" in the way that you have been taught. Times will change and you will not be notified of the event.
I hope you realize you are in danger of becoming Trump's "forgotten man" alongside coal miners and Carrier manufacturing line workers.