3 ms·
+1 Changing one "shared library" shouldn't mean deploying 140 services immediately. They had one service to begin with forked for each destination. Of course
by nikon 8y ago
+1
Changing one "shared library" shouldn't mean deploying 140 services immediately.
They had one service to begin with forked for each destination. Of course that was a nightmare to maintain!
- Cthulhu_ 8y agoI can see their reasoning though; most of those services are pretty straightforward I think (common data model in -> transform -> specific outbound API data out -> convert result back to common data model). The challenge they had is that a lot of the logic in each of those services could be reused (http, data transformation, probably logging / monitoring / etc), so shared libraries and such.