Trying to get a better picture of our #microservices landscape via #OpenTracing #d3jspic.twitter.com/sges3X1qKZ
U tweetove putem weba ili aplikacija drugih proizvođača možete dodati podatke o lokaciji, kao što su grad ili točna lokacija. Povijest lokacija tweetova uvijek možete izbrisati. Saznajte više
I decided to make it a bit more reusable/generic and #OpenSource #d3js https://codeberg.org/hjacobs/application-landscape-explorer …pic.twitter.com/f54LKmXjqz
You can prune the graph around the selection with number keys 1-9 - here the same application selection pruned to 1st degree to 4th degreepic.twitter.com/fQKGnBjF9O
I'm currently mostly interested in app dependencies for migration and deprecation projects. OpenTracing was a key enabler for us for last year's Cyber Week load testing (and forecasting). I agree that OT should provide more value for debugging. /cc @voidmaze
When I see diagrams like this I remember seeing similar ones to represent the classes of monoliths. The difference being that a monolith can be deployed easily. This is not to criticize, rather to encourage (myself?) to think about microservices after the hype. Was it worth it?
This probably highly depends on the context. At the size of Zalando probably yes. Is the cut of services always right? Probably no. But pros are prevailing cons. — Would I start with microservices in early stage startup? Probably no, except there are big, big benefits.
Looks like a well designed and orchestrated infrastructure. But honestly it somehow underlines my argument that software engineers are artisans rather than engineers.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.