Serverless Costs
In Part 2: Serverless Scales I briefly touched on how a serverless architecture can have a cost benefit. In this post, I will go over: How to approach and analyze the cost of serverless, Two detailed examples of a cost analysis.
The latest News and Information on Cloud monitoring, security and related technologies.
In Part 2: Serverless Scales I briefly touched on how a serverless architecture can have a cost benefit. In this post, I will go over: How to approach and analyze the cost of serverless, Two detailed examples of a cost analysis.
In Part 1: What is Serverless? I talked about how one of the biggest pros to a serverless architecture is how well it scales and how high availability is baked in. In this post I’ll go over: How a traditional highly available scalable architecture works, How a scalable serverless architecture works, How you can benefit from a serverless architecture.
In this post we’ll answer the following questions: What is serverless architecture? (and what it’s not), What are the pros & cons of serverless?
One of the biggest challenges in a self-provisioned, public cloud environment like Amazon Web Services (AWS) is finding the right balance between resources, performance, and cost. With no initial visibility into usage stats, AWS customers tend to overprovision compute, storage, and database resources to cushion sudden spikes in demand. If users could see resource usage, they'd be able to determine if the numbers provisioned are really in line with the application workload.
Developers working hand in hand with IT professionals is vitally important to maintaining stable application environments with mininal errors. Ideally, they work in the same environment. This is called DevOps. Learn why DevOps and collaboration is necessary.
Function as a service (FaaS) products like AWS Lambda, Azure Functions, and Google Cloud Functions have instigated a paradigm shift in the way Ops teams provision and manage their organization's infrastructure. With everyday administrative tasks like provisioning, patching, maintaining compliance, and configuring operating systems all being abstracted away, your Ops team only has one task to work on - writing world-class code.
Back in 2016, AWS extended the resource ID length from 8 characters to 17 characters. Back then, this change applied to EC2 instances, EBS snapshots, EBS volumes, and EC2 instance reservation IDs. Now they’re doing it again with the remainder of EC2 resource types.
This small release introduces custom stages, stage-level configuration overrides, instant rollbacks and a few other refinements for Up the serverless deployment tool.