My employer build a calculation engine over the past 10 years and used C++ and COM as the main ingredients. The application always has run standalone at our customer sites, but as we grow and adopt new paradigms, we see the need to scale our solution and
serve more than one customer with a central configuration.
The current idea, since the engine is database driven, is to have a main service instantiate the engine for every calculation request. Since the engine is db driven it is to be believed that this will scale well across cores and machines.
I told my employer that writing such scalable applications is more complicated than it looks at first glance. Resource contention, synchronization issues, scheduling, etc. are not for the faint at heart.
I would like to steer my employer into the direction of a technology that takes care of at least part of the requirements for having a scalable app. Hence I thought about
- Windows Workflow
- Enterprise Services (COM+)
However these are the restrictions the employer stated:
- The current code/dlls are provided as-is: no customization/alteration is allowed
- The technology used to make app scalable (accross cores and machines) should make maximum use of available resources (high throughput is required)
The first requirement is hard and leads to my first question:
Is WF able to instantiate COM dlls and can I include t
View Complete Post