Application-level multi-tenancy: the promise and pitfalls of shared-everything architectures

SaaS providers aim for economy of scale: multiple customers (tenants) must be serviced on a common infrastructure/platform or software application.
As such, application service providers (ASPs, and more recently SaaS providers) have evolved their deployment architecture from strict hardware separation between tenants towards an increasing level of sharing between tenants. This process is mainly driven by scalability and maintainability reasons.

Standing on the Shoulders of Giants: 6 APIs for instant SaaS Success

[This post appeared first at the Sirris Blog.]

Running a software as a service (SaaS) business is hard: you need to develop and evolve a stellar software product, that elegantly and intuitively, dare I say 'auto-magically' solves pressing problems for your customers. You need to attract new customers, bring them onboard and hook them for life, you need to address support issues.

Is your SaaS company solving a shark bite or a mosquito bite problem?

Ideas... We all have them, day in day out. If I could sell 1% of my ideas, I'd be rich, just by the sheer volume of idea I have. Point is, nobody would pay for an idea, because without acting upon an idea, an idea in my head just stays... well, an idea in my head. Nobody will ever know if it was a good idea or a bad idea.

This is exactly the dilemma startups face: how do we know if an idea is worth something? Is this idea so good that we can build a company on top of it?