Quality engineering in a world with AI and IoT

Editor's Notes

• #3: Why are we here today? DevOps buzzword – no formal definition Our view of devops, history of amazon, …
• #8: Established 1994 (seattle)
• #9: company’s logo is subtly designed to portray a customer’s smile
• #10: - we took the monolith and broke it apart into a service oriented architecture - factored the app into small, focused, single-purpose services, which we call "primitives" - for example, we had a primitive for displaying the buy button on a product page, and we had one for calculating taxes - every primitive was packaged as a standalone web service, and got an HTTP interface - these building blocks only communicated to each other through the web service interfaces - this created a highly decoupled architecture where these services could be iterated on independently as long as they adhered to their web service interface - to give you an idea of the scope of these small services, I've included this graphic - this is the constellation of services that deliver the Amazon.com website back in 2009, 8 years ago - this term didn't exist back then, but today you'd call this a microservice architecture
• #11: - I have a confession to make – I used to hate the term "DevOps" - it bugged me because it's a very fuzzy term - people use it in many different ways to mean many different things, so no one really knew what other people are talking about when they hear it - earlier this year, I finally caved to the momentum, and started using it in my talks - I had to admit that "DevOps" came the closest to describing this new modern style of rapid cloud development and delivery that I talked about today - since I'm using this fuzzy term, it's now my responsibility to define it, so at least we're on the same page - but rather than try to define it directly, I'm going to put it in the context of something that all of us are familiar with - the software development lifecycle - here's the general development lifecycle for a web application or service - on one side is the development team, and on the other side are the customers - every new feature or bug fix goes through this same process - developer writes code, code is built and unit tested, app is deployed to a testing environment for deeper testing, finally given a thumbs up and deployed to production where customers can use it - after that happens, the company can collect feedback from customers, make decisions, and continue to iterate and improve the product - there are a few important things to note here - the speed of completing this loop determines your business agility: to go from an idea, to a delivered feature, to learning about it and coming up with the next idea - the faster you can complete that loop, the faster you can innovate - if you can only complete this cycle once a month, you will be outmaneuvered by competitors that can do this every day - another point is that you're only adding value when you're writing code for new changes - the effort you spend in this middle section is lost time - don't get me wrong, you need to ensure high quality releases, but the less your team spends releasing software, the more time they can be writing code - to me, that's the essence of DevOps – to make this process as efficient as possible, and speed up the learning cycle - this is why DevOps is fuzzy, because there are many different ways to optimize this cycle - you can make process changes, organization changes, culture changes, tool changes - to me, they all count, and I think it's fine to classify them all as DevOps
• #12: - with these new tools, we completed the puzzle - the teams were decoupled and they had the tools necessary to efficiently release on their own
• #13: - what does success look like - there are a lot of ways that you can measure the process, and no one way is perfect - but here's one data point - when you have thousands of independent teams - producing highly-factored microservices - that are deployed across multiple dev, test, and production environments - in a continuous delivery process - you get a lot of deployments - at Amazon in 2014, we ran over 50M deployments - that's an average of 1.5 deployments every second
• #15: Why are we here today? DevOps buzzword – no formal definition Our view of devops, history of amazon, …
• #16: Amazon Go is a new kind of store with no checkout required. We created the world’s most advanced shopping technology so you never have to wait in line. With our Just Walk Out Shopping experience, simply use the Amazon Go app to enter the store, take the products you want, and go! No lines, no checkout. (No, seriously.) No lines, no checkout Our checkout-free shopping experience is made possible by the same types of technologies used in self-driving cars: computer vision, sensor fusion, and deep learning. Our Just Walk Out Technology automatically detects when products are taken from or returned to the shelves and keeps track of them in a virtual cart. When you’re done shopping, you can just leave the store. Shortly after, we’ll charge your Amazon account and send you a receipt.
• #35: The truth is, the future is always in the making. It’s engineers and wild thinkers that are helping to create the world of tomorrow. It’s customers like tusimple, revolutionizing the commerical trucking industry, arterys saving lives through 4d medical imaging, duolingo teaching language around the world.. It’s customers like you that are helping to build this. Together, we can tackle some of the worlds most challenging problems, and together we can continue to build a smater future.