Serverless Ninja: Serverless = Efficiency

This article aims to explain how organizations and individuals can benefit from the efficiency that serverless architectures offer. It contains the top 4 cost centers where serverless can help in eliminating cost.

Elimination of Server Management Cost

Serverless architectures do not require developers neither organizations to manage underlying infrastructure. On the other hand, AWS handles the server management activities on our behalf so that we can focus on writing our application's features and capabilities.

Since serverless-based systems do not require organizations to manage servers. Organizations achieve cost-efficiency in spending money involved in the following activities:

  • Managing Cluster Scalability
  • Implementing Risk Mitigation
  • Implementing Disaster Recovery Strategy
  • Patching Security Vulnerabilities
  • Installing Operating System Updates
  • Hiring Server Management Staff

Reduced Security Risk & Cost

One cool side-effect of letting AWS manage the underlying infrastructure is the reduction in terms of security risk and cost associated with it. If we think about it, AWS hires top of the line security and infrastructure engineers. Utilizing serverless architectures is almost similar to asking these world class professionals to manage our infrastructure which ultimately results to cost and risk reduction in the security department.

Reduction in Compute Bills

Since AWS Lambda's billing mode require us to pay for actual execution usage time, we can save a significant amount of money by eliminating cost generated by:

  • Idle Compute Time (Payment made for time where servers' aren't processing invocations.)
  • Compute Time for Failover Servers (Payment for server redundancy and disaster recovery)

Reduction in Development Cost and Time

Since Lambda-based APIs allow us to focus on building our application. We can save the budget that we use to spend on:

  • Activities related to provisioning servers
  • Testing cluster scalability & resiliency
  • Designing and implementing disaster recovery systems

Since we can now delegate these activities to AWS, we can safely say that we are also reducing the time to deliver production software.

I'm writing a book about serverless!

If you are interested to learn more about serverless architectures, you can visit my github repository and read more about topics that I haven't published in this blog yet. You can also find interesting sample code and projects that can help you get started with serverless architectures.

Relevant Links

Get Some Cool Stuff From Amazon!

Comments

  1. James AnthonyNovember 24, 2021 at 12:52 PM

    If your company is struggling financially, despite your best efforts to turn things around, voluntary liquidation may be your best option. https://www.cfsredundancypayments.co.uk/

    ReplyDelete

Post a Comment

Popular posts from this blog

Microservices: Picking the .NET Framework for your containerized applications.

Image
The objective of this blog post is to explain the factors that should be considered when picking a framework for a .net application that you intend to deploy in containerized fashion. .Net Core Generally, .Net Core is the preferred option when building applications that were intended to be deployed in containers due to the fact that .Net Core is built using modular architecture (.net core app images contains only the dependencies it requires to run). .NET Core apps are packaged using Windows Nano Server which is a far smaller compared to the OS required by the standard .NET runtime (Windows Server Core) therefore producing lighter images (end product of building containerized application). On the image above, you will see an image built for .Net Core app that prompts "Hello World". Please take note of the size of the image (251 MB) as it would be critical to demonstrating the difference of the two frameworks. Download Demo Apps from GITHUB
Read more

API Gateway in a Nutshell

Image
In this article, we will explore what are API gateways, the use-cases that you wanna solve with it and the benefits that you rip out of using them. This will be an introductory post to a series of articles that will showcase API gateway development using ASP.net Core, NodeJS and Docker. Articles in the Series This article belongs to a series of articles that explains the importance of API gateways and how to build them using ASP.net Core. If you're interested to learn more about API gateways, it might be a good idea to spend some time reading the articles listed below. Part 1: API Gateway in a Nutshell. Part 2: Building Simple API Gateways with Ocelot. Part 3: API Response Aggregation using Ocelot Part 4: API Def
Read more

API Gateway: Response Aggregation with Ocelot and ASP.net Core

Image
In the previous article , we've learned how to setup an API gateway using ASP.net Core and Ocelot. This article supplements the previous article by introducing downstream response aggregation through the use of API gateways. You can download the application used in this article by cloning it from GITHUB . Articles in the Series This article belongs to a series of articles that explains the importance of API gateways and how to build them using ASP.net Core. If you're interested to learn more about API gateways, it might be a good idea to spend some time reading the articles listed below. Part 1: API Gateway in a Nutshell. Part 2: Building Simple API Gateways with Ocelot. Part 3: API Response Aggregation using Ocelot P
Read more

Security: HTTP headers that expose web application / server vulnerabilities

Image
Today's blog post will cover how ASP.net response HTTP headers can expose security holes in your web application and servers. The post will also contain steps on how to remove this headers and mitigate chances of getting attacked using C# and ASP.net MVC. Problem When an attacker performs an attack on a web server, the first thing he /she needs to do is to identify the profile of his target. To profile a target web application / server, an attacker would have to perform the following steps: Identify the address of the web application. Identify the OS where the web application resides Identify the type of server (IIS, Apache, etc) that was hosting the web application Identify the frameworks (ASP.net MVC, PHP, JSF) used by the applications After an attacker gathers the following information, the attacker would proceed on using penetration to
Read more