Let’s dig into the Cloud journey and see how Cloud providers build and use open source products. Cloud Native Computing Foundation (CNCF) serves as the vendor-neutral home for many of the fastest-growing open source projects, including Kubernetes and Prometheus. How does the foundation work? What does “Cloud Native” mean? What’s the relationship with Cloud Providers? Based on an overview of cloud features & projects, we will discuss about open source health, community-led success and licencing changes. From open source ideas to community adoption, let’s discover how you should define a cloud strategy to achieve your digital transformation.

Serverless is the fastest way to build a modern application, and in most cases, the lowest cost and most sustainable as well. It’s so much faster than other approaches that it’s worth building serverless first, using all the capabilities of AWS Lambda and related services, before trying to optimize parts of the application by creating new container based long running services. In this talk we’ll look at some of the patterns and tooling, and the many new features that have been released in the last six months. If there’s still some remaining friction in your serverless development flow, let us know what it is, as that feedback is what’s driving the roadmap.

Creating an innovation-driven culture is difficult and requires deliberate and well managed change to how you operate. Scaling it to a large organization is even harder. You also need the organizational context and norms – the culture – that allows innovate practices and thinking to thrive. Nailing these down, let alone what “culture” even is, can be hard. This talk will define what an innovative culture is and then cover several proven methods for leading culture change. Throughout, we’ll draw from use cases from large organizations that have tackled the challenge of changing to a innovation-driven culture.

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.

There’s a great deal of talk about the crucial role culture plays in a successful cloud native transformation. But what does that really mean, and why is it so important? Cloud native is more than a toolset. It’s a full architecture, a philosophical approach for building applications that take full advantage of cloud computing. Drawing on decades of personal experience, Pini Reznik outlines the differences between waterfall, Agile, and cloud native approaches, then proposes a pattern language with transformation designs that may lead to a successful adoption of the cloud native approach.