3 ms·
I've used this paradigm for a long time. What's new here ? Basically your code has no concept of "network boundary", there's only package import each other, th
by revskill 3y ago
I've used this paradigm for a long time. What's new here ?
Basically your code has no concept of "network boundary", there's only package import each other, there's no "microservice".
But when deploying, i can choose which package to be deployed as a service.
- kitd 3y agoWhat's new is that you don't choose, the runtime does, generating the cross-network interface as needed.
- revskill 3y agoNo way (or no need) to be such generic. You should have a choice (at least it's my choice). Because your app is separated by functionalities, not technical aspects.
- danielvaughn 3y agoUnless I'm misunderstanding, separation by functionality is only useful for engineering teams. Once it's in production, the only thing that matters are the technical aspects. By technical aspects, I'm interpreting to mean mem/cpu usage, throughput, security requirements, etc.