Serverless computing is a cloud-native model where developers build and run applications without managing server infrastructure. It has largely become the standard approach to achieve scalability, often with reduced operational overhead. However, in banking and financial services, adopting a serverless model can present unique challenges. Brian McNamara is a distinguished engineer at Capital One, where he works in serverless integration and development. Brian joins the show with Sean Falconer to talk about why Capital One shifted to a serverless approach, how to think about cloud costs, establishing governance controls, tools to stay well-managed, and much more.
This episode is hosted by Sean Falconer. Check the show notes for more information on Sean's work and where to find him. Brian, welcome to the show. Hey, Sean. Thanks so much for having me. Yeah. So to start our conversation, can you explain a little bit about your role at Capital One? Sure. So I'm a distinguished engineer at Capital One. Essentially, that's a senior IC role. And my role really revolves around considering how we do serverless at scale, both at a tactical level and a strategic level. So at a tactical level, I have the opportunity to engage with different teams who are looking to adopt serverless compute, help them run through any outstanding questions that they might have around the technologies, help them decide which compute may be better for their given workloads.
But then we also have the opportunity on my team to actually work with others across the enterprise. So in terms of where I sit at Capital One, I'm in the retail bank, but I have the opportunity to really work with partners in other lines of business like our car business, enterprise, cyber, ML. So it's really nice to operate really both at a very high level and really very low level too. When you reach the level of distinguished engineer within an organization, is that kind of your primary thing that you're doing day-to-day? Instead of necessarily hand-on-keyboard coding, you're a little bit more like a thought leader within a company working with some of these other teams to help them invest in certain technologies where you have deep expertise in? I'll say yes, and. So one of the nice things about the distinguished engineer role at Capital One specifically is you do have the ability to influence really how a large engineering organization works or considers problems. So in that sense, we do get to work on the big boulders.
In my role, though, it's actually a really good blend in that I do get to get my hands on the keyboard. So while I may not support feature teams and actually write production code, I am working on ways, you know, whether it's in sample applications or templates, you know, looking for ways to help streamline the overall adoption of serverless like Cat1. Okay. And what would you say is kind of like the primary difference between operating at this level as an engineer versus, say, being at maybe like a senior staff engineer level? Yeah. So I think...
And I mean, obviously, this is my experience. It's the ability to influence strategy. I think it is one of the main differentiators. So while I do get to work with those future teams who are looking to adopt serverless compute, it's working with our partners across the enterprise, not just within a single line of business. And that really, I think, allows us to take a more holistic view in how our engineers approach solving business problems with serverless technology. I see. And why did Capital One decide to make this transition to serverless technology?
Great question. So, you know, if you look back at Capital One's history, we really started our cloud journey in 2014. And, you know, if we look at how we've adopted cloud technologies over the years, I think it followed more or less, I mean, I hate to say a traditional pattern, but, you know, you can look at initial efforts revolved around, you know, like literally lift and shift. So, you know, moving existing stacks from on-prem to the cloud. But really, as the years progressed, you know, our leadership was looking for ways to improve the overall developer experience and quite honestly, reduce developer burden, you know, letting the developers focus on what they do well.
So, you know, really in 2021, we made a declaration that we were going to be a serverless first company. And what that's meant is, you know, for newer projects, newer applications, not that you have to go serverless first, but, you know, serverless technologies like Lambda and like AWS Fargate should be considered first. And if we look at the reasons why, one of the canonical examples that people provide for, you know, why any organization goes serverless is lower cost. I think it makes sense to unpack that a little bit more. If we look at, you know, what's driving that cost, there are really three components. There's the engineering cost. There's the cloud infrastructure cost.
You know, and then there's the maintenance cost. If we look at the cloud compute cost, you may actually find that serverless, when compared with an equivalent or, you know, an analog for an instance-based compute, may actually be more expensive. So, you know, people often hold up cloud cost as a reason to not consider serverless. I think our leadership has looked beyond that and said, well, you know, really, if we look at what's really driving overall cost or, you know, the total cost of ownership, it's not necessarily only cloud cloud cost. We have to consider maintenance cost and the ability to innovate. And I think really that's what serverless provides. You know, if we look at the dimensions of what constitutes serverless compute, you know, really it's all about minimizing management cost.
So yes, there are servers and serverless, but you don't have to manage them. You don't have to patch them. You can have compute that scales to really, really high levels if needed, but can also scale down to zero if needed to. You know, you also have compute that really runs when it's needed to. So in response to business events and you have built in resiliency. So looking at, let's say, a service like AWS Lambda in particular, you get high availability out of the box. Whereas if you look at instance based compute, you know, you may need to consider like, OK, how resilient I want this application to be to different types of failures. Well, with a managed service like AWS Lambda, well, we as customers don't have to worry about that. We can let developers focus on the interesting problems.
the point you raised there about speed of innovation and being able to potentially plug and play different parts of the stack as essentially the public cloud introduces new technologies. It's a little bit easier to be adaptive versus if you are sort of running this stuff yourself, then in the same way that like a monolithic application, you end up with like this tight coupling of different services and it makes it hard to be essentially as adaptive because every team kind of needs to be in sync and it's going to really slow down your price. If you're running this yourself, you're almost like you're tightly coupling your software to the on-prem system that you're running versus having a little bit more of a decoupling between the service that you're creating and essentially taking advantage of something like public cloud. Does that make sense? Yeah, exactly. We're working with wonderful cloud partners like Amazon. This is a great time of year where we get to see what Amazon's been working on for the past year. It's always exciting knowing that we have a partner that's innovating on our behalf. Yeah.
And then some of the problems I've seen companies run into when it comes to actually like cloud costs being expensive comes from not really going through the process of rethinking or re-architecting the way that they are building and running their software to be best suited for the cloud, right? Legitimately just sort of lifting and shifting something into the cloud is not going to help you save money. You need to go through a process of sort of, you know, rethinking how those services are going to take advantage of the fact that not everything has to run in the cloud, like, you know, 100% of the time. And that's how you can actually help reduce your cost if you're optimizing for the things that the cloud is actually good at. Yeah, I would agree with that. And with like, you know, say land applications in particular.
Even when we see teams that are interested in moving from other compute to Lambda, there's this initial thought to build essentially like a monolithic Lambda or LambdaLith. And if they don't initially go through the process of decomposing their application, breaking down that monolith, they may find that Lambda may not be the right choice for any number of reasons. But I think for teams that take the time to consider what their applications do, how they're invoked, and really break things apart, they find that Lambda can really be a suitable landing place for me. So I believe you said that this sort of project kickstarted in 2021. So what is the status of things today in terms of Capital One's journey to serverless? Yeah, so we have a large number of applications that are, in fact, running on serverless compute. I can't share the exact numbers, but it's a non-trivial number. And what we've seen for the teams that have made the transition is that they are able to spend time or more time on adding business value, on delighting customers, and much less time on patching infrastructure or managing availability.
in the event, like, you know, as a part of our normal process of launching applications, we ensure that applications are resilient to different types of failures. Well, with serverless compute, that honestly becomes a lot easier. You know, we've talked about a couple of the advantages of serverless in terms of, you know, the team being able to work faster, be a little bit more adapted to changes in technology. Is there also an advantage in terms of, you know, bringing engineers into the organization where they might have experience with a lot of these services already, and it's kind of like the way that they're used to working? Yeah, I mean, I would say...
For us, as a large enterprise, we have about 14,000 engineers. So when we do bring new engineers on, it's often easy. Yes, as with any new hire, there is a ramp-up period. But we find that people are happy to embrace serverless technologies without necessarily being beholden to legacy architectures, figuring out what the right server is to jump to, and all those activities that don't necessarily add value. So we find that the more that we lean into managed services, the more productive our developers can be. And you don't have to share specifics, but can you help maybe for the audience shape?
the amount of data or traffic that you're dealing with and actually running through AWS? How big is this, essentially? So we are a very, very large AWS customer. Without going into specifics, I can say you can think of CapOne as a very, very large user of AWS, a strategic partner with AWS, akin to a Netflix. So we are all in on the AWS public cloud. In fact, we shut our last data center back in 2020. So really, whether it's serverless compute, instance-based compute, storage, we are very, very large users of AWS. And what are some of the high-use services that you use within AWS? What were some of the original workloads that you wanted to move over?
So we are large users of serverless compute, as you might imagine. But we do also have a large footprint in more traditional compute. So whether it's instance-based like EC2 or ECS on EC2, if you look at other services that are more serverless in nature, S3, we are very, very large users of S3. That powers a lot of our AI and data analysis workloads. Then there are the connective services like Amazon Simple Modification Service, Amazon Simple Queue Service. So really, we don't use all AWS services, but we do use a lot. And what we do use, we're pretty heavy users of.
As you might imagine, despite being, yes, we are a very, very innovative tech company, but we are a financial services company first. So we do have to be mindful in how services are approved and in how we govern usage within the developer community. Yeah, I'd love to get into details on that. But one thing before we jump there is, like with many industries, banking's gone through a lot of transformations, I think, over the last certainly 10 to 15 years. And I think one area that has changed banking significantly is around the fact that...
Now, if I'm a customer of Capital One, a lot of my access to my accounts is going to be coming from a mobile device. Whereas before, maybe I actually had to go into a bank or reach an ATM machine or something like that to make something happen. And I would think that that would have a pretty massive effect on the traffic that you end up seeing. Because I can essentially just be hitting that banking app multiple times a day, doing transfers, doing refreshes, all kinds of stuff that you never would have seen before. Yeah. So for us, we have recognized the industry changing from being exclusively to a physical experience to the virtual experience as well. And I think Capital One places a really high value on delaying customers wherever they are.
So whether it's in a retail bank itself, you know, whether you're a customer of a retail bank who uses our mobile app or, you know, our website or, you know, similarly a credit card holder, we want to meet you where you are. Yeah. And I guess some of the sort of elasticity of the cloud really helps with potentially spiky traffic. Yes. Yeah. And for, you know, you bring up a great point there. You know, I think when people were initially migrating to the cloud, like, you know, when you saw the public cloud become more of a thing, like, you know, in the mid, we'll say 2010s, where you saw larger businesses adopting cloud technologies.
I think the initial value that people held up was that you'll save money. And I don't know if that's necessarily true. I think what you're really buying is elasticity, you know, the ability to be wrong, right? You know, like if you think about what it takes, like the process of actually racking and stacking a physical server, like there's a whole lot that goes into that. And you better be right. You know, otherwise, you know, you're living with that decision for a non-treatening amount of time. I think what the cloud offers you is, you know, one, the ability to be wrong. So if you don't get, like, if you're looking at instance-based compute, you don't have to get it just right, right out of the gate. You know, it's just an API call to destroy that instance. It's an API call to create a new instance. But I think, you know, the point that you bring up about.
adjusting to customer demand and having that elasticity built in like even if you get that instance sizing right or the lambda you know function configured with just the right amount of ram well you may need to scale horizontally and i think that's really the power of the cloud you know we don't have to have capacity just waiting and with each type of compute that is offered by lab providers like amazon it's interesting to look at what the unit of scale becomes and how fast that unit of scale can be applied with services like lambda you can see the unit of concurrency which is really the unit of scale you know you get a large number in your account in your region out of the box But depending on your needs, you can work with Amazon to increase those limits as needed. And we've certainly seen use cases where we have had to go well beyond those account default limits. But beyond that, you're able to get more and more capacity and scale to really high levels pretty fast, too. Whereas even if you compare lambda scaling with, let's say, instance-based auto scaling, you're talking about potentially milliseconds or hundreds of milliseconds versus minutes. So it lets you more closely associate scale with the business value. You don't have to over-provision or worry that you're under-provisioned.
right what you need as you need it does working in a sort of these elastic service environments change the way that you have to think about monitoring and observability I'll say yes and no. So yes, you know, it doesn't change the need, right? There is a need to understand what's happening in your application. That need doesn't go away. Just because AWS is handling, you know, we'll say the underlying infrastructure, you know, it doesn't absolve you of making sure your applications are monitored appropriately. It does change how you do it or the mechanism that you use. So like in many regards, I think working in serverless environments forces you to be more disciplined in how you approach observability. You know, there's no instance SSHN2 or, you know, where you can run, you know, HTOP and see which processes are.
consuming cpu what you're you know we're running io stat or you know vm stat you don't have an instance right so like i think you do need to be more disciplined the good news is you know aws does provide you know a number of metrics out of the box whether it's to deal with concurrency performance you know like there are a number of metrics that are there but you also have the ability to add your own instrumentation as well so if you want to write custom metrics that are associated with let's say business user sign up you know user abandonment or you know deposits made like you have that ability right you know you can build that logic in itself and the nice thing is there's a really good vibrant community that has, I think, shown how to do this well. So whether it's using utilities provided by AWS. So I'll give a shout out to a capability that AWS offers called AWS Land of Power Tuning. Initially, Power Tuning was built to help with observability. So if you look at what the module provides, so there's Power Tuning for Python, Node, and for Java. The nice thing is logging, metrics, and traces are all first-class citizens in those modules. So you don't have to do a whole lot to get a lot of visibility, which is really nice. But if you wanted to embrace industry standards like open telemetry, you can do that too. And there is a good story for OTEL with Lambda in particular.
So if you want to instrument code, you can. Otherwise, you can lean into the SDKs to auto instrument code. Obviously, there are tradeoffs there. If you are using non-compiled language, auto instrumentation, you'll see a penalty at cold start. But you can do it. You don't have to be an OTL expert to get that visibility, which is great. So I wanted to talk a little bit about essentially governance and security compliance. Banking is a very regulated, sensitive industry. You have to take care of anything that you're building. Obviously, you're dealing in customer trust. How does that kind of change the way that you have to think about building products when you work at a bank?
Yeah. So, I mean, at Capital One, security is job one. As you point out, we are working in a regulated industry. We need to make sure that we're doing things the right way from a security standpoint, from a governance standpoint. What that means is that, you know, as new services are introduced, we may not be early adopters, right? We need to do evaluations to determine whether or not services have the necessary controls that we feel they need. So, you know, there's that part of it, making sure, you know, services are imbued with the necessary controls that we need internally. But beyond that, we need to make sure then that our process of building and deploying code.
also is very rigorous and stands up to compliance. So making sure that all artifacts are versioned, making sure, like some of the practices that we adhere to, we use tools like Open Policy Agent or OPA to make sure that anything that we deploy conforms with our policies, that we're not deploying services that we're not supposed to deploy, making sure that even for the resources that we can deploy, that they are compliant, that we're not using certain properties, or if we are using certain properties, that they're configured a particular way. So you can get really, really granular. And the nice thing is you can offload burden from your developers in figuring it out, right? Like, so we use OPA so that developers can deploy compliant applications. You know, it's an important part of how we deploy code. And in terms of, you know, the same care that you have to take when potentially adopting new services within AWS, like, what is that process like when you look at potentially bringing in, you know, a new library within natural source code that isn't something that was developed at Capital One Accru? Obviously, I'm sure you must have some checks in place to make sure that there's not some sort of malicious supply chain attack that is hidden within the library or a reference library or something like that.
So, you know, as a part of our security process, we do vet new libraries that come in. And we do have internal processes that continually check for vulnerabilities and notify teams when they're using modules that are no longer compliant because they may have a critical CDE. So, yeah, like we really try to secure the entire supply chain from build to deploy to, you know, really you're running applications as well. Like these governance controls that meet these standards without sort of compromising some of the speed and efficiency that you get from this serverless development environment. Yeah, it's I mean, it is certainly an interesting question.
There is this natural tension, I think, between developers who want to iterate fast and want to deliver and want to execute on the latest, greatest thing. But I think many of our engineers also recognize the importance of the work that we do, and they're willing to accept a certain trade-off there because we're dealing with people's money and their finances. We need to partner closely in engineering organizations or more developer-focused organizations. We have to partner with our developer experience teams, teams that are... actually you know managing the ci and cd processes we have to partner with our cyber teams we have to partner with our open source management teams there is a lot of coordination and you know i think if we consider you know all that's involved there you know really there is this effort to try to shift as much of that as possible away from our developers so in many respects you know we try to both shift left and shift right so like when we talk about centralized controls you know we want to make sure that our cicd pipeline is the choke point, you know, the ultimate decider to determine whether or not something can be deployed. Is it compliant? Is it secure? But we also want to minimize friction for our developers. So their day-to-day should not be spent wondering, am I doing this right? Am I doing this securely? And we do things internally. So like one of the nice things we've built, you know, we certainly lean into open source tooling, like I mentioned, open policy agent. We have the ability to let our developers determine, am I doing things in a secure and compliant manner? Or do I have to wait for something to go to a pipeline and see it fail? Ideally, we want to shift that left. So we use some internal tooling.
But we also do lean into tooling like AWS CFN Lint. So you can determine, like, for, let's say, cloud confirmation-oriented deployments, are the templates that you're deploying, are they syntactically correct? You know, is it valid YAML? Is it valid JSON? All the way down to, like, you know, are there rules or, like, you know, resources that you have to find? Are the properties that you're specifying valid? You can also lean in and write your own rules to determine, like, whether or not that template is compliant and, you know, add that to your CFN Lint run. So really, it's a really delicate balancing act, you know, making sure that we do, you know, provide our developers with the means to be agile.
iterate quickly while balancing the need to be secure, compliant, and well governed. What role does a strong notification messaging system play in this? For messaging systems, we think it's important that developers understand when things change, making sure that they have visibility into what has changed and why it's changed. Ideally, we would allow those developers to see notifications. When we move things, when we shift things right, when we have that central CIC-CD process, if things aren't going according to plan, if, let's say, builds fails, if deploys fail, making sure developers understand where the failures occur. And similarly,
you know, actually having that visibility tied back to shift left efforts as well. So like if resource that you're trying to deploy is not compliant, making sure they understand why and making sure that we have supporting documentation to help them understand how to get that non-compliant resource compliant. Do those notifications ever get too noisy? I'm not going to lie, it can be noisy for our developers, but the great thing is we have a really, really strong developer productivity group internally, and they're constantly looking for ways to improve that experience. Because it's one thing to see that a build failed, and you see this huge dump, and you wonder, how the heck am I going to troubleshoot this? They've been spending a lot of time in narrowing down where failures occur, making sure that messages are only as verbose as they need to be, and providing that supporting documentation. And also meeting your developers where they are. So whether you're looking at a build-build log, or whether you receive Slack node notification or an email node notification.
You know, just making sure that developers understand at that necessary point why things didn't necessarily go according to plan. What role does the servoist center of excellence play in all this? Yeah. So for an organization the size of Capital One, I think it'd be arrogant to say, I know, you know, like what our developer community needs. And, you know, like I'm the only one who can speak authoritatively because I am not like I'm not at all. Different lines of business have different priorities and they have different needs. So really what the center of excellence allows us to do is group people, you know, like people who have an interest in improving the servoist developer experience, letting them come together.
and share like what's working, what's not, what are the pains, what can be done, you know, like how do we appropriately leverage the knowledge and experience that we may have as a group of domain experts to improve the lives of all developers, whether or not you have that domain expertise. And also really like I think work with other teams outside of, let's say the service center of excellence, work with cyber partners, work with enterprise partners, work across multiple lines of business. So really, it's a good platform to receive feedback from the developing community, but also influence how other teams consider the work that we do as developers. When you talk about the developer community, you're talking about the internal developers at Capital One, is that right? Yeah. How big is that, roughly? There are about 14,000 developers at Capital One. OK, so a good-sized community. Yeah, yeah. Going back to some of the things that we were talking about in the beginning there in terms of some of the reasons for moving to a serverless for Capital One, what were some of the challenges with actually putting that migration in place?
Yeah, I think there are a few. One, I would say, is plain old FUD, you know, fear, uncertainty, and doubt. You know, I think people for a long time have associated Lambda with, I mean, like, I hate to say toy applications, but, you know, we'll say, like, operations-oriented things that may not be business critical. Lambda doesn't scale like I need it to scale. You know, there's no way I can run my application in Lambda. You know, like, initially, you know, five minutes isn't enough, 15 minutes isn't enough. You know, I need more resources. I think developers will be surprised at, you know, the workloads that can be handled by serverless compute like Lambda.
The other important thing to note, too, is that we're really big on saying we're serverless first, but we're not serverless only. There are going to be certain workloads that are not suited for Lambda that are not, you know, like if they're not well suited for Lambda, we would ask teams to look at, you know, serverless container services like Farf Bargate. But even beyond that, like if a service is not right, like we have the means to support other compute and other services as well. But I think the biggest issue is helping overcome a lot of FUD, even helping teams understand what good looks like. So what I mean by that is, you know, earlier you mentioned, like, how does observability change? Well, we want to make sure that teams are empowered to know how their serverless applications are running. When it comes to things like, you know, splitting apart the monolithic application, what's the right way to do it? When is the right time to do it? How does your Lambda function scale? Like, how does your application traffic change over time? Are serverless services like Lambda able to keep up with what you need? So really.
Overcoming FUD, but then ultimately just doing the hard analysis to say like is lambda right for you if it is great If it's not that's okay to for those teams that that did decide to make the plunge Yeah, I think it was initially a struggle to help them understand like what the different metrics really meant so you know, for non-circleless compute, a really common metric, let's say for APIs in particular, is, you know, requests per second or transactions per second. And in Lambda, if you look at the unit of scale, it's concurrency, which is really a product of, you know, the number of requests that come in, so that RPS, that TPS, but also duration. How long does that Lambda function run for? And the goal is to minimize the amount of concurrency that your function's consuming. With that, it's a matter of helping teams understand, like, what's the right way to impact performance? And in Lambda, really, there's only one knob to turn.
And that's memory. So with lambda functions, you'll find that both memory and CPU scale together linearly. So like a 256 meg lambda function has twice the compute and RAM has a 128 meg lambda function. So for some teams, we would see them come in and, you know, allocate, you know, 10 gigs of RAM. Like I need all the RAM in the world. When you look at what they're actually consuming, it's like, you know, drop in the bucket. Maybe we ratchet that down. But we also saw a lot of teams under allocate the amount of RAM. So, you know, like knowing what the calculation is for lambda functions, you have indications.
There's a number of invocations. That's a component of the price. But then there's the amount of RAM consumed and the duration that that RAM is consumed for. And we would see teams allocate like 120 megs. That's the minimum RAM that we can allocate. So I'll do that and I'll save all this money. Well, what we would see is teams would actually starve their Lambda functions. So functions would actually run longer because they didn't have the necessary resources. So the great thing is there are open source tools. AWS Lambda Power Tuner is a great open source tool. If you're not using it and you're a Lambda shop, please use it. Alex Castleboney was a solutions architect at AWS at the time, wrote it. It is awesome.
And it really helps you determine what's that right number based on either cost or performance needs. So you actually can dial that in a lot more. You're not wasting resources or money. When it comes down to teams having to make decisions about is serverless the right thing to use versus using something like Fargate, what's the framework for making that decision? Yeah, like I would say first, consider the AWS constraints. Like, do you have a function, like, do you have a workload that needs to run consistently for more than 15 minutes? If so, you know, Lambda's not right for you. Do you have the need to consume more than 10 gigs of RAM? If so, Lambda's not right for you, right? Like, there's some easy ones to look at, but it's interesting when you consider then too, like, you know, beyond those obvious constraints, looking at things like, well, what is your Lambda function being triggered by? And what I mean there is like, you know, Lambda is event-driven compute. It'll be, you know, your code is, you know, is triggered in response to an event. And AWS has, you know, over 100.
event sources that can trigger Lambda functions. But let's say you're using, you know, you want to write a Lambda-backed API, and you're using, let's say, ALB, Amazon's Application Load Balancer Service. Well, that's a synchronous indication of a Lambda function. Now, Lambda can handle a 6 meg payload size at this time. But ALB can only pass in one meg and one meg in, one meg out. So if you were writing an API and you need to handle more than one meg in or one meg out, Lambda may not be the right choice if you're using ALB. With a service like Amazon's API Gateway REST service, that number jumps up to the full six meg. So API Gateway can handle 10, 10 meg, but you're going to be constrained by the six meg Lambda limit. So look at the obvious things like, hey, what are the physical constraints? Consider what you're looking to integrate with. Beyond that, though, it really gets interesting.
One common thing that comes up that would drive someone away is, you know, I have a Java application, you know, the Java will never run well in Lambda. Well, I would ask you to revisit your assumptions. You know, there are ways to mitigate things like cold start pains. Consider how often things like that, you know, those cold starts happen. Like, is it something that's happening a lot or not? If it's, you know, if it's a synchronous invocation where you have a user on the other end of that request, that cold start may really matter a lot more than an asynchronous invocation. Like someone uploads an object to S3, well, you know, you're not, you may not have somebody waiting on the other end of that request. So if you have a cold start that takes a little while, so what? You know, like it may not matter as much. The other thing too is, I mean,
The AWS Lambda team has worked really, really hard over the years to improve that developer experience for, let's say, Java in particular. So you can use services or capabilities like provision concurrency, where you essentially have an AWS management capability that will keep a certain number of Lambda execution environments warm. So you won't have those cold cold starts for the number of provision concurrent units that you've set. Last year, Amazon also introduced a capability called Snapstart for Java. And I'll be honest, I need to revisit the exact Java version. I want to say Java 17 and higher. I need to double check. But this year, they actually introduced that for Python as well as a pre-invent announcement.
So, you know, AWS is looking for ways to improve that developer experience and help developers, you know, force them into making a tough choice. Like, is Lender right? Where do you think reInvent's going on this week? There's lots and tons of announcements. Like, where do you think, you know, serverless is going in the next couple of years? Interesting places. So, like, one of the more interesting announcements I heard this week was on DSQL Aurora. Like, that, I think, is going to be massive in ways that we can't yet comprehend. That's one. I think durable workflows will be another area. So, like, if you consider how important it is for certain workloads to run to completion.
When you have ephemeral compute services like Lambda, state becomes really important. So how do we do that for a really important look? That's going to be another one. I think continuing to manage the software supply chain is going to be really important too and providing visibility into that. And I think the last I would say, improving the operator experience. One thing that makes me shudder is when people say serverless is no ops.
It absolutely is. Like, it doesn't absolve you from your operational responsibilities. The good news is, you know, as your cloud provider, whether it's AWS, Google, Azure, or anybody else, they're assuming more of the responsibility. But it doesn't mean that you don't have any responsibilities. So, like I would say, I would look for ways to improve the understanding of what's happening in applications. So the ability to observe what's happening is going to be really important. Yeah. Well, I know we're coming up on time here, Brian. I want to thank you so much for coming on the show. I really enjoyed this. Yeah, Sean. Thank you so much for the invitation. I really enjoyed the conversation. Cheers.