Using a serverless content management system (CMS) should ensure that developers can concentrate on what they are there to do – write code. It can remove the burden of running back-end infrastructure and let other teams manage the content that is put in place.
You can attend the Serverless Architecture Conference and the API Conference either on-site in The Hague or remotely from your home office on April 4 – 6, 2022. Learn from innovators and experts in their field, discover best practices, and expand your horizons about serverless and API tech.
You can attend the Serverless Architecture Conference and the API Conference either on-site in The Hague or remotely from your home office on April 4 – 6, 2022. Learn all about best practices from the experts, attend sessions, keynotes, and workshops, and network with professionals in your field!
Erez Berkner, the co-founder and CEO of Lumigo, spoke with JAXenter about the cloud observability space, elaborating on what it’s trying to solve and how it’s different from monitoring. He explains in detail how Lumigo helps make sense of the ever-growing complexity of cloud-native applications and allows developers to find the root cause of an issue in highly-distributed systems. Erez explains Lumigo’s decision to expand to Kubernetes and hybrid apps and reveals the company’s plans for further down the road.
As the industry moves towards DevOps, full-stack, and Serverless, there is a responsibility for the application team to do everything. Every data service will now start to claim serverless. Let’s explore the seven tenets of serverless data and hopefully provide some guidance about data in a serverless architecture.
We chatted with Jonas Bonér, CEO and Founder of Lightbend about Akka Serverless and what makes it so different from other architectures. Jonas explains how data is kept secure in Akka Serverless and what limitations it removes with its data-centric backend application architecture.
We spoke with Veselin Pizurica, CTO and co-founder of Waylay about the serverless paradigm. What concerns do enterprises have regarding serverless adoption and security issues, how can they achieve monitoring and observability of serverless applications, and how will the world of serverless evolve?
We spoke with Matt Biilmann, CEO and co-founder of Netlify about Jamstack and why it is such a strong stack for the serverless model. Discover what some of the current challenges are for serverless models, how to overcome them, and see what the future holds.
It is no secret that our world is changing. This article will explore how using a combination of Knative, the Kubernetes-native serverless platform, and Quarkus, Red Hat’s container-native approach to Java, can be used together to help simplify the modernization of application delivery.
We are just beginning to enter a new world of ubiquitously accessible client-serverless applications. Just like the client-server and three tier architectures did, the client-serverless application model will create tremendous opportunity (and disruption) for every kind of customer and vendor in the industry.
Serverless is a relatively novel concept and cloud architectural model but has been advancing very quickly over the past 5 years. In this article, we’ve compiled a list of recent changes that are likely to shape how development teams use serverless in practice.
The Thundra Application Observability and Security Platform was originally developed inside Opsgenie and spun off in 2018. In this article, we will go into detail about Thundra’s features. We will be using a real-life example of a serverless application and show how to boost its visibility by using distributed tracing.
A shortage of resources always leads to searching for alternatives and solutions. This is also one of the key reasons behind the adoption of serverless: it makes developers more productive and speeds up time-to-market.
In this session from the API Conference, you will learn about the benefits of serverless for startups and why Laserhub sees a lot of potential by adopting Serverless Framework in early use cases. By limiting the scope of serverless, we balanced risk and value add, but entered a new world for development and DevOps within two weeks.
