A modular, redundant platform built for pharmacy operations. 50+ API modules, 37 pharmacy-specific endpoints, 3-node on-premises processing, automatic failover.
| Action | T0 Auto | T1 Tech | T2 RPh | T3 Mgr |
|---|---|---|---|---|
| Status inquiry | AUTO | |||
| Refill request (eligible) | AUTO | |||
| Store hours / location | AUTO | |||
| Transfer request | TECH | |||
| Insurance question | TECH | |||
| PA form submission | TECH | |||
| New Rx verification | RPh | |||
| Controlled substance | RPh | |||
| Drug interaction override | RPh | |||
| Clinical consultation | RPh | |||
| Price adjustment | MGR | |||
| Refund processing | MGR | |||
| Patient complaint | MGR |
Hybrid approach: local LLM handles 90% of requests. Cloud AI handles complex reasoning with anonymized context.
| Scenario | What Happens | Downtime |
|---|---|---|
| Primary server crash | Hot standby takes over automatically | <30 seconds |
| Both active nodes fail | Cold standby activated manually | <5 minutes |
| Internet outage at pharmacy | Phone system continues (Twilio hosted externally) | 0 seconds |
| All LLM providers down | Local Llama handles calls with simpler responses, escalates more to staff | 0 seconds |
| Power outage | UPS keeps Mac Minis running for 15-30 min. Twilio continues externally. | 0 seconds (calls) |
Total redundancy cost: ~$85/month (standby VPS + monitoring + backups). The previous vendor's system went down because they had a single point of failure. We have zero.
50+ isolated modules. Each one runs independently. Update one without touching the rest. No full reimaging. No full rollbacks. No downtime.
Each box is an independent module. Pull one out, the rest keep running.
| Step | Node A (Primary) | Node B (Hot Standby) | Node C (DR) |
|---|---|---|---|
| 1. Prep update | Serving traffic | Receives update | Unchanged |
| 2. Test on B | Serving traffic | Testing updated module | Unchanged |
| 3. Promote B | Standby (old version) | Now serving traffic | Unchanged |
| 4. Update A | Receives same update | Serving traffic | Unchanged |
| 5. Both current | Back to primary | Hot standby (current) | Snapshot updated |
Total downtime during the entire update process: zero seconds. Traffic never stops. If the update fails on Node B, Node A is still running the proven version. Node C is always available as the last-known-good backup.
Monolithic systems go down because everything is coupled. One bad update, one crashed service, one corrupted config -- and the whole thing stops. With modular architecture, you're swapping a single Lego brick while the rest of the structure stands. With 3 nodes, you always have a working copy to fall back to. This is how enterprise systems are built. This is why your phones will never go down.