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

AWS Lambda

+ 1

+ 1
Add tool

AWS Lambda vs Hibernate: What are the differences?

AWS Lambda: Automatically run code in response to modifications to objects in Amazon S3 buckets, messages in Kinesis streams, or updates in DynamoDB. 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; Hibernate: Idiomatic persistence for Java and relational databases. Hibernate is a suite of open source projects around domain models. The flagship project is Hibernate ORM, the Object Relational Mapper.

AWS Lambda and Hibernate are primarily classified as "Serverless / Task Processing" and "Object Relational Mapper (ORM)" tools respectively.

"No infrastructure" is the primary reason why developers consider AWS Lambda over the competitors, whereas "Easy ORM" was stated as the key factor in picking Hibernate.

PedidosYa, Zapier, and Repro are some of the popular companies that use AWS Lambda, whereas Hibernate is used by, StyleShare Inc., and Peewah. AWS Lambda has a broader approval, being mentioned in 1002 company stacks & 585 developers stacks; compared to Hibernate, which is listed in 85 company stacks and 72 developer stacks.

Decisions about AWS Lambda and Hibernate
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 Private StackShare. Sign up for Private StackShare.
Learn More