2018 Talks by Donna Malayeri - @lindydonna
--
QCon New York - June 29, 2018
- Talk slides
- Video [Requires InfoQ subscription]
Not all compute in modern cloud applications is serverless, nor should it be. Most modern applications use a mix of serverless functions and containers for their compute needs. And, with new container offerings like AWS Fargate and Azure Container Instances, the boundary between containers and serverless has become more blurry.
We’ll talk about how we’ve helped our customers transition from a traditional architecture to one that uses serverless and containers. They can now ship solutions more quickly, as their deployment and ops practices are far simpler. Engineering teams are also more empowered to take advantage of services offered by the cloud vendor, as they share DevOps responsibilities among the entire team.
In this talk, you’ll learn why it’s not serverless OR containers, it’s serverless AND containers.
GeekWire Cloud Tech Summit - June 27, 2018
At its core, serverless represents an evolution of cloud computing. In the early days, there were only virtual machines, and now there are containers, container orchestrators, serverless computing, and more. Even though serverless has created a big shift in how modern applications are developed, most applications are not architected in an entirely serverless way--nor should they be.
In fact, we’re seeing an emerging trend: applications now use a combination of serverless and containers. Each have their own strengths: when you want code to scale on demand, without explicitly provisioning compute resources, serverless is a good fit. For existing code, or when you need control over the execution environment, containers are a great choice. And, lightweight container services such as AWS Fargate and Azure Container Instances further blur the boundary between containers and serverless. Serverless is not all-or-nothing, it’s really a spectrum.
Through real application examples, this talk will describe guidelines for when to use containers and when to use serverless functions. Serverless and containers really are better together--learn how to have the best of both worlds!
Velocity 2018 - June 14, 2018
- Talk slides
- Example code! (Terraform, Serverless Framework, Claudia.js, Up, Pulumi)
At its core, serverless can be considered “service-full” computing, a trend that’s been around for a while. Instead of running your own Redis cluster, you use a managed cache service. Instead of running a database server on VMs, you use a database service. Serverless simply pushes this notion further: rather than keep a container active when it’s not processing requests, use a managed functions-as-a-service platform such as AWS Lambda, Azure Functions, or Google Cloud Functions.
This trend creates an architectural shift: strangely, your application becomes simultaneously simpler and more complex. Simplicity comes from managed services, which allow you to focus on your business problem instead of infrastructure. Complexity comes from the extra moving parts once you’re juggling dozens of services and hundreds of individual components. While managed services simplify your application, you must now control and understand each of them.
There are a growing number of tools that aim to wrangle this complexity. Of course, we’ve now traded one problem for another: determining which tools are best for your project, application, or organization—or if you even need a tool at all.
Tooling is necessary for serverless and service-full applications. Donna Malayeri shares a decision framework for choosing infrastructure deployment tools, based on whether you need flexibility and control or simplicity and ease-of-use. You’ll learn how to evaluate several popular cloud automation tools, including AWS SAM, Terraform, Chalice, Serverless Framework, Apex/Up, Claudia, kubeless, and Pulumi. Each of these tools offers something unique and is designed for particular problem spaces. There’s no one-size-fits-all answer and sometimes you’re better off with no tool at all.
GlueCon 2018 - May 16, 2018
As DevOps has evolved, developers are more often responsible for creating and managing the infrastructure their application code depends on. Unfortunately, cloud tools are designed around the previous ops model, where there were organizational silos between dev and ops teams. We’ll describe a novel idea: what if you could write code in a general purpose language, code that defines both your declarative infrastructure and your application logic? What if we go beyond the idea of infrastructure-as-code, and treat infrastructure as software? We’ll show how this approach creates a fundamental shift in the way in which modern cloud applications are designed and developed.
ProductTank Bellevue Meetup - Jan 24, 2018
In tech, the role of a Product and Program Manager is constantly evolving. Even within an organization, the role can be dramatically different, depending on the team and the product. Donna will talk about how the role evolved at Microsoft over the years, and what she's learned now from being at a startup. Then we'll lead an open discussion of how to adjust your role to suit your team and business needs.
Seattle Code Camp - Sep 9, 2017
Have you ever wondered why most big company product managers seem to be in meetings all day? Do you work effectively with your product manager? I’ll go through some areas that PMs typically manage and why they are important to your business. After this talk, you’ll learn about the many teams that contribute to the success of your product, such as marketing, evangelism, and sales. You’ll have an answer to the mystery of what all those meetings are for, and why Outlook is our IDE. Finally, you’ll learn how your PM can help you be even more effective.