In the article talking about SLAs I mentioned two strategies Northwind hosting can use to manage performance and scalability of the hosted application: Adding new servers to host web services, with a front load balancer Doing "database load balancing...

Part III of this series of articles introduced a common design pattern (using an interceptor) to provide value added services such as billing and metering. The interceptor works at the operation level, and uses both information provided by the ISV (Litware...

Billing is obviously a very important concern, after all Litware has to get paid! As described in Part I, Litware is looking at two models for Billing: • Subscription based: (For example: $X/tenant/month up to 5 seats/tenant + $Y/month for additional...

On-Boarding is the process of bringing the application to the operation. It's everything that needs to happen for hand-off of the app from the ISV to the hoster. In the scenario described in the previous post , I mentioned that Northwind requires ISV...

In its current version, LitwareHR is focused very much on the challenges an ISV faces while building a SaaS delivered app: multi-tenancy, configurability, etc. In the last few weeks I've been working on exploring the implications of hosting LitwareHR...