The way engineers traditionally became distributed systems engineers was by creating infrastructure in-house and building hands-on familiarity with how data moved through a system. But specialization among engineers and increasing levels of abstraction have created a situation in which almost no one has a complete view of how data moves through an entire system end to end. At the same time, it’s become harder to understand the systems we’re building because we didn’t build them ourselves. Mobile and web apps are increasingly built on backends as a service (BaaS), platforms as a service (PaaS), and infrastructure as a service (IaaS), and we snap together software as a service (SaaS) like Legos.
We’ve all become distributed systems engineers, intentionally or not. This means that the skills required for understanding and diagnosing problems within a distributed system are more important for everyone, whether frontend, backend, or full stack. Rachel Myers and Emily Nakashima detail tools and skills we can use to get ourselves out of the corner we’ve boxed ourselves into.
Rachel Myers is a backend engineer at Google working on Firebase rules. Previously, she was an engineer at GitHub and ModCloth and founded Opsolutely. In her free time, she designs enamel pins.
©2018, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org