Call me crazy, call me stupid. I’m preparing a project where I will simulate the possible behaviour of the Steam database as an ASP.NET MVC solution. My goal is to prove that it could be possible to have a database as large as the Steam database with a similar payload and still have an adequate community API which doesn’t sacrifice flexibility, comfort and data delivery for performance savings. I understand this project more than a prototype for the Steam Community API and therefore will focus completely on a redesigned web service interface and its according data layer.