On this episode of Modern Digital Business, we dive into the world of ModernOps and talk STOSA (Single Team Oriented Service Architecture) with Beth Long.

This is part 1 of a two part discussion with Beth Long, an operations manager for New Relic, and Jeli.io. She is passionate about the concept of STOSA, which was first introduced in Lee Atchison's highly popular book, Architecting for Scale.

Lee and Beth switch roles for a bit, with Beth interviewing Lee on these and related topics.

"Stosa: Stosa or single team oriented service Architecture is an important guiding principle for organizations that have development teams that own and manage applications that are composed of multiple services."

— Lee Atchison 00:00:00

Accountability and Ownership in Service-Based Architectures: "Each service needs to have a team that owns that service 100%, all aspects of that service. And it's a one to end relationship...but each of those services has exactly one team owner...that ownership has to be well understood throughout the organization, well known, well documented..."

— Lee Atchison 00:03:30

The Impact of Clear Visibility on Company Culture: "And that kind of culture tends to arise when there's confusion and frustration. And that's a byproduct of not knowing where the problems are and not understanding. And so when you have that clear visibility, you can reduce that tendency because now you know what's happening and where and why, and you can actually get traction on the problem."

— Beth Long 00:12:33

The Challenges of Meeting SLAs in Cloud Services: "If I had a requirement that I couldn't meet with my dependencies requirements, it was my responsibility to get creative, to find a solution. Whether that was caching running instances to attach later or whatever it was, it was my responsibility to solve that problem. I could do that by getting creative. I could do that by negotiating with my partners to have better or different SLAs available to me."

— Lee Atchison 00:13:16

Ownership and Boundaries: "If an organization has a microservices architecture and the boundaries have become fuzzy over time, they should be cautious when dividing up ownership and making it a single team. There are rules of thumb that they can think about to avoid complications."

— Beth Long 00:17:36

"Shared Tooling and Service Responsibility: Even though those teams own services that are shared in terms of their usage, but they still own a service and they're still responsible for that service and they're still responsible."

— Beth Long 00:23:02

Management Attitudes Towards Internal Customers: "There's this kind of this attitude that if we're doing work for our internal customers, like, we should be doing as little of that as possible. And that always frustrated me because I thought, no, this is the inner workings of a body."

— Beth Long