Frequently Asked Questions
Find answers to some of the most frequently asked questions about Momento services. Can't find an answer you're looking for? Reach out on Discord or contact us and we'll help you out.
Our Approach to Serverless
What does serverless really mean?
Does Momento Cache only work with serverless applications?
What is Momento Cache and how do I get started?
What is Momento Topics and how do I get started?
What type of data can I store in a cache?
What programming languages do you support?
What cloud providers and regions do you support?
How is Momento priced?
How does Momento work with DynamoDB?
What if I'm already using Redis?
How is Momento Cache different than DAX?
How does Momento Cache differ from other products in the industry?
Is Momento GDPR Compliant?
Once we had the new Momento provider, we were able to quickly swap Momento across multiple workflows and assess the performance and scale impact. Momento outperformed ElastiCache on our workflows by 15% on latencies and is able to automatically handle approximately 12X our current peak loads, without wasteful overprovisioned infrastructure or distracting scaling efforts from our engineers.
We have implemented Momento Serverless Cache to store a large volume of small objects. Momento was fast and easy to deploy, boosted the performance of our workload, and increased our developer productivity by eliminating operational tasks. Next up we are implementing Momento to accelerate our ML workflows.
It was a whirlwind from dev to prod, and Momento blew us away! Faster, scalable, and half the price of our old cache fleet—all integrated in just one week.
Before Momento, surges of sudden connections and Redis cold starts blocked our migration to a serverless architecture. Momento solved this—fast! It worked so well, we're adopting it for future caching projects.
Thanks to Momento, we finally have a cache built for the cloud. No more instance-based, self-hosted infrastructure. You get a dynamic cache with pay-per-use pricing, unparalleled performance, and no pre-provisioning of instances.