Innovation and automation: Examining development in a multi-tenant world

Right now, students all over the country are leaving home, starting university, and moving into their halls of residence. From my experience, that’s usually a single building, teeming with rooms, where they can get to know one another, collaborate on ideas, and share student facilities, like cooking. It’s a cheaper way of living too.

A true multi-tenant architecture, in other words.

This got me thinking about software development within that same multi-tenanted architecture.

First things first: what is multi-tenant? It is defined as a single instance of a software application serving multiple customers. These ‘tenants’ can customise some parts of the application, but not the application’s core. It’s cheaper because development and maintenance costs are shared, in contrast with single-tenancy, where each customer has their own software instance. Moreover, you only need to make updates once—in a single-tenancy architecture, the updates are endless.

Read more here.