Need advice about which tool to choose?Ask the StackShare community!
ArangoDB vs Serverless: What are the differences?
Developers describe ArangoDB as "A distributed open-source database with a flexible data model for documents, graphs, and key-values". A distributed free and open-source database with a flexible data model for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions. On the other hand, Serverless is detailed as "The most widely-adopted toolkit for building serverless applications". 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.
ArangoDB and Serverless are primarily classified as "Databases" and "Serverless / Task Processing" tools respectively.
"Grahps and documents in one DB" is the top reason why over 24 developers like ArangoDB, while over 10 developers mention "API integration " as the leading cause for choosing Serverless.
ArangoDB and Serverless are both open source tools. It seems that Serverless with 30.5K GitHub stars and 3.38K forks on GitHub has more adoption than ArangoDB with 8.14K GitHub stars and 575 GitHub forks.
Droplr, Plista GmbH, and Hammerhead are some of the popular companies that use Serverless, whereas ArangoDB is used by AresRPG, Stepsize, and Brainhub. Serverless has a broader approval, being mentioned in 112 company stacks & 43 developers stacks; compared to ArangoDB, which is listed in 11 company stacks and 13 developer stacks.
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 ArangoDB
- Grahps and documents in one DB37
- Intuitive and rich query language26
- Good documentation25
- Open source25
- Joins for collections21
- Foxx is great platform15
- Great out of the box web interface with API playground14
- Good driver support6
- Low maintenance efforts6
- Clustering6
- Easy microservice creation with foxx5
- You can write true backendless apps4
- Managed solution available2
- Performance0
Pros of Serverless
- API integration14
- Supports cloud functions for Google, Azure, and IBM7
- Lower cost3
- 3. Simplified Management for developers to focus on cod1
- Auto scale1
- 5. Built-in Redundancy and Availability:1
- Openwhisk1
Sign up to add or upvote prosMake informed product decisions
Cons of ArangoDB
- Web ui has still room for improvement3
- No support for blueprints standard, using custom AQL2
