Tacnode™
Pipelies2 min

The Vanishing Order: "Order Not Found," So the Customer Pays Twice

Order not found. But the order went in two seconds ago, and the replica hasn't caught up. A customer submits an order, and the write lands on the primary. The order exists. One second later the confirmation page loads. It reads from a replica that is still applying earlier writes, so the page says order not found. The customer does what anyone would do and taps Pay again. The second submission arrives, nothing can see the first one yet, and it's accepted. Now there are two orders, two charges and a support ticket. Then the same two seconds with the order written to Tacnode. The confirmation page reads from the place the order went, so it finds the order, and a second tap is treated as the same order. When orders are written to Tacnode, the very next read sees them, so there's no replica to wait on. The confirmation page and the duplicate check both read what was just committed, and the outcome is written back as context. Records your own systems own stay with them.

Overview

One of the fourteen Pipelies lies: how a confirmation page reading a replica turns one order into two, and the same two seconds with the order written to Tacnode.

Topics Covered

  • •An order written to the primary
  • •A confirmation page reading a replica one second later
  • •"Order not found" and a second tap on Pay
  • •The confirmation page reading from where the order was written
  • •A second tap treated as the same order

Key Takeaways

  • ✓The order existed the whole time; the page read a copy that didn't have it yet
  • ✓The duplicate check couldn't see the first order either
  • ✓When the order is written to Tacnode, the very next read sees it
  • ✓Records your own systems own stay with them

Ready to get started?

Book a demo to see how Tacnode can power your real-time data infrastructure.