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.

Comments

  1. 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

WSO2 ESB tuning performance with threads

I have written several blog posts explaining the internal behavior of the ESB and the threads created inside ESB. With this post, I am talking about the effect of threads in the WSO2 ESB and how to tune up threads for optimal performance. You can refer [1] and [2] to understand the threads created within the ESB. [1] http://soatutorials.blogspot.com/2015/05/understanding-threads-created-in-wso2.html [2] http://wso2.com/library/articles/2012/03/importance-performance-wso2-esb-handles-nonobvious/ Within this blog post, I am discussing about the "worker threads" which are used for processing the data within the WSO2 ESB. There are 2 types of worker threads created when you start sending the requests to the server 1) Server Worker/Client Worker Threads 2) Mediator Worker (Synapse-Worker) Threads Server Worker/Client Worker Threads These set of threads will be used to process all the requests/responses coming to the ESB server. ServerWorker Threads will be used to pr

How puppet works in your IT infrstructure

What is Puppet? Puppet is IT automation software that helps system administrators manage infrastructure throughout its lifecycle, from provisioning and configuration to orchestration and reporting. Using Puppet, you can easily automate repetitive tasks, quickly deploy critical applications, and proactively manage change, scaling from 10s of servers to 1000s, on-premise or in the cloud. How the puppet works? It works like this..Puppet agent is a daemon that runs on all the client servers(the servers where you require some configuration, or the servers which are going to be managed using puppet.) All the clients which are to be managed will have puppet agent installed on them, and are called nodes in puppet. Puppet Master: This machine contains all the configuration for different hosts. Puppet master will run as a daemon on this master server. Puppet Agent: This is the daemon that will run on all the servers, which are to be managed using p

How to configure timeouts in WSO2 ESB to get rid of client timeout errors

WSO2 ESB has defined some configuration parameters which controls the timeout of a particular request which is going out of ESB. In a particular  scneario, your client sends a request to ESB, and then ESB sends a request to another endpoint to serve the request. CLIENT->WSO2 ESB->BACKEND The reason for clients getting timeout is that ESB timeout is larger than client's timeout. This can be solved by either increasing the timeout at client side or by decreasing the timeout in ESB side. In any of the case, you can control the timeout in ESB using the below properties. 1) Global timeout defined in synapse.properties (ESB_HOME\repository\conf\) file. This will decide the maximum time that a callback is waiting in the ESB for a response for a particular request. If ESB does not get any response from Back End, it will drop the message and clears out the call back. This is a global level parameter which affects all the endpoints configured in ESB. synapse.global_timeout_inte