Browse Prior Art Database

Client system DB Driver for data loading onto Cloud Infrastructure

IP.com Disclosure Number: IPCOM000199905D
Publication Date: 2010-Sep-21
Document File: 2 page(s) / 45K

Publishing Venue

The IP.com Prior Art Database

Abstract

As Cloud computing gains ground, issues such as security over the internet, data privacy etc. gain further importance. As enterprises leverage services hosted on Cloud for achieving business goals, it often becomes necessary to load business data including such confidential information as that of client and prospects over the internet. Cloud service providers may have come of age and offer satisfactory SLA for data security and transfer, however, the dilemma on part of companies to load their mission critical confidential data onto the internet remains. This disclousre offers an alternative to hosting data onto a cloud by allowing client database to be hosted on their premises. The essence of a transient service lies in not storing any part of the customer data on the internet and alloowing on demand access to the data from the premises of the client. Although, there has been an endeavour to access data on the Cloud (such as Zoho) and access the same using SQL, accessing data from client hosted machine within the boundaries of internet security for transient services remain an area unadressed.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 71% of the total text.

Page 1 of 2

Client system DB Driver for data loading onto Cloud Infrastructure

The system consists of a socket pair, a server socket hosted on the Cloud and a client socket hosted on the Company system, The Server socket is wrapped by standard database driver API such as JDBC for the cloud hosted service to easily invoke it from a datasource. For example, if the hosted service uses a database (for example DB2, Oracle etc), the server socket must implement the DB2 driver API. However, instead of making a call to a DB2 database, the server socket communicates the SQL over the internet to the Socket client that uses the database Driver to access the local database and send the response back to the client. The Server socket must implement the necessary API for Resource Adapter and must be able to participate in transactions as determined by the underlyring data system.

The socket client receives SQL from the Server, executes them on the comapny database. Taking the example database, they must invoke the local database driver and return the responses to the server. The server in turn returns the response to the hosted service (application) as if it were just another database driver. The responses are then returned to the client as usual.

It may be noted that in order to do away with usual internet security concerns such as DoS etc., the socket end point is implemented as a client on the company system and the server end point is hosted on the cloud such that the security measures...