loading...
Cover image for Serverless Redis is Here!
Lambda Store

Serverless Redis is Here!

svenanderson profile image Sven Anderson Originally published at Medium ・3 min read

We are excited to introduce Lambda Store. Lambda Store is the first Serverless Redis service. It enables developers to boost their application with Redis without paying hundreds of dollars. You can have a fully managed Redis database in seconds. Lambda Store team deals with persistence, replication, maintenance, and all other boring stuff while you focus on your application.

Lambda Store is not "yet another Redis Cloud". Let's talk more about what makes Lambda Store so different?

1- Serverless Pricing Model

You have a new project and you do not know how many requests will it receive? You love the performance and simplicity of Redis. But all Redis Cloud services ask charges you per instance or per GB of memory. But maybe your application will not receive any traffic in the first days, then why will you pay so much? Unfortunately, none of the current Redis cloud products provides a real pay-per-use pricing model.
Let's do a simple calculation. Say I have a 1GB Redis database and I receive 1 million requests per month. For Elasticache (cache.t3.small, $0.034 hourly) this costs at least $24 assuming there is no data transfer and storage cost. For RedisLabs, the 1GB plan costs $22 per month. For Lambda Store the price is $0.4 per 100k requests. For 1 million, it is $4 plus the storage cost that is $0.15. So for 1GB, 1M request per months, Elasticache is $24, RedisLabs is $22, Lambda Store is $4.15

Alt Text

What if your product becomes so popular that it receives high and steady traffic? Most of the serverless products start to lose their spell when the application receives steady and high traffic as it starts to cost more than server/instance-based pricing models. To overcome this situation we give you the option to purchase reserved databases. A reserved database has a fixed price per month with a restriction on max throughput and data size. For high and steady throughput use cases, reserved databases cost less than serverless one. The good thing is you can start your database with serverless pricing and move it to reserved pricing when you want. See reserved plans for more information.

Alt Text

2- Younger Technology

Create a database in Elasticache and Redis Labs. Then create one in Lambda Store. Do you feel the difference? It takes minutes with both of them while Lambda Store database is ready in 2 seconds. Both Elasticache and Redis Labs are 9 years old technologies. It is late for them to make use of the technologies of post kubernetes era. Meanwhile, Lambda Store is a child of cloud native world. It is fully based on containers and kubernetes. This enables Lambda Store to satisfy the needs of new world of serverless.

Alt Text

3- Hungry Team

Elasticache is just one of the hundreds of services of AWS and you can easily say it is not one of them that AWS invests and promotes most. Redis Labs is a VC backed company and it fights with AWS to win enterprise customers. It is understandable that Redis Labs focuses more on big enterprise customers to keep its shareholders happy. Whereas, the Lambda Store team is hungry and passionate to make every user happy whoever touches Lambda Store.

Alt Text

What is next?

Right now, Lambda Store supports AWS. We have already started working on GCP and Azure. Moreover, we are working on more advanced database types that will have replication among availability zone to provide a higher level of availability. Currently, Lambda Store supports majority of the Redis API; but we are working on the missing ones too.

Try Out!

We will be more than happy if you try out Lambda Store and send your feedback via feedback@lambda.store. You can join our community Gitter channel too. Lambda Store is so easy to start but still, we prepared a Getting Started Guide.

Alt Text

Posted on by:

svenanderson profile

Sven Anderson

@svenanderson

Making the world serverless

Lambda Store

Lambda Store is the first the `serverless Redis` service. In this blog, Lambda Store engineering team shares their experiences on Cloud, AWS, Kubernetes, Redis and of course Lambda Store.

Discussion

markdown guide
 

This looks great.

Most of people use redis for cahing as it makes your stuff fast. By making this as a serverless which runs on requesting time, does it delay the response as it needs time to spin up?

 

Lambda store does not have a spin-up (cold start). Latency numbers are quite similar to open source redis' ones.

 

Great. can you explain how it works bit if it is okay for you?

We will posting a blog series which will explain our architecture. Follow us :)

 

The idea is great and I will follow the product. It looks promising. On the other hand I think these kind of solutions don't really fit the serverless model, because they mostly have a serious bottleneck: connection count. I would love to see a truly serverless solution just like FaunaDB did it.

 

Yes, I was part of a team working on Lambda. They were proud of their setup, the database being MongoDB Atlas.

. . .

Until the connection limits reared its ugly head!

I don't know about many products, but unless you have a true "infinitely scalable" DB like Dynamo, Serverless for high loads means very little. It's much better to stick to the tried, tested, and mature EC2 way.

 

Looks promising. There is also a free plan with persistence enabled to play with.

 

I was looking for something like this the other day. Nice work! Will be giving it a shot this weekend

 

Amazing idea! Will be interested to see where it goes.

 

There are already serverless caching solutions available such api gateway cache, and dynamodb cache (DAX). Why would I choose this over what's already there?

 

Caching is just one of the many use cases of Redis. For furher comparisons see here

 

In our setup we have 2Mrps to redis during daylight. It will be $8 every f..ng second. $8000000 every month. Are you serious?

 

We have reserved pricing for high throughput use cases. See here