Tuesday, December 7, 2021
OPENING KEYNOTE: WSO2 -- Cloudy with a Chance of Integration - A Practical Approach to Cloud Native Integration
Today no code and low code integrations are all the rage in app development. Over the past decade we've seen various approaches to integration and app development including full code, low code and no code, as well as specialized integration languages and DSLs, let alone developers who claims their integration is composed of complex microservices. Analysts predict that more than 50% of development work is really integration of various systems. Whilst proponents of the various technologies argue over the pros and cons of each, one aspect is clear - integration is key to development, regardless of how you get there. This talk is a Solution Architect's take on making sense of complex integration. Having worked with teams dealing with over 1500+ integration projects over the past decade, we look at the various types of integration projects and challenges teams have faced. We pick examples from startups and SMEs to large fortune 500 enterprises and look at successful projects as well as failed projects. Maybe there isn't a one size fit all solution to integration, even within a single organization. We propose an approach that combines the best of all worlds which addresses multiple personas, so that everyone can use what they like. And whilst at it, arrive at the true objective they were looking for - Integration!
The development of APIs always begins with the old -- and meanwhile boring -- battle of API-first or code-first. However, working with APIs involves a process that includes design, development and operation. With this in mind, along with the various ways API gateways and API platforms can support these processes, the question of how to automate these processes arises very quickly.
In this session, Daniel Kocot will show how API gateways and API platforms can positively influence the development process of APIs based on the DevOps concept and CAMS model to deliver better and better APIs to consumers.
With supercomputers in our pockets, self-driving vehicles, and software recognizing images better than humans, what we recently thought of as the future is already here, so how do we define the next future? Rod Cope explains how different aspects of artificial intelligence, augmented reality, high-performance computing, digital platforms, massive bandwidth, and an obsessive focus on user experience will be the fundamental drivers to future application success as we build upon lower barriers to entry and shift from improving technology to improving life. Rod shares his 20+ year journey from the forefront of open source to a predicted future where the IoT and big data are the new normal and the key questions are less “How can we do it?” and more “How do we make it better?” Come to this session to learn what you can do now in terms of research, planning, and investment to get the most out of our inevitable future.
This talk introduces Site Reliability Engineering (SRE) at Google, explaining its purpose and describing the challenges it addresses. SRE teams manage Google's many services and web sites from our offices in Pittsburgh, New York, London, Sydney, Zurich, Los Angeles, Dublin and Mountain View. They draw upon the Linux based computing resources that are distributed in data centers around the world.
As companies grow in size, achieving true agility becomes more and more challenging. Adding OKRs on top of that can create even more friction. But can OKRs really help your organisation be agile? In large technology organisations, friction is created when trying to implement and track OKRs. This happens because OKRs are perceived as a waterfall-like way of presenting business value to the teams and traditionally companies have been using activity-based OKRs. We will explore how agile can scale, by adopting value-based OKRs, while still leaving space to the teams to self-organize and plan their work. Examples will be given from both Scrum and large scale agile like SAFe.
“We’ll build it ourselves!”
We’ve all heard it, seen it, and likely been directly impacted by the decision to build a custom, in-house solution rather than use an existing one.
Whether it’s a CI/CD tool, artifact management solution, or even the entire DevOps tech stack, it’s a common misconception that building it internally is easier, cheaper, and faster. When, in fact, the complete opposite is true!
Modern development processes demand high levels of availability and performance, so building a custom system that provides both of these isn’t a trivial undertaking.
So why, then do enterprises continue to build in-house? And what exactly are the benefits of purchasing an existing solution? And how does this impact the quality of their overall organization?
Join Cloudsmith’s Dan McKinney in this session as he answers all of these questions while helping attendees understand the true difference between building and buying DevOps solutions, how to make the best decision for your organization, and the benefits of an existing solution made to solve the problems you face.
This talk will focus on the architecture implications of a fast growing fully-remote organization and the use of a monolithic (versus micro services) application to facilitate scalability, onboarding, and manageability. This is a real-world case study.
Ever wonder where your organization's DevSecOps effort stands relative to your peers? GitLab's fourth annual survey of developers provides insight into the maturity of DevSecOps and reveals key trends. We'll cover key takeaways to take your program to the next level.
In the course of your day as an SRE or DevOps, or SysAdmin, your knowledge and expertise are in high demand. You can’t do every task every person in your org needs from you without the help of comprehensive automation. Automation can be tricky. Some systems aren’t built with automation in mind, but assume that a human being will be there to keep an eye on things and fix errors on the fly, and we can’t be everywhere when there’s too much to do. Plus, you want to provide access to automation for the right folks and keep a record of when the tools were used.
In this talk, we’ll cover some things to keep in mind when you’re building out your automation library, characteristics of good automation, and give you a look at Rundeck by PagerDuty, a platform that will help you share your expertise with other folks in your organization. Build automation that works for you and gives you your time back!
The hype around AI is real, but who among us is actually capitalizing on it? It's estimated that anywhere from 50-90% of AI models developed never make it past the AI "valley of death" that exists between the lab and deployment into production. This talk will cover how an API-centric approach to building and maintaining AI-enabled applications can bridge the divide between data scientists, software developers, and infrastructure managers and make the power of AI accessible to everyone. Not only is this approach better by making AI more accessible and easier to use, but also offers leaders the sophisticated governance and compliance monitoring needed for AI at scale.
In today’s business environment, companies are challenged by scattered business management tools and interfaces that don’t work well together, tedious and manual processes and paperwork, and ultimately lost business due to decreased automation and inefficiencies. In this session, attendees will learn how those challenges can be addressed through the power of built-in, no-code API integrations and management - demonstrated through a real use case. Attendees will hear from airSlate, a leader in workflow automation solutions, and TurnKey Lender, which provides AI-driven risk assessment, decision management, and digital lending process automation software and services for businesses ranging from lending companies, banks, and credit unions to alternative lenders, healthcare companies, and retailers. By integrating with airSlate's eSignature solution signNow, TurnKey Lender was able to offer its customers an intuitive signing solution within their digital lending platform. This has resulted in a seamless and flexible digital lending process, enhancing the end-to-end platform with legally-binding eSignatures, delivering a safe and intuitive e-signing experience to lenders and borrowers, and reducing loan approval lifecycles from weeks to just 30 seconds.
Wednesday, December 8, 2021
Airlines have on-time arrival. Retail has sales per square foot. Marketing teams have cost per acquisition. Manufacturing has yield and safety scores. But how do we measure the performance of engineering teams, and why is understanding team performance so important?
If you’ve ever wondered how to solve that nagging feeling of wanting to “improve the team” but not being able to say exactly what that means, or if you know your team is world class and want a way to prove it, this is the talk for you.
In this session, CircleCI CTO Rob Zuber will look at anonymized team data to share insights, behaviors, and metrics that lead teams to both high quality, and high velocity. He’ll share anonymized, aggregate data from millions of builds to show best practices on commits and pull requests, disaster recovery, frequency of deploy, and more.
- Measuring team performance sounds scary, but it’s really helpful for everyone to see where the opportunities for improvement are, and to foster open discussions about what’s working and what’s not
While velocity is critical, velocity without quality is a recipe for disaster.
- Monitoring consistency metrics like net value score, time to recovery, and transition information can help your team get better at both speed and quality
It’s the middle of the night, and there’s much ado about nothing. Well, not quite about nothing - there’s definitely something happening: one of the services your team owns is crashing. And by crashing, I mean sometimes crashing. It’s not really that bad, but it’s bad enough for the floodgates to open and for the DevOps folks to lose their marbles and ping you relentlessly on Slack. Ping. Ping. Ping.
This talk is all about that feeling, and what we can do to make the whole situation suck less when it inevitably comes up again. We will walk through a close-to-real life incident from the perspective of the on-call developer, and discuss practical and technical steps developers can take to increase observability while on-call (even when a serious, hard to debug issue arises).
In complex projects, the last 10% of the project is often the most difficult part. In this talk, I will share a case study of Box's 4-year effort to get rid of our legacy mapping DB and move the last piece of our legacy monolith MySQL traffic to our data access layer. This talk will cover how to manage technical risk and optimize team execution in a technically complex and operationally distributed environment. This talk will share reflections on useful tactics that led to the successful completion of this 4 year migration project for others to learn from and leverage.As a relatively new Staff engineer, I learned and experimented with building and maintaining a long time-horizon project plan, identifying unknown unknowns, and continually finding ways to de-risk the project at every stage of development. As the project progressed, I found that successful execution depended not only on these technical strategies, but even moreso on how the team operated. In the spirit of Agile and mitigating the isolation of the pandemic, we experimented with almost every aspect of how we worked: how/when we worked together, how our sprints ran, how we evolved designs, and even the minutia of how we retrospected. In this session, we will have a candid discussion on the technical and organizational strategies that I believe were important to our success, or that were promising enough to warrant more experimentation in the future. Participants will leave with a few ideas that they should be able to try out within their own teams. Additionally, there are some deeper ideas about team leadership and effectiveness that I hope participants will be able to reflect on going forwards.
Roman Stanek, current founder and CEO of GoodData, has founded three SaaS companies over the past 22 years. His first two companies, NetBeans and Systinet, both ended in successful exits, including a sale to Sun Microsystems and one of the most successful acquisitions in the web services/SOA space. GoodData is currently experiencing rapid growth including a 33% expansion across the entire customer base in Q4 2020, a 9x increase in the number of self-service accounts in 2020, and the signing of our largest expansion deal yet, a $14 million contract –– all critical metrics as GoodData continues to surge and provide customers with high-quality data analytics and insights. Until now, there’s been little market pressure for BI to adapt to modern devops tooling and best practices like CI/CD, DataOps, GitOps and others. Popular BI tools often offer a “real time BI optimized” architecture that removes the analytical storage layer to reduce ETL latencies. Unfortunately, in most cases, the analytical capabilities are severely limited in the “real-time-optimized” mode. Roman and the GoodData team just released GoodData Cloud Native after two years of engineering work — the first solution to deliver enterprise-grade analytics as a microservices-based stack. Roman can speak to how to identify not just today’s market need but tomorrow’s — and how to turn those insights into the next phase of your roadmap. For GoodData, that looked like putting analytics on equal footing with core business operations like app dev, and committing to a headless BI structure that delivers scalable, real-time data to everyone who needs it.
As enterprises quickly adapt to a contactless, digital-first world, there is a crucial need to deliver customer-centric features in short iterations. This requires rethinking how teams innovate, develop, and deploy solutions and reimagining the flow of value within the organization. In this session, I share two phenomenal case studies that showcase how teams disrupted organizational culture and existing processes in a non-traditional way to achieve their business outcomes. Through these stories, I highlight how important it is to rethink and reimagine how we approach problems, develop solutions, and have fun while we are achieving our business outcomes.
Code Review is a great collaboration tool and it is a socio-technical engineering practice that every software developer already uses (or should). While many view code review as a low-value formality in the code writing process, its promise is so much more -- from writing more robust code and learning from one another, to developing a deeper understanding of the systems we work on and even helping to build a sense of collective ownership among fellow engineers. I will talk about why we need to focus more on its social aspects, best practices, and concrete ways to promote more inclusive code reviews. Even if we each learn one way to participate in code review better, this would have a huge positive impact in the everyday lives of software developers around the globe.
With just CI/CD/CR, technology and product leaders miss out on a critical step in delivering products to the market. "Continuous Exploration" is the foundational building block of product development lifecycles. Come and gather ideas on how you can avoid this pitfall.