Is it feasible to store data on cloud services?

[2023peterV5]

pl redis memcache is connected to the cloud service, then the remaining part of zulip becomes a stateless service. When the number of users increases rapidly, automatic expansion can be performed. Is this idea feasible?

[DhruvLamba]

pl redis memcache is connected to the cloud service, then the remaining part of zulip becomes a stateless service. When the number of users increases rapidly, automatic expansion can be performed. Is this idea feasible?

Storing data on cloud services for Zulip is highly feasible and beneficial, offering scalability, cost-efficiency, and robust security. By integrating Redis and Memcached in the cloud, Zulip can maintain a stateless architecture, enabling seamless horizontal scaling and enhanced performance. Cloud services provide autoscaling and load balancing to handle rapid user growth effectively. This approach ensures high availability, compliance with data regulations, and optimal user experience, making it a strategic solution for Zulip's infrastructure needs.

[timabbott]

@DhruvLamba was that comment generated by AI?

[DhruvLamba]

@DhruvLamba was that comment generated by AI?

Nope. Actually I am specializing in cloud computing and virtualization , hence worked with many cloud providers like AWS, GCP , Azure.
AWS provides with the following architecture:
Amazon ElastiCache: Fully managed Redis or Memcached service.
Amazon RDS: Managed relational database service.
Amazon EC2: Scalable virtual servers.
AWS Elastic Load Balancing (ELB): Distributes incoming traffic across multiple targets.
AWS Auto Scaling: Automatically adjusts the number of EC2 instances in response to load.

[timabbott]

OK. Well in any case, it is feasible to use cloud services, though not an option that we recommend, because it's more work to set up. You can see documentation here:

• https://zulip.readthedocs.io/en/latest/production/deployment.html#running-zulip-s-service-dependencies-on-different-machines
• https://zulip.readthedocs.io/en/latest/production/settings.html
• https://zulip.readthedocs.io/en/latest/production/system-configuration.html

Or look at docker-zulip if you prevent that style of splitting up systems.

However, there are some algorithms/data flow issues that do not make it trivial to scale to millions of users, especially in a single organization through such techniques, so don't expect that just doing those things will dramatically change Zulip's scaling characteristics.