Need advice about which tool to choose?Ask the StackShare community!
AWS Lambda vs Apache OpenWhisk vs Serverless: What are the differences?
- Execution Environment: AWS Lambda provides a managed environment where users can upload their code without worrying about infrastructure management, whereas Apache OpenWhisk allows users to bring their own execution environment, giving more control over dependencies and configurations. Serverless, on the other hand, is a framework that supports multiple cloud providers, including AWS Lambda and Apache OpenWhisk, allowing users to switch easily between different providers.
- Programming Language Support: AWS Lambda supports a limited number of programming languages such as Node.js, Python, Java, and C#, while Apache OpenWhisk has broader support for languages like Node.js, Python, Java, Swift, and PHP. Serverless, being a framework, can support multiple languages as it abstracts the underlying provider-specific details, making it easier for developers to work with different languages across different providers.
- Request Handling: AWS Lambda supports synchronous and asynchronous invocations where events trigger the execution of functions, while Apache OpenWhisk uses triggers and rules to manage event-driven executions. Serverless abstracts the underlying event handling mechanism, allowing developers to focus on writing functions without worrying about event configurations.
- Scalability: AWS Lambda automatically scales the invocation of functions based on demand without any configuration needed from the user, whereas Apache OpenWhisk provides more control over scalability through the configuration of limits and concurrency. Serverless abstracts the scalability requirements, making it easier for developers to deploy scalable applications without manual intervention.
- Pricing Model: AWS Lambda offers a pay-per-use pricing model where users only pay for the compute time consumed, while Apache OpenWhisk follows a similar pricing model but with more flexibility in resource allocation. Serverless integrates with the pricing models of different cloud providers, allowing users to take advantage of cost-efficient strategies across multiple providers.
In Summary, the key differences between AWS Lambda, Apache OpenWhisk, and Serverless lie in their execution environment, programming language support, request handling methods, scalability options, and pricing models.
Need advice on what platform, systems and tools to use.
Evaluating whether to start a new digital business for which we will need to build a website that handles all traffic. Website only right now. May add smartphone apps later. No desktop app will ever be added. Website to serve various countries and languages. B2B and B2C type customers. Need to handle heavy traffic, be low cost, and scale well.
We are open to either build it on AWS or on Microsoft Azure.
Apologies if I'm leaving out some info. My first post. :) Thanks in advance!
I recommend this : -Spring reactive for back end : the fact it's reactive (async) it consumes half of the resources that a sync platform needs (so less CPU -> less money). -Angular : Web Front end ; it's gives you the possibility to use PWA which is a cheap replacement for a mobile app (but more less popular). -Docker images. -Kubernetes to orchestrate all the containers. -I Use Jenkins / blueocean, ansible for my CI/CD (with Github of course) -AWS of course : u can run a K8S cluster there, make it multi AZ (availability zones) to be highly available, use a load balancer and an auto scaler and ur good to go. -You can store data by taking any managed DB or u can deploy ur own (cheap but risky).
You pay less money, but u need some technical 2 - 3 guys to make that done.
Good luck
My advice will be Front end: React Backend: Language: Java, Kotlin. Database: SQL: Postgres, MySQL, Aurora NOSQL: Mongo db. Caching: Redis. Public : Spring Webflux for async public facing operation. Admin api: Spring boot, Hibrernate, Rest API. Build Container image. Kuberenetes: AWS EKS, AWS ECS, Google GKE. Use Jenkins for CI/CD pipeline. Buddy works is good for AWS. Static content: Host on AWS S3 bucket, Use Cloudfront or Cloudflare as CDN.
Serverless Solution: Api gateway Lambda, Serveless Aurora (SQL). AWS S3 bucket.
When adding a new feature to Checkly rearchitecting some older piece, I tend to pick Heroku for rolling it out. But not always, because sometimes I pick AWS Lambda . The short story:
- Developer Experience trumps everything.
- AWS Lambda is cheap. Up to a limit though. This impact not only your wallet.
- If you need geographic spread, AWS is lonely at the top.
Recently, I was doing a brainstorm at a startup here in Berlin on the future of their infrastructure. They were ready to move on from their initial, almost 100% Ec2 + Chef based setup. Everything was on the table. But we crossed out a lot quite quickly:
- Pure, uncut, self hosted Kubernetes — way too much complexity
- Managed Kubernetes in various flavors — still too much complexity
- Zeit — Maybe, but no Docker support
- Elastic Beanstalk — Maybe, bit old but does the job
- Heroku
- Lambda
It became clear a mix of PaaS and FaaS was the way to go. What a surprise! That is exactly what I use for Checkly! But when do you pick which model?
I chopped that question up into the following categories:
- Developer Experience / DX 🤓
- Ops Experience / OX 🐂 (?)
- Cost 💵
- Lock in 🔐
Read the full post linked below for all details
Pros of Apache OpenWhisk
- You are not tied to a provider. IBM available however4
- Still exploring... its just intresting3
Pros of AWS Lambda
- No infrastructure129
- Cheap83
- Quick70
- Stateless59
- No deploy, no server, great sleep47
- AWS Lambda went down taking many sites with it12
- Event Driven Governance6
- Extensive API6
- Auto scale and cost effective6
- Easy to deploy6
- VPC Support5
- Integrated with various AWS services3
Pros of Serverless
- API integration14
- Supports cloud functions for Google, Azure, and IBM7
- Lower cost3
- Auto scale1
- Openwhisk1
Sign up to add or upvote prosMake informed product decisions
Cons of Apache OpenWhisk
Cons of AWS Lambda
- Cant execute ruby or go7
- Compute time limited3
- Can't execute PHP w/o significant effort1
Cons of Serverless
Sign up to add or upvote consMake informed product decisions
What is Apache OpenWhisk?
What is AWS Lambda?
What is Serverless?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Apache OpenWhisk?
What companies use Serverless?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Apache OpenWhisk?
What tools integrate with AWS Lambda?
What tools integrate with Serverless?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+47
+43
+26
+23+42