You've found a Premium Feature!
Certain videos, events and workspaces require a Premium Membership. Become a Skills Matter Premium Member today to access exclusive benefits including free tickets to online conferences, Members-only events and discounts on training.Unlock this Video
Cloud-native microservices encourage autonomous teams that make their own decisions without high-overhead formal processes to deliver features rapidly. However, we need to glue services together at some point. Without oversight, how do they seamlessly integrate technically and with smooth user experience, a.k.a. how do we avoid distributed balls of mud? And what is the role of an architect if teams make most of the decisions and designs? The modus operandi changes from owning decisions to facilitating team decision making in a way that aligns with business and technical strategy (without scaring teams with the concept of "strategy").
In this talk, we discuss the role of an architect in a world without ivory towers and techniques we can use to help teams pull in the same direction, enhancing their dev velocity over time. We'll share lessons we've learnt at Atlassian, a globally distributed company with a very strong grass-roots engineering culture.
YOU MAY ALSO LIKE:
How to Win Friends and Influence Architecture
Jeff Farber is an architect at Atlassian, where he currently focuses on building enterprise customer solutions within the Atlassian cloud. In his prior Atlassian role, he built a critical permissions service used across Atlassian. Jeff has been building software since a young age across various domains. He enjoys guiding software teams and making business-oriented software decisions.