Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

8
  • 1
    A bit away from what you are looking for, but Apache Solr would come with the ability to cache requests. The kind of query is quite different from SQL of course, but you could either use a interface that 'emulates' this or maybe using something like Solr could get away some of the heavy queries anyway if used properly (would depend on the kind of query you run, Solr can do a bit ore than full text search) Commented Dec 13, 2012 at 10:09
  • Your idea is solid enough. We actually already have this type of caching built into our query engine (in a sense we are our own database) and are moving it out of there into a REST server layer around it. This will enable us to move the caching out of the query service entirely, should we so want to. Commented Dec 13, 2012 at 12:29
  • 1
    Did you had a chance to look at AppFabric caching? msdn.microsoft.com/en-us/library/ff383731(v=azure.10).aspx Commented Dec 13, 2012 at 13:27
  • Would it not be a better idea to spend the resources on upgrading the SQL Server and rely on it to cache queries for itself? Commented Dec 13, 2012 at 13:52
  • How are you currently sending queries to your server, are you using an ORM? It sounds like you could probably benefit from making some stored procedures. Commented Dec 13, 2012 at 14:19