3 ms·
Man what a mess. Meanwhile, everyone else can extend a library used by their common services in a common language trivially.
by skullone 3y ago
Man what a mess. Meanwhile, everyone else can extend a library used by their common services in a common language trivially.
- rs_rs_rs_rs_rs 3y agoLet me guess, they should rewrite everything in Javascript?
- skullone 3y agoWoe is us if they actually did.
- tomrod 3y agoNah, Excel. /s
- HumanOstrich 3y ago[flagged]
- wmf 3y agoAlmost everyone embraced polyglotism and microservices together.
- hotnfresh 3y agoMeh. As long as you’ve got a good, typed interface for passing messages between them and for having a common understanding of (and versioning system for) key data structures, that’s fine for this sort of thing where it’s largely processing steams of small messages and events. … but it’s probably JSON and some JSON-Schema-based “now you have two problems” junk instead of what I described. In which case, yeah, ew, gross. Unless they’ve made some unusually good choices.
- nostrebored 3y agoThere are tons of approaches to align on service contracts for JSON based API calls. There’s also libraries like gRPC which help make contacts explicit. Neither are really uncommon
- xwowsersx 3y agoWhat are some of those approaches? Are there formal methods and/or tools for doing this?