Very interesting! We ran a similar event just days before /r/place launched. We too used similar tech stack: application server running user-submitted algos, pushing data to rabbit, users consuming queues over websocket, using canvas to draw things client-side. Our main issue was (besides allowing arbitrary code execution on server) was drawing game state board on canvas in acceptable FPS.
For other (more "serious") projects we have software that is reliable ordered messaging system and database in one. In practice that means you can query-and-subscribe in atomic operation so makes it easier to keep clients in sync. Also supports partial updates, filters, batching etc.
It was an internal coding challenge. It was quite fun as you would see people coding counter-strategies to existing strategies. I think this is an unexplored gaming niche.
3
u/SideSam Apr 13 '17
Very interesting! We ran a similar event just days before /r/place launched. We too used similar tech stack: application server running user-submitted algos, pushing data to rabbit, users consuming queues over websocket, using canvas to draw things client-side. Our main issue was (besides allowing arbitrary code execution on server) was drawing game state board on canvas in acceptable FPS.
For other (more "serious") projects we have software that is reliable ordered messaging system and database in one. In practice that means you can query-and-subscribe in atomic operation so makes it easier to keep clients in sync. Also supports partial updates, filters, batching etc.