Hi folks - hope someone can help me out with this one.
I have a system using .NET Enterprise Services in the middle tier, making
data access calls to an Sql Server. In an attempt to improve speed and
concurrency, and reduce the load on the Sql server, I am trying to make use
of a data cache in the middle tier.
This situation is this - the middler tier needs access to a certain set of
static, well structured data for almost every call made to it from the
client. So it is sensible to cache this static data so that each component
has it readily available, rather than having to always load from the db.
Note: all components will be deployed in the same COM+ application, hence
will all be running in the same DLLHost.

So static variables wont work (although I'm not entirely sure why), and the
only other way I can see to implement this is to use the Shared Property
Manager (SPM). Reading about this, it certainly does what I need. I can
serialise the static data as a simple string, and store it in the SPM for
later access by all components. Obviously this will have some CPU overhead
performing the serialisation all the time, but I can live with that.

The worry I have is that the SPM ONLY performs serialised Reads/Writes to
its data, so if I have 30 concurrent components trying to access it at the
same time, they will all get queued up. This may not be a big problem, as I
am only intending to access the SPM stored data once at the beginning of a
call, but it could cause me scalability issues.

Has anyone got any ideas on an alternative solution for this?, or any
comments on my current solution and its pros/cons

Many Thanks in advance