Cloud integration is a solution that allows disparate applications to share data and communicate. It is not just meant as a narrow solution to hook up a specific set of databases with certain applications, but as a standardized tool that can serve future needs too. It should be able to integrate everything the company has on premises with applications hosted on the cloud.
The normal state of affairs these days involves critical data locked up safely on the premises, with some applications being run on-premise while others are hosted remotely or accessed as a service. It is a common mess that creates what is known as compartmentalized data silos, where users in one system cannot access data or applications in other areas.
This problem needs connectors which can import data from an on-premise database and provide it to hosted applications. The connector would need to synchronize both sets of data in order to make it work. This sort of solution can be developed and used in a number of ways. The exact methodology followed depends on criteria such as the company's IT capabilities and resources, its size and the deployment scope.
Traditionally, such tools would be developed in-house and housed on-premises along with the rest of the critical data. This is something an enterprise level customer would do, in order to maintain continuity with existing tools used to integrate applications available on the premises. The tools simply have to be expanded to include hosted applications and SaaS services.
To take this one step further, the connectors can be put on the cloud too. The only difference is that the integration setup does not have to be in-house. The customer still retains control over the tools and the ability to continue development with the help of a PaaS provider. This works nicely for companies that have the IT capability to develop tools and manage them, but do not want to add more IT hardware on the premises.
There are now SaaS providers that allow clients to use pre-developed tools as a service. This means the tools do not have to be developed or maintained, removing PaaS from the equation. All a company has to do now is to pay for use of a tool, with no other IT resources or investments required. This is just about ideal for customers who need this done quickly and without a big budget.
Not all enterprise customers can make do with a pre-developed SaaS solution. Their needs are likely to be more complex and require a fair bit of customization. It might be still be feasible if the deployment scope is limited, such as for a single division. As far as medium and small scale companies are concerned, the value in SaaS offerings is unbeatable.
Before getting into a cloud integration dance with a provider, it might be advisable to clarify a few aspects. One of these things is the ability to share data between separate clouds. Get a clear picture about how long the process is going to take, and what kind of training has to be provided to users. A lot of implementations fail not because of flaws, but due to delays and confused users simply unable to realize the potential of the integrated system.
The normal state of affairs these days involves critical data locked up safely on the premises, with some applications being run on-premise while others are hosted remotely or accessed as a service. It is a common mess that creates what is known as compartmentalized data silos, where users in one system cannot access data or applications in other areas.
This problem needs connectors which can import data from an on-premise database and provide it to hosted applications. The connector would need to synchronize both sets of data in order to make it work. This sort of solution can be developed and used in a number of ways. The exact methodology followed depends on criteria such as the company's IT capabilities and resources, its size and the deployment scope.
Traditionally, such tools would be developed in-house and housed on-premises along with the rest of the critical data. This is something an enterprise level customer would do, in order to maintain continuity with existing tools used to integrate applications available on the premises. The tools simply have to be expanded to include hosted applications and SaaS services.
To take this one step further, the connectors can be put on the cloud too. The only difference is that the integration setup does not have to be in-house. The customer still retains control over the tools and the ability to continue development with the help of a PaaS provider. This works nicely for companies that have the IT capability to develop tools and manage them, but do not want to add more IT hardware on the premises.
There are now SaaS providers that allow clients to use pre-developed tools as a service. This means the tools do not have to be developed or maintained, removing PaaS from the equation. All a company has to do now is to pay for use of a tool, with no other IT resources or investments required. This is just about ideal for customers who need this done quickly and without a big budget.
Not all enterprise customers can make do with a pre-developed SaaS solution. Their needs are likely to be more complex and require a fair bit of customization. It might be still be feasible if the deployment scope is limited, such as for a single division. As far as medium and small scale companies are concerned, the value in SaaS offerings is unbeatable.
Before getting into a cloud integration dance with a provider, it might be advisable to clarify a few aspects. One of these things is the ability to share data between separate clouds. Get a clear picture about how long the process is going to take, and what kind of training has to be provided to users. A lot of implementations fail not because of flaws, but due to delays and confused users simply unable to realize the potential of the integrated system.
About the Author:
Peggie K. Lambert loves working and research the world of data integration. If you are looking to learn more about integration as a service then she recommends you refer to Liaison.
No comments:
Post a Comment