Squadra Enterprise

What is Multi-tenancy?

It is a single software application that serves multiple customers; each customer is known as the tenant. Tenants can edit some parts of the application, but they can’t change the code of the application.
In multi-tenancy, all the customers used the same platform but with multiple instances. This architecture works perfectly because the tenants are physically integrated but logically separated. In a multi-tenant architecture, the software runs on one server and then on the server of multiple tenants.

Importance of Multi-tenancy:

Multi-tenancy isn’t a new concept; you can find its roots in the classic mainframe architecture, where the apps were shared among users on a common computing platform. With the help of modern hardware-assisted architecture, virtualization, such as virtual machines and their applications, significantly impacted multi-tenancy capabilities.

Types of Multi-tenancy:

Three main types of multi-tenancy are differentiated by complexity and cost. Following are the three types of multi-tenancy:

1- A single application, single database:

This type of architecture has a shared database with multiple tenants. This architecture costs the lowest as multiple tenants use a shared resource. In this form, you use a single application and instances for multiple simultaneous tenants and their data.

2- A single application, multiple databases:

In this form, the tenants use a single platform with different databases for each tenant. Due to a higher number of databases, it is difficult to scale the architecture and costs more per overhead. This architecture is functional when the data from each tenant needs to be treated separately, and it helps lower the potential noisy neighbor effects.

3- Multiple applications and multiple databases:

This type of architecture hosts different data for multiple tenants, a more complex architecture. The cost differs for each model, and it also differs in management and maintenance.

‍Squadra Enterprise worked with different companies, every company had a unique sign-in link, and for that, they purchased a package; the unique link was then shared with the company's candidates. Candidates provided the data and uploaded their Resume alongside soft skills. Afterward, they were also assessed based on the tests, which helped the HR hire candidates and kept their performance in check.

The platform consisted of the following:

• Unique access and an admin dashboard
• Team insights and individual insights
• Human resource development
• Current team 360 self-assessment
• Performance assessment
• Team leads could check the insight of all the members with various insights on the different assessments.
• Enterprise insights on performance, soft skills assessments.

Obstacles

1. There was no user data layer in the initial period. It was added later at the funding stage, meaning we were flying blind for most of the early phase of the product.
2. Weologix, the previous version of Squadra Enterprise, was for individuals, and evaluating teams' skills wasn’t possible, so we had to rethink the product approach.
3. Some graphs, such as the Scale 1-5 graph in the bar chart, weren’t descriptive enough.