Sign up to save your podcasts
Or
Share Diving Deep Into Serverless Architectures (2/2)
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
Diving Deep Into Serverless Architectures (2/2)
This episode is sponsored by The Chief I/O.
The Chief I/O serves Cloud-Native professionals with the knowledge and insights they need to build resilient and scalable systems and teams. Visit The Chief I/O, read our publication, and subscribe to our newsletter and RSS feed. You can also apply to become a writer.
Visit www.thechief.io.
The global serverless architecture market size is projected to grow from USD 7.6 billion in 2020 to USD 21.1 billion by 2025, at a Compound Annual Growth Rate of 22.7% during the forecast period.
The major factors driving the growth of the serverless architecture market include the rising need to shift from Capital Expenditure (CapEx) to Operating Expenditure (OpEx) by removing the need to manage servers, thereby reducing the infrastructure cost.
This is what "MarketsAndMarkets" research company states in one of its reports about Serverless.
The expected rise of Kubernetes may make some of us think that Serverless is just a hype that will disappear with the emergence of more robust frameworks and architectures, but the industry trends show that this is wrong.
Serverless has discerned how to adapt to the competitiveness of distributed systems such as Kubernetes. Instead of disappearing and giving up space to such technologies, Serverless has followed the wave and found its niche. If we take the example of AWS Fargate, Google Cloud Run, or Knative, we will surely realize that.
It is possible to run Serverless in public or private clouds, using a micro VM technology like Firecracker or a containerization technology like Docker running on top of a Kubernetes based cluster.
In short, serverless made it through the storm and gained wide recognition.
This is part 2 of our series about Serverless. In part 1, we discussed technical details about Serverless use cases, best practices, and productization. Today, we are going to continue in the same direction but in a different way, so stay tuned.
Wisdom and experience dictate that before taking any application to production, you must ensure that it is fully observable, both at a component level and end to end.
This practice applies to serverless too. However, the abstraction and complexity of the Serverless architecture make monitoring, observability, and debugging a real challenge. Most remarkably, you don't have a full overview of every part of your system.
This gets even worse when you run multiple serverless functions that work together.
For the same reasons, the Serverless ecosystem has seen the birth of different Serverless monitoring solutions like Dashbird.
That was Taavi Rehemägi - CEO & Co-Founder of Dashbird. As a founder of a Serverless monitoring startup, we're excited to have him as our main guest today.
We wanted to learn his vision about Serverless Architectures and the challenges around using it. We would like to understand the use cases, best practices, and his experiences as an entrepreneur in the DevOps and Cloud-Native space.
View all episodes
By FAUN
5
22 ratings
This episode is sponsored by The Chief I/O.
The Chief I/O serves Cloud-Native professionals with the knowledge and insights they need to build resilient and scalable systems and teams. Visit The Chief I/O, read our publication, and subscribe to our newsletter and RSS feed. You can also apply to become a writer.
Visit www.thechief.io.
The global serverless architecture market size is projected to grow from USD 7.6 billion in 2020 to USD 21.1 billion by 2025, at a Compound Annual Growth Rate of 22.7% during the forecast period.
The major factors driving the growth of the serverless architecture market include the rising need to shift from Capital Expenditure (CapEx) to Operating Expenditure (OpEx) by removing the need to manage servers, thereby reducing the infrastructure cost.
This is what "MarketsAndMarkets" research company states in one of its reports about Serverless.
The expected rise of Kubernetes may make some of us think that Serverless is just a hype that will disappear with the emergence of more robust frameworks and architectures, but the industry trends show that this is wrong.
Serverless has discerned how to adapt to the competitiveness of distributed systems such as Kubernetes. Instead of disappearing and giving up space to such technologies, Serverless has followed the wave and found its niche. If we take the example of AWS Fargate, Google Cloud Run, or Knative, we will surely realize that.
It is possible to run Serverless in public or private clouds, using a micro VM technology like Firecracker or a containerization technology like Docker running on top of a Kubernetes based cluster.
In short, serverless made it through the storm and gained wide recognition.
This is part 2 of our series about Serverless. In part 1, we discussed technical details about Serverless use cases, best practices, and productization. Today, we are going to continue in the same direction but in a different way, so stay tuned.
Wisdom and experience dictate that before taking any application to production, you must ensure that it is fully observable, both at a component level and end to end.
This practice applies to serverless too. However, the abstraction and complexity of the Serverless architecture make monitoring, observability, and debugging a real challenge. Most remarkably, you don't have a full overview of every part of your system.
This gets even worse when you run multiple serverless functions that work together.
For the same reasons, the Serverless ecosystem has seen the birth of different Serverless monitoring solutions like Dashbird.
That was Taavi Rehemägi - CEO & Co-Founder of Dashbird. As a founder of a Serverless monitoring startup, we're excited to have him as our main guest today.
We wanted to learn his vision about Serverless Architectures and the challenges around using it. We would like to understand the use cases, best practices, and his experiences as an entrepreneur in the DevOps and Cloud-Native space.