Live Collectibles Auction Platform

An online auction house runs live bidding events for collectible items. During an event each bidder's browser must hold an open two-way connectionThis asks forThe server has to push to the browser unprompted. That rules out request-and-response front doors on its own. so that price changes are pushed out to every participant the moment they happen, without any client pollingThis asks forConfirms it: you may not fake live updates by asking again on a timer.. The team wants nothing to size or patchThis asks forNo servers you own. Instances and container hosts are out., per-request billing, and a handler that runs only for the length of each messageThis asks forBilled per invocation, not per hour a process stays up. while scaling from dozens of participants to tens of thousands in seconds. Bidders sign in with an email address and passwordThis asks forA managed user directory, so you are not storing credentials yourself. before joining, and every accepted bid is written to a durable relational store kept for seven yearsThis asks forDurable and relational. In-memory state cannot hold a regulatory record. of regulatory audit. The current high bid and the ranking of bids per lot must be held in memory, updated with atomic counters and sorted structuresThis asks forData structures, not plain keys. Sorted sets and INCR specifically., and published to subscribed handlersThis asks forPub/sub from the same store holding the live state..