Lightspeed K-Series: avtomaticheskoye serenie blyud menyu pri stoke 0

V Amsterdame losos zakanchivalsya v razgar lancha — no tsifrovoye menyu uznavalo ob etom cherez 20 minut. S thMenu podklyuchennym k WebSocket Lightspeed K-Series seryi badj "Segodnya net" poyavlyaetsya cherez 280ms posle nulya stoka. Vozvraty po nepravilnym zakazam upali na 94%.

Postoyannyi WebSocket, ne polling 5s

Postoyannoe soedinenie k /inventory-events cherez Cloudflare Durable Objects — odin socket na lokatsiyu. 18 socketov pomeshchaiutsya v 32 KB pamyati.

Hranim tolko posledniy snapshot SKU, bez istorii — push-bazirovannyi update s latentnostyu menshe sekundy.

Seryi badj, ne udalenie

Kartochka ostaetsya vidimoy, opacity 0.5, badj "Segodnya net". Klient vidit foto i vernetsya zavtra. Knopka v korzinu poluchaet pointer-events:none.

• Tsvet: ugolnyi seryi (#3a3a3a), nikogda ne krasnyi.
• Animatsiya: cross-fade 220ms.
• Filtr allergenov: sold-out ostayutsya vidimymi, prosto neyakazumye.

Krayniy sluchay: otmena ofitsiantom

Ofitsiant otmenyaet 1 losos, Lightspeed podnimaet stok do +1, no kuhnya uje prigotovila poslednyu portsiyu. Resheniye — ruchnaya blokirovka sold-out. Menedjer vklyuchaet "net segodnya" vruchnuyu, WebSocket sobytiya ignoriruyutsya do snyatiya. Hranitsya v manual_soldout_until, cron 23:00 chistit posle servisa.

Bolshe net prizrachnyh zakazov "stok 1, realnost 0".

FAQ

L-Series sovmestim? Net — L-Series tolko REST polling. K-Series imeet WebSocket.

Esli socket otvalivayetsya? Eksponentsialnyi rekonnekt 1s/2s/4s/8s plus REST kajdye 5 minut.

Kakoy plan? Pro i Platinum. Starter sohranyaet ruchnoy toggle.

Было полезно? Поделитесь.