NashJS: How Do You Know If You've Made a Microservice?

The Topic:
So I hear you want to make your application scalable, resilient, and easy to reason about. You've heard about these cool things called "microservices", and you break up your application into many small parts. Great! But why is it slow/not scaling/full of bugs/impossible to onboard new developers onto? Stop pulling your hair out, and let's talk about what it actually means to write systems that are explainable, simple, and appropriately "microserviced". We'll cover what it means to decomplect an application into its base components, and I will share my own experience breaking out an enterprise monolith over the past two years into a fleet of microservices that has enabled my team to go fast, scale, and avoid the pitfalls of feature creep.

About the speaker: Derek is a distributed systems enthusiast and amateur historian with 15 years of experience writing complex software. His experience ranges from PhD research at Purdue, teaching programming/computer organization at Tennessee State, and building enterprise-grade applications at large companies. He is currently a Software Engineering Director at HCA Healthcare, leading a team of 20 developers who build software used by clinicians in 180 hospitals every day. While he has coded in a wide gamut of languages from Golang to JS to assembly, he is currently enraptured in Clojure functional programming and is unlikely to be saved.

See you there !

Code of Conduct is listed on our about section