Need advice about which tool to choose?Ask the StackShare community!

AWS Lambda

23.6K
18.4K
+ 1
432
Sequelize

861
1.4K
+ 1
143
Add tool

AWS Lambda vs Sequelize: What are the differences?

Introduction:
AWS Lambda and Sequelize are two popular technologies used in cloud computing and database management. Here are the key differences between AWS Lambda and Sequelize:

1. **Execution Environment**:
AWS Lambda is a serverless computing service that allows developers to run code without provisioning or managing servers. On the other hand, Sequelize is an ORM (Object-Relational Mapping) that simplifies database interactions by mapping database rows to objects in Javascript.

2. **Scaling**:
AWS Lambda automatically scales based on the incoming traffic, allowing high availability and performance without manual intervention. In contrast, Sequelize does not have built-in auto-scaling capabilities, and developers need to manage the scaling of database resources manually.

3. **Pricing Model**:
AWS Lambda follows a pay-as-you-go model, where you only pay for the actual compute time consumed by your code. Sequelize, being an open-source library, is free to use but may involve costs related to managing the underlying database services.

4. **Functionality**:
AWS Lambda is primarily used for event-driven and serverless applications, where code is executed in response to specific triggers. Sequelize, on the other hand, focuses on data modeling and querying in relational databases, enhancing the development of database-driven applications.

5. **Vendor Lock-in**:
Using AWS Lambda ties you to the AWS ecosystem, making it difficult to migrate to other cloud providers. Sequelize, as an ORM, offers more flexibility in terms of database choices, allowing developers to switch between different databases without much hassle.

6. **Community Support**:
AWS Lambda has a large and active community that provides resources, tutorials, and support for developers. Sequelize also has a strong community backing but might not be as extensive as that of AWS Lambda due to the specialized nature of ORM tools.

In Summary, AWS Lambda and Sequelize differ in their execution environment, scaling capabilities, pricing models, functionality, vendor lock-in, and community support.

Advice on AWS Lambda and Sequelize

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!

See more
Replies (2)
Anis Zehani

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

See more

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.

See more
Decisions about AWS Lambda and Sequelize
Tim Nolet

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.
The setup

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

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of AWS Lambda
Pros of Sequelize
  • 129
    No infrastructure
  • 83
    Cheap
  • 70
    Quick
  • 59
    Stateless
  • 47
    No deploy, no server, great sleep
  • 12
    AWS Lambda went down taking many sites with it
  • 6
    Event Driven Governance
  • 6
    Extensive API
  • 6
    Auto scale and cost effective
  • 6
    Easy to deploy
  • 5
    VPC Support
  • 3
    Integrated with various AWS services
  • 42
    Good ORM for node.js
  • 31
    Easy setup
  • 21
    Support MySQL & MariaDB, PostgreSQL, MSSQL, Sqlite
  • 14
    Open source
  • 13
    Free
  • 12
    Promise Based
  • 4
    Recommend for mongoose users
  • 3
    Typescript
  • 3
    Atrocious documentation, buggy, issues closed by bots

Sign up to add or upvote prosMake informed product decisions

Cons of AWS Lambda
Cons of Sequelize
  • 7
    Cant execute ruby or go
  • 3
    Compute time limited
  • 1
    Can't execute PHP w/o significant effort
  • 30
    Docs are awful
  • 10
    Relations can be confusing

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

What is AWS Lambda?

AWS Lambda is a compute service that runs your code in response to events and automatically manages the underlying compute resources for you. You can use AWS Lambda to extend other AWS services with custom logic, or create your own back-end services that operate at AWS scale, performance, and security.

What is Sequelize?

Sequelize is a promise-based ORM for Node.js and io.js. It supports the dialects PostgreSQL, MySQL, MariaDB, SQLite and MSSQL and features solid transaction support, relations, read replication and more.

Need advice about which tool to choose?Ask the StackShare community!

What companies use AWS Lambda?
What companies use Sequelize?
See which teams inside your own company are using AWS Lambda or Sequelize.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with AWS Lambda?
What tools integrate with Sequelize?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

GitHubPythonNode.js+47
54
72326
GitHubDockerAmazon EC2+23
12
6566
JavaScriptGitHubPython+42
53
21868
What are some alternatives to AWS Lambda and Sequelize?
Serverless
Build applications comprised of microservices that run in response to events, auto-scale for you, and only charge you when they run. This lowers the total cost of maintaining your apps, enabling you to build more logic, faster. The Framework uses new event-driven compute services, like AWS Lambda, Google CloudFunctions, and more.
Azure Functions
Azure Functions is an event driven, compute-on-demand experience that extends the existing Azure application platform with capabilities to implement code triggered by events occurring in virtually any Azure or 3rd party service as well as on-premises systems.
AWS Elastic Beanstalk
Once you upload your application, Elastic Beanstalk automatically handles the deployment details of capacity provisioning, load balancing, auto-scaling, and application health monitoring.
AWS Step Functions
AWS Step Functions makes it easy to coordinate the components of distributed applications and microservices using visual workflows. Building applications from individual components that each perform a discrete function lets you scale and change applications quickly.
Google App Engine
Google has a reputation for highly reliable, high performance infrastructure. With App Engine you can take advantage of the 10 years of knowledge Google has in running massively scalable, performance driven systems. App Engine applications are easy to build, easy to maintain, and easy to scale as your traffic and data storage needs grow.
See all alternatives