Wednesday 11:40 - 12:40
Microservices were all the rage, so you broke up your monolith. The services talk to each other by gRPC, you use a service mesh to route and load balance, and provide reliability oriented computing, you are fully buzzword compliant.
Yet something seems to be wrong.
You can't easily release software from one team, without coordinating with teams creating other. Testing has to be end-to-end to flush out problems or risk your team creating breaking changes for another team. Your 'heavy-lifters', whether you call the principals or architects seem to spend all their time on Docker, K8s, Istio and a whole slew of infrastructure technologies. Your system won't run without them, and you feel locked in.
2-Day Workshops workshop - 6-7 May
Increasingly developers are relying on distributed architectures to solve the problems of scaling their applications and their development teams. But that means they now have to consider the problem of getting the parts of their systems to talk to each other.
Full Stack Engineer, Pluralsight Author, OSS Hacker
Managing Editor, Pragmatic Bookshelf
Front End Jedi, Evangelist and Dog Lover