Need advice about which tool to choose?Ask the StackShare community!
AWS Lambda vs Realm: What are the differences?
1. Scalability - AWS Lambda and Realm differ in terms of scalability. AWS Lambda is designed to automatically scale based on the demand and can handle a large number of requests without requiring any manual intervention. On the other hand, Realm's scalability is limited by the resources available on the device, as it operates locally on mobile or client-side devices and does not have the same level of automatic scalability as AWS Lambda.
2. Deployment - Another key difference between AWS Lambda and Realm is the deployment process. AWS Lambda allows developers to deploy their code onto the AWS cloud infrastructure, making it accessible through various triggers such as API Gateway or event sources. In contrast, Realm is primarily used for mobile or client-side applications and is typically deployed as part of the mobile app itself, eliminating the need for an external deployment process.
3. Complexity - While both AWS Lambda and Realm offer serverless functionality, they differ in terms of complexity. AWS Lambda provides a highly flexible and configurable environment for developers, allowing them to write complex serverless functions using various programming languages. On the other hand, Realm offers a simpler and more opinionated approach, focusing on client-side data synchronization and offline capabilities for mobile apps. This makes Realm easier to use for developers who are primarily focused on mobile application development rather than serverless architecture.
4. Pricing - AWS Lambda and Realm also differ in terms of pricing. AWS Lambda follows a pay-per-use model, where developers are only charged based on the number of requests and the execution time of their functions. On the other hand, Realm operates under a subscription-based pricing model, where developers pay a fixed monthly fee based on the number of users or devices accessing the Realm database. This pricing model may be more suitable for small to medium-sized applications with a predictable user base.
5. Integration - AWS Lambda and Realm differ in terms of integration capabilities. AWS Lambda can be easily integrated with other AWS services, such as Amazon S3, DynamoDB, or API Gateway, allowing developers to build complex serverless architectures. Realm, on the other hand, offers seamless integration with mobile development frameworks and provides SDKs for iOS, Android, and other platforms, enabling developers to easily incorporate data synchronization and offline functionality into their mobile apps.
6. Infrastructure management - Another key difference between AWS Lambda and Realm is the level of infrastructure management required. In the case of AWS Lambda, developers are responsible for managing and configuring the underlying infrastructure to some extent, such as specifying the amount of memory, setting up IAM roles, or defining environment variables. On the other hand, Realm abstracts away the infrastructure management aspect, allowing developers to focus more on app development rather than infrastructure setup and maintenance.
In summary, AWS Lambda and Realm differ in terms of scalability, deployment process, complexity, pricing, integration capabilities, and infrastructure management.
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 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 Realm
- Good7
- Elegant API3
- Cloud Syncing3
- React Native Support2
- Strong Adoption Growth1
Sign up to add or upvote prosMake informed product decisions
Cons of AWS Lambda
- Cant execute ruby or go7
- Compute time limited3
- Can't execute PHP w/o significant effort1
Cons of Realm
- No offline support for web till now1
Sign up to add or upvote consMake informed product decisions
What is AWS Lambda?
What is Realm?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with AWS Lambda?
What tools integrate with Realm?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+47
+43
+26
+23+42