在使用.NET的内存通信中

Question

I've implemented a type of in memory database using generic Lists and Linq and it is consumed by an ASP.NET application. Building this database in memory takes about 45 seconds (it's built from a database) so we're trying to minimize ASP.NET app pool recycles to once a day at 1:00 am to avoid having the worker process recycle in the middle of the day and spin for 45 seconds rebuilding the database.

I'd like to move our in memory database to another process isolated from the ASP.NET worker process but I'm unsure as to how I can get objects in the ASP.NET application talking to a separate process that would hold the database. Should I use a TCP listener type of thing? I know IIS used to be able to host libraries and make them available via remoting...is this still possible?

If you're wondering why I'm going to all the trouble of an in memory database it's because it's powering a faceted search application. Using Linq and in memory lists is faster by many orders of magnitude than going to the database for each search.

Thanks in advance for any advice.

Answer 1

You should probably look at WCF over named pipes: http://www.switchonthecode.com/tutorials/wcf-tutorial-basic-interprocess-communication .

You could host your DB in a simple windows service.

Answer 2

Named pipes are one option to do it. You can abstract that away to an extent using WCF Named Pipes bindings . You can also apply security permission to said named pipes to improve security against arbitrary applications doing stuff to your in memory database.

Answer 3

CK1，WCF和Named Pipes就像其他人说的那样在同一台服务器上都没问题，如果你再将其他机器（如应用服务器）放入内存数据库托管中，你可以简单地更改绑定并使用netTCP进行快速二进制通信TCP上的机器......