This is the sixth and final piece of our Modern Cloud series.

Modern Cloud has to represent value for the different personas across the business. The customer is an obvious one. But it's good to talk about internal stakeholders.  The CEO and Product personas are very interesting. I think we were happy talking about the Developer and CTO/Architect perspectives. They are our personas!

Wardley Mapping guides us towards our users and their needs. Having those conversations and distilling that down helps us with our thinking. And to articulate the benefits.  What are the good approaches for 'time to value'? And to realise the potential of modern cloud ecosystems. It's been useful to talk and clarify the mental model of what the cloud is and what it can be.  And what benefits teams and organisations following this path can get out of it. This has been democratised globally. If you pursue this properly, you can compete with anybody in the world.

When we started talking about the cloud we thought about building ephemeral event driven architecture. But our CEO was thinking, can you be faster and cheaper? It became a value proposition. Remembering some of those things is important! You need to keep that commercial lens as you design applications and processes. And as you build up teams. One thing that is interesting (we've been talking about it for a long time) is the term 'serverless'.  But the serverless term itself is problematic. One of the reasons why we use the term modern cloud is because Serverless has turned into a type of religious war. When people hear the word Serverless, they think of Lambda. But it's much more than that.

Lambda was the first 'go to' for ephemeral event driven or function based workloads. And it's been fantastic. But the ecosystem has evolved with managed services becoming available. And direct integration between managed services is available. So you don't need as much glue! You don't need to worry about operational burden or code liability. You can offload that to the cloud provider and to the services. Serverless, as a term, is probably coming to a close. It was a useful vehicle to describe what emerged. But it has gone through an evolutionary journey. Now, I think the term modern cloud supplants it.

Serverless exists within the IT org.  With the modern cloud, you are working with Product and Business.  And you need to start talking in the language of capabilities. You need to develop a ubiquitous language about building blocks to describe getting capability into production. We know what the modern cloud has under the hood. But we have to evolve to talk in business terms.  The well architected approach helps to frame it.  Is it secure and operationally excellent? Is it performing and reliable? Is it cost optimised and sustainable? Those capability conversations are supplanting the discussions on whether you are using serverless or not.

Another thing we have been thinking about is modern cloud versus legacy cloud. Legacy cloud is the traditional call stack in the cloud. There's a whole bunch of stuff that's going to be running hot all the time. It's really just stuff that should be in your data centre,  but it's now in the cloud. It's a very interesting question. It's quite a challenging question. But a lot of people look back at their traditional stack and suddenly realise it's actually a legacy monolith in the cloud.

A lot of people think transformation e

Serverless Craic from The Serverless Edge
Check out our book The Value Flywheel Effect
Follow us on X @ServerlessEdge
Follow us on LinkedIn
Subscribe on YouTube