jrirei

6 ms·

1. 1.▲
   by jrirei 15y ago

   Yes, this might work. But I would be careful about replication and scaling - this could make things somewhat complicated. ;-)
2. 2.▲
   by jrirei 15y ago

   For Monster World we did not consider this as the game is running fine (or good enough) as it is now. During the last weeks we were more focused on reducing RAM consumption of our databases as that is currently the main driver of cost and o
3. 3.▲
   by jrirei 15y ago

   We did go for Ruby in order to increase developer productivity (having a very small team of just two developers), and good code quality/high test coverage. We were sure we needed to refactor a lot later on. So Ruby seems like a good choice.
4. 4.▲
   by jrirei 15y ago

   You are right: "no cache" means no cache in the app layer, so no eviction logic and inconsistencies between an app-layer-cache and a database. And yes the best thing a cloud can offer is lots and lots of memory. That's where it's good. And
5. 5.▲
   by jrirei 15y ago

   We do preload all data on client side as the client must never wait on server responses for better user experience. But we cannot batch on client side as we cannot foresee when the user will kill the client. And actually we have more than 4
6. 6.▲
   by jrirei 15y ago

   The presentation was recorded by InfoQ. I hope they will make it available during in the next 1-2 months. There's a lot I said but did not put on the slides. You are correct in your assumption that each Tile had been a record in a MySQL tab