How Mural.ly Achieves Great Performance for a Low Cost
Come on and see how we are serving 80K request per hour per server on only two small instances. We'll share our secrets on how Mural.ly uses a canonical operation model that converts into MongoDB statements that it uses to keep the murals updated while sorting out concurrency issues. Throughout the sessions we'll show the different patterns that we've applied to achieve this and we'll share all our secrets on how to optimize for performance on the client/server interaction. By the end of the session you will understand how we built mural.ly from Client/Server/DB I/O interaction, and which tools and metrics, you can use to understand what's going on.
Comments have been closed since this content was published more than 30 days ago, but if you'd like to send us feedback you can Contact Us.