November 6, 2023 By Jason McGee 3 min read

Over the past decade, we’ve seen serverless computing take the cloud computing world by storm. Serverless is a cloud computing application development and execution model that enables developers to build and run application code without provisioning or managing servers or backend infrastructure.

When developers first started using serverless technology, they were mostly only using it for Function-as-a-Service, or FaaS. This was useful for event-driven functions, but it was very limited. Recently, we’ve seen serverless expand far beyond FaaS: there is a lot more value by using this technology for more large-scale, compute-intensive workloads. This can include supporting large container-based architectures or even running batch jobs at scale.

As we head into KubeCon 2023, we’ve identified several trends to watch around serverless. We’ve also asked our colleagues at MongoDB to weigh-in with their thoughts on this transformative technology.

Serverless is a developer-first technology

As the role of the developer continues to evolve to meet increasing demands, it’s crucial for organizations to adopt technology that simplifies and enhances the developer experience. Serverless is one of those technologies that is improving developer efficiency. Since serverless platforms often utilize pre-made integrations, developers can quickly utilize application functionality and accelerate market deployment. It’s allowing them to push new boundaries without hindering performance.

At IBM, we’ve built a single, unified serverless platform that is driven by developers who liked the idea of not managing servers, but also disliked working within the small space that FaaS supports. It also allows them to concentrate on coding by freeing up time that was spent managing the infrastructure. IBM Cloud Code Engine takes serverless to the next level. With IBM Cloud Code Engine, developers have a single deployment experience whether they’re running containers, building and deploying source code, or submitting larger batch workloads to the IBM Cloud with a common API and user experience, from one management dashboard, leveraging a simple pay per use consumption model.

Serverless can prevent vendor lockin

IT professionals across industries have a desire for flexibility and adopting technology that don’t create vendor lock-ins. Recent IBM research found that nearly 80% of C-suite executives said workloads being completely portable with no vendor lock-in​ is important or extremely important to the success of their digital initiatives.

While some serverless technology is proprietary and creates vendor lock-in, recently there have been more serverless solutions built on open-source technologies such as Kubernetes, Istio, knative and Paketo. This means that the workloads running are more portable compared to the proprietary options. IBM believes that today’s organizations need to work with an ecosystem of partners to succeed, even if they’re competitors. Our partner ecosystem approach upends the traditional paradigm of competition, moving away from rivalries toward a more fluid and collaborative path to success. Through this lens, serverless can help put an end to complexities brought on by vendor lock-in.

Serverless supports compute intensive workloads

Enterprises today are rapidly adopting more compute intensive technology, such as High-Performance Computing (HPC) and AI. While these technologies can be incredibly valuable, the costs and skills associated with these solutions can prohibit adoption. For example, HPC users tend to have domain expertise — such as EDA, simulations, financial modeling — but they don’t have the skills to provision, manage and secure infrastructure. Serverless does all that for them. AI workloads need to come to the market quickly because of tremendous competitive pressures. They’re also usually very expensive, so businesses want an infrastructure that enables rapid enablement and pay-per-use models, which serverless achieves.

We also had Chris Shum, Director, Product Management, MongoDB weigh-in with his thoughts on where serverless is going:

“We’re seeing a paradigm shift where serverless is becoming a developer’s best friend for building modern applications. With databases being the backbone of applications it’s important that they too, embrace this shift to deliver a developer-first experience. At MongoDB, developer centricity is a cornerstone of who we are as a company and our mission is to make developers’ lives easier when working with data – so for us, embracing serverless is critical. Not only in ensuring our developer data platform, MongoDB Atlas, can be seamlessly integrated into serverless architectures but that the core tenets of serverless are also embedded into everything we offer. This enables developers to focus on what matters — building innovative applications rather than managing their database. Together with partners like IBM, we can give developers solutions to capitalize on the benefits of serverless with a modern, elastically scalable database alongside a fully managed containerized environment to run their code, so they can meet the demands of the most dynamic applications without being bogged down by infrastructure complexities.”

Meet us at KubeCon

Similar to previous KubeCons, the IBM booth will be the best place to meet and talk to IBMers, including the authors of this post. You can view and register for all the IBM sessions at KubeCon below.

Learn more about IBM Cloud Code Engine
Was this article helpful?

More from Cloud

Microcontrollers vs. microprocessors: What’s the difference?

6 min read - Microcontroller units (MCUs) and microprocessor units (MPUs) are two kinds of integrated circuits that, while similar in certain ways, are very different in many others. Replacing antiquated multi-component central processing units (CPUs) with separate logic units, these single-chip processors are both extremely valuable in the continued development of computing technology. However, microcontrollers and microprocessors differ significantly in component structure, chip architecture, performance capabilities and application. The key difference between these two units is that microcontrollers combine all the necessary elements…

Seven top central processing unit (CPU) use cases

7 min read - The central processing unit (CPU) is the computer’s brain, assigning and processing tasks and managing essential operational functions. Computers have been so seamlessly integrated with modern life that sometimes we’re not even aware of how many CPUs are in use around the world. It’s a staggering amount—so many CPUs that a conclusive figure can only be approximated. How many CPUs are now in use? It’s been estimated that there may be as many as 200 billion CPU cores (or more)…

Prioritizing operational resiliency to reduce downtime in payments

2 min read - The average lost business cost following a data breach was USD 1.3 million in 2023, according to IBM’s Cost of a Data Breach report. With the rapid emergence of real-time payments, any downtime in payments connectivity can be a significant threat. This downtime can harm a business’s reputation, as well as the global financial ecosystem. For this reason, it’s paramount that financial enterprises support their resiliency needs by adopting a robust infrastructure that is integrated across multiple environments, including the…

IBM Newsletters

Get our newsletters and topic updates that deliver the latest thought leadership and insights on emerging trends.
Subscribe now More newsletters