Write a Real-Time Chat Architecture

This prompt helps developers design production-ready real-time messaging systems using Google's Gemini AI. If you're building a chat feature, notification system, or live collaboration tool, this prompt guides you through the critical architectural decisions that separate hobby projects from scalable applications. Whether you're a backend engineer planning infrastructure or a full-stack developer implementing real-time features, Gemini walks you through WebSocket strategies, database persistence patterns, and horizontal scaling approaches that actually work in production.

To use this prompt effectively, replace [application] with your specific use case. For example, if you're building a customer support chat platform, you'd enter "Design a real-time messaging system for a customer support platform serving 50,000 concurrent users." Another concrete example: "Design a real-time messaging system for a multiplayer collaborative document editor." The more specific you are about your application type and expected scale, the more tailored Gemini's recommendations become. Include constraints like expected user count, message volume, or geographic distribution if you have them.

Gemini typically responds with a comprehensive architecture overview including WebSocket connection management strategies, message queue options like Redis or RabbitMQ, database schema recommendations for message persistence, and approaches for scaling horizontally across multiple servers. You'll get concrete guidance on delivery guarantees, explaining at-least-once versus exactly-once semantics and when each matters. The output usually includes code examples or pseudocode showing how to implement key components.

For better results, ask Gemini follow-up questions about specific constraints in your environment. If you're limited to certain technologies or have strict latency requirements, mention those details. You can also ask Gemini to compare trade-offs between different approaches, like comparing message queuing systems or explaining database indexing strategies for message lookups. The more context you provide about your technical constraints and priorities, the more actionable Gemini's architecture recommendations become.