LitwareHR on SSDS – Part III – Data access enhancements 1: caching

In most applications, the distance (in terms of bandwidth and latency) between the store (the database) and the application logic (like the web servers and web services) is usually very small. The connectivity between these two components is usually very reliable and with very high throughput. But because SSDS is on the other side of…

7

LitwareHR on SSDS – Part II – The data access layer

The heart of LitwareHR implementation on SSDS is in it’s data access layer of course. In fact, we created two different, but functionally equivalent implementations: one runs against SQL (LitwareHR’s original implementation) and a second stack that runs against SSDS. Of course they are mutually exclusive and all layers above the DataModel cannot tell the…

7

LitwareHR on SSDS – Part I – Multi-tenancy & Flexibility

SSDS’s application model and features map quite nicely to our customization and multi-tenancy requirements in LitwareHR. A significant amount of code in LitwareHR is in the generic, multi-tenant, extensible data access. Our multi-tenant database performance guide, compares different extensibility approaches (XML datatypes, extended tables, fixed columns), their advantages and disadvantages, etc. All of that is…

7

SQL Server Data Services – SSDS – New version of LitwareHR

Today, in his keynote, Ray Ozzie announced a new “cloud service” available from Microsoft: SQL Server Data Services (code name: Stika). It’s a good that he announced it, because now I’m out of quarantine and I can talk about it :-). For the last 2 months I’ve been working very closely with the SSDS team,…

13

Northwind Hosting Concept Demo

For the last months our team has invested a lot of time exploring and researching the relationship between ISVs and Hosters. I shared some of the early thoughts and findings in a series of posts in this blog: Part I – The Scenario Part II – On-Boarding Part III – Billing, Metering Part IV -…

4