Please log in to watch this conference skillscast.
Some of the biggest problems Richard has seen in helping teams build Microservices consistently come from the design of how the services communicate. The issues can seem subtle at first, but become crippling at scale - the first example he was exposed to caused a flood of deadlocks and timeouts as soon as it was turned on in the wild! Over the years, Richard has collected some of the causes of these problems which he'll share, with tips on how to avoid similar problems and stay on the happy path.
YOU MAY ALSO LIKE:
Messages - Patterns and Pitfalls
Richard is a software developer/tech lead/architect who's spent the last few years specialising in microservice systems in .Net for companies big and small, currently working with a team in Copenhagen on their journey from monolith to services. He was worked on AAA games for Microsoft, on minimum viable products for startups, and everything between, bringing a focus on pragmatism and the pursuit of continuous improvement. He is passionate about engineering and solving real problems, over code and complexity for the sake of it, and about finding new and better ways to collaborate and succeed together a team.