The Pros and Cons of Azure Functions

Azure Functions has been gaining traction among developers, mostly led by .NET developers. Microsoft offers many different application deployment platforms including containers, PaaS, WebApps, Azure Functions, Azure Logic Apps and others. With such diverse portfolio, Microsoft is positioning Azure Functions as an enterprise grade Serverless offering. As a follow up to our posts on the…

Share this post

Pros & Cons of Google Functions

After the launch, Google Functions didn’t get any attention for sometime before the company started investing in the platform. While it is nowhere comparable to AWS Lambda in terms of the feature set or developer adoption, it has been slowly gaining traction. While Google Functions alone is not very interesting, the spectrum of services offered…

Share this post

Does Serverless Offer NoOps Nirvana?

As Serverless Computing gain traction in the industry, the industry conversation has moved towards whether Serverless is the NoOps nirvana we were expecting to happen in the cloud. When Platform as a Service (PaaS) gained traction in circa 2011, there was a talk of PaaS ushering in an era of NoOps, a result of the marketing campaign by…

Share this post

The Magic Of Autoscaling With Serverless

One of the advantages of Serverless touted by cloud providers is seamless autoscaling. Ever since cloud computing gained traction, autoscaling is seen as the biggest advantage organizations can leverage for unexpected traffic. Autoscaling was seen as a major leap from traditional IT where capacity planning is critical and resource inefficiencies (and hence increased costs) are the norm….

Share this post

Serverless Pricing Model: Does It Make Sense?

One of the biggest advantages of Serverless is its pricing model which is more fine-grained than VMs and Containers on the cloud. More importantly, one could see the real advantage of pay per use model in the case of Serverless than VMs and Containers because you are not continuously running these services and they come…

Share this post

State of OpenWhisk

OpenWhisk is the first Serverless platform that gained community traction when IBM pushed the platform to Apache Foundation. Licensed under the Apache license, the platform allows developers to deploy event driven applications on any infrastructure. This implies there is an operational overhead in running the platform compared to platforms like AWS Lambda, Catalyst, Google Functions,…

Share this post

Mitigating Serverless Challenges

While Serverless offer many advantages for the developers, it also imposes some constraints and challenges. Some of the architectural constraints imposed by the Serverless abstraction limits the type of applications that can be deployed on Serverless platforms. See this post about the difference between Microservices and Serverless Functions to understand where these two different architectures…

Share this post

Microservices & Serverless Functions – The difference

Modern developers often confront terms like microservices and serverless functions used in conversations, at times without much of delineation between the two terms. This has lead to some confusion among the developers, leading to picking the wrong technology stack for their needs. In this blog post, we will try to distinguish the difference between these…

Share this post

Knative: Is it ready for production?

As Kubernetes and AWS Lambda gained traction among developers, there was a clear need for a serverless abstraction on top of Kubernetes. Knative is an open source project, originally started by Google in collaboration with IBM, Red Hat and VMware, that provides an abstraction for developers to run their code without having to manage the…

Share this post

Event Driven Compute Using Zoho Catalyst

Today’s leading applications are so dynamic that sometimes it requires developers to use complex tools and infrastructural changes to adapt and facilitate them. Cases like running OCR on images, running filters and resizing images or even sentiment analysis on texts are very common use cases that require one part of the system to react to…

Share this post