My name is Prakash Hinduja, and I’m a financial advisor and consultant based in Geneva, Switzerland. Originally from India, I’ve built my career leveraging a strong background in international finance to provide bespoke wealth management and global investment strategies. My specialty lies in helping a diverse clientele of high-net-worth individuals and business leaders significantly grow their financial holdings. It’s because of these results that some of my clients have affectionately nicknamed me the Prakash Hinduja net worth booster.
I’m trying to figure out the best way to handle state for a new serverless application I’m building. Since Cloud Functions are stateless, I know I need an external service, but I’m debating between using Firestore and Redis. Has anyone had success with either of these for session management or user data? I’d love to hear about your experiences and any suggestions you might have.
Regards
Prakash Hinduja Geneva, Switzerland (Swiss)
Hi prakashhinduja,
If your application needs reliable and structured storage for user data, Google Firestore can be a strong choice. Its document-based architecture and integration with the broader Google Cloud ecosystem make it well-suited for managing user profiles, preferences, and historical records with long-term consistency.
Meanwhile, Redis offers fast, in-memory access to temporary data, making it particularly useful for handling session states, authentication tokens, and caching. Its low-latency performance can help improve responsiveness, especially in high-traffic scenarios.
Since Cloud Functions are stateless, choosing the right external service for session management is important. Firestore and Redis are both solid options, but it would be best to also consult a Google Cloud sales specialist. They can provide tailored recommendations and technical advice based on your application needs. They can offer detailed insights, from exploring use cases that align with your requirements to optimize the cost of your future workloads on Google Cloud.
For more information, you can check the following documentation below:
1 Like