🌸 スプリングセール：年間プラン30%オフ 🌸 コード：SPRING2026
Technical Design & Review
Prompt detail
Act as a Staff Software Engineer at a large tech company. I need to design a real-time notification system for our web application.
My initial plan is to use a direct WebSocket connection between each client and our main backend server.
Please review this approach:
1. Pros and Cons: Advantages and disadvantages regarding scalability, complexity, and reliability.
2. Alternative Architectures: Propose two alternatives (e.g. message queue or third-party service).
3. Comparison Table: Compare all three approaches across: Scalability, Cost/Complexity, and Development Speed.
What the prompt does
When designing systems like real-time notification infrastructure, engineers need to evaluate their initial approach against viable alternatives before committing resources. This prompt takes your proposed architecture — such as direct WebSocket connections — and produces a structured review covering pros, cons, and two alternative approaches.
remio accelerates this by referencing past architecture decision records, design docs, and Slack discussions your team has already had about similar systems. Instead of starting from scratch, you get a comparison table spanning scalability, cost, complexity, and development speed — ready to drop into an ADR or RFC.
When to use
• You're drafting an architecture decision record for a new real-time feature and need to document why you chose one approach over others.
• A design review is coming up and you want a structured pros-and-cons breakdown to present to your team.
• You're evaluating whether to build a WebSocket layer in-house or adopt a managed service like Pusher or Ably.
• Your team is debating message queue architectures (Kafka, RabbitMQ) versus direct connections and needs a clear comparison framework.
• You're onboarding onto an existing notification system and want to understand the tradeoffs that were likely considered.
Prompt examples
Input: Act as a Staff Software Engineer at a large tech company. I need to design a real-time notification system for our web application. My initial plan is to use a direct WebSocket connection between each client and our main backend server. Please review this approach with pros and cons, two alternative architectures, and a comparison table.
remio responds:
Your direct WebSocket approach offers low latency and full control, but it tightly couples notification delivery to your backend, creating scaling bottlenecks past ~10K concurrent connections per server. Alternative 1: Introduce a message broker like Redis Pub/Sub or Kafka between your backend and a dedicated WebSocket gateway — this decouples producers from consumers and enables horizontal scaling. Alternative 2: Use a managed service like Pusher or Ably, which handles connection management entirely. Here's the comparison: Direct WebSocket scores high on development speed but low on scalability; the message queue approach is moderate on both cost and scalability; managed services score highest on scalability and speed but carry ongoing vendor costs. I've also found a related discussion in your #platform-architecture Slack channel from March where your team evaluated Redis Pub/Sub for a similar use case.
Tip 1:
Specify your expected scale — concurrent users, messages per second, geographic distribution — so the architecture review addresses your actual constraints rather than generic tradeoffs.
Tip 2:
Include your current tech stack (e.g., Kubernetes, AWS, specific languages) to get alternatives that fit your existing infrastructure.
Tip 3:
Ask remio to search your team's past design docs and RFCs before generating the review, so the comparison reflects decisions your organization has already explored.
More tips
レミオは知識に関するあらゆるニーズを満たします
詳しい機能はこちら
ウェブサイト、ローカル フォルダー、ファイルからリソースをキャプチャします。
ナレッジベース全体から、信頼できる回答を即座に取得できます。
デスクトップ、ブラウザ、モバイルで使えるアシスタント。
無制限の無料録音と文字起こし、ボットなし。