Skip to main content

How multi-tenant systems can help you in Enterprise IT

What is a multi-tenant system?

According to wikipedia, "Multitenancy refers to a principle in software architecture where a single instance of the software runs on a server, serving multiple client organizations (tenants)".

Which means that a single software instance runs on a single server can be shared between multiple client organizations or tenants. This is somewhat different Virtual software systems in which each organization gets a piece of their own (virtual) software (or hardware) resources.

This concept is really helpful in cloud computing architecture where we use the common resources by different clients.

How multi-tenancy can save your Enterprise IT?

In a multitenancy environment, multiple customers share the same application, running on the same operating system, on the same hardware, with the same data-storage mechanism.

Multitenancy allows for cost savings over and above the basic economies of scale achievable from consolidating IT resources into a single operation.

  • An application instance usually incurs a certain amount of memory and processing overhead which can be substantial when multiplied by many customers, especially if the customers are small. Multitenancy reduces this overhead by amortizing it over many customers. 
  • Further cost savings may come from licensing costs of the underlying software (such as operating systems and database management systems). Put crudely, if you can run everything on a single software instance, you only have to buy one software license
How hard it is to build a multi-tenant system?

Even though this is not related to the customer, he should know that designing multi-tenant systems is a very complex task and requires a really good effort.

But it is not that hard when the release management is considered. Since the system runs in a single server, new releases can be easily deployed in to that system comparing non multi-tenant systems in which we have update each and every system for every new release.
Labels:

Comments

  1. E Square System and TechnologyMay 7, 2024 at 4:47 AM

    System integration services involve the process of connecting various disparate IT systems and software applications within an organization to ensure seamless communication and data sharing. This involves integrating hardware, software, networking technologies, and other components to create a cohesive and efficient system. System integration aims to streamline operations, improve productivity, enhance data accuracy, and facilitate better decision-making by enabling different systems to work together harmoniously. It often involves tasks such as data migration, application integration, API development, and customization to meet specific business needs. Overall, system integration services play a crucial role in optimizing organizational processes and leveraging technology to achieve strategic goals.

    ReplyDelete

Post a Comment

Popular posts from this blog

How to protect your APIs with self contained access token (JWT) using WSO2 API Manager and WSO2 Identity Server

In a typical enterprise information system, there is a high chance that people will use different types of systems built by different vendors to implement certain types of functionalities. The APIs might be hosted in an API Manager developed by vendor A and the user management can be implemented using a different vendor (vendor B). In this type of a situation, one system will not be able to directly contact the other system but they want to use both systems in tandem. Self-contained access tokens are used in these types of situations where applications can get the token from one system and use that in another system to access protected resources. In this scenario, the second system does not need to make a contact to the first system over the network to validate the user information since the token is self-contained and it has relevant details about the user. This will improve the token processing time significantly since it completely removes the network interaction. The below fig...
1 comment
Read more

WSO2 ESB creating a response for a "GET" request

When you are creating REST APIs with WSO2 ESB, you may need to send some response message back to the user when something goes wrong. In this kind of scenario, you can create a payload inside the ESB and send it back. For doing this, you can use the below configuration. <api xmlns=" http://ws.apache.org/ ns/synapse " name="LoopBackProxy" context="/loopback">    <resource methods="POST GET">       <inSequence>          <property name="NO_ENTITY_BODY" scope="axis2" action="remove"></property>          <log level="full"></log>          <payloadFactory media-type="xml">             <format>                <m:messageBeforeLoopBack xmlns:m=" http://services...
Post a Comment
Read more

WSO2 ESB usage of get-property function

What are Properties? WSO2 has a huge set of mediators but property mediator is mostly used mediator for writing any proxy service or API. Property mediator is used to store any value or xml fragment temporarily during life cycle of a thread for any service or API. We can compare “Property” mediator with “Variable” in any other traditional programming languages (Like: C, C++, Java, .Net etc). There are few properties those are used/maintained by ESB itself and on the other hand few properties can be defined by users (programmers). In other words, we can say that properties can be define in below 2 categories: ESB Defined Properties User Defined Properties. These properties can be stored/defined in different scopes, like: Transport Synapse or Default Axis2 Registry System Operation Generally, these properties are read by get-properties() function. This function can be invoked with below 2 variations. get-property(String propertyName) get-property(String scop...
Post a Comment
Read more