|Daily Request Limit||5000||Unlimited||Unlimited|
|Supported Platforms||AWS||AWS, GCP (alpha), Azure (alpha)||AWS, GCP (alpha), Azure (alpha)|
|Max Size||256 Mb||10 Gb||50 Gb|
|Max Concurrent Connections||20||1000||5000|
|Max Request Size||50Kb||400KB||1Mb|
|Multi Zone Replication||Not available||Not available||Available|
|Security||Password + TLS||Password + TLS||Password + TLS + Mutual Authentication|
|Audit Logs||Last 7 days||Last 30 days||Last 1 year|
|Price (per 100K request)||Free||0.4$||0.75$|
|Price (per 1GB-month storage)||Free||0.15$||0.15$|
Alpha: Premium databases and support for GCP and Azure platforms are in alpha stage. They are not open to public usage yet. To be an alpha tester or to learn date of general availability, please email to firstname.lastname@example.org
Database limit per user: One user can have at most one free database at a time. This limit is 20 for standard and premium databases at start. You can increase this limit by emailing your request to email@example.com
Is credit card required? You can create and start using Free database without a credit card. For Standard and Premium databases credit card is required.
Daily Request Limit: This is the maximum number of requests that your database can receive and process per day. After limit is reached, your clients will start receiving limit exceeded errors. Daily request limit is reset at 00:00 UTC time.
Max Size: This is the total data size that you can store in your database. After limit is reached, write requests will be rejected and clients will receive rejection errors. Read and delete requests will not be affected by max size limit. You can delete some entries to allow further writes after limit is reached. Also you can consider setting TTL (expiration time) for your keys.
Max Concurrent Connections: This is the maximum allowed number of concurrent connections (clients) at a moment. This cap does not essentially limit the number of requests that can be submitted per second, but defines the maximum number of open TCP connections to the database. After the limit is reached, further connection attempts will be rejected. If you have short-living Redis connections, for instance if you create and close Redis connections inside the Lambda functions, you should have more than max-concurrent-connections number of Lambda function calls at the same time to receive a rejection error. Assume you are using a Standard database and max-concurrent-connections is
1000, and assume your Lambda function call takes
10msaverage to complete. In this setup, you can reach to 100K ops/sec throuhput without any connection limitation.
Max Request Size: This is the maximum allowed request size. Request size is total size of a Redis command and its parameters. If your request exceeds this limit, it will be rejected by the server.
Persistence: Lambda store has its own persistence layer that integrates with block storage services of cloud providers. This provides fault tolerance to all database types including the free.
Multi zone replication: Lambda store replicates data to multiple zones for Premium type of databases. This provides high availability and minumum failover time. This is not available for Free and Standard databases.
Security: Authentication to databases are done via password. TLS encryption can be enabled for all database types. You can also enable Mutual Authentication (in TLS) in Premium databases.
Price (per 100K request): In Free databases there is no price per request but you have the limit of 5000 requests per day. In standard databases, 100.000 requests cost 0.4 USD. In premium databases 100.000 requests cost 0.75 USD. All type of Redis commands count as request (GET, SET, AUTH etc).
Price (per 1GB-month storage): In Free databases there is no price per storage but their max size is quite limited. In standard and premium databases, if your database is 1GB during the month then it will cost you 0.15$ at the end of the month. If your database size is different at each day of the month, we take the average and multiply it with 0.15$.