Method and system for synchronization of relational database management system to non-structured query language database

A method and system for synchronization of Relational Database Management System (RDBMS) to non-Structured Query Language (noSQL) database receives a user request and associated predefined business logic from a user device for retrieving one or more transactional data and synchronizes the RDBMS to the noSQL database based on the predefined business logic. The database synchronization system segregates the predefined business logic into one or more processing divisions and assigning the one or more processing divisions to the RDBMS and the noSQL database. Further, the noSQL database retrieves data related to one or more elements of one or more tables related to the one or more transactional data from the RDBMS. Thereafter, the noSQL database transforms the retrieved data and provide to the database synchronization system. Finally, database synchronization system provides transformed data received from the noSQL database to the user device.

This application claims the benefit of Indian Patent Application Serial No. 201641009400, filed Mar. 17, 2016, which is hereby incorporated by reference in its entirety.

FIELD

The present subject matter is related in general to database management systems, and more particularly, but not exclusively to a method and a system for synchronization of Relational Database Management System (RDBMS) to non-Structured Query Language (noSQL) database.

BACKGROUND

Generally, enterprises maintain traditional databases such as relational databases for their users/customers. Most of the relational databases store a large amount of data in a tabular format. As an example, data may be related to transaction processes of customers in a banking enterprise. The data continuously grows over time in the relational databases and builds up to a large quantity. As size of the relational databases increase, performance of the relational database becomes a major concern. More problems are faced by the users using current technologies, such as mobile based technologies, that may require quick response, high speed data processing and analytical reporting. Also, accessing/retrieving data from a plurality of tables in the relational databases becomes difficult because of the increasing size of the relational databases. In spite of these issues, the enterprises do not prefer changing from relational databases to newer technologies as the relational databases are the legacy applications and contain data of high importance.

Currently, a hybrid data management system is provided wherein the hybrid data management system comprises a first data management system (e.g., NoSQL database) in sync with at least one additional connected data management system (e.g., large data store). The system further comprises data management logic, for receiving a read request from external application or a user, retrieving metadata and reading data object associated with the metadata. But the current method does not distribute the processing among the hybrid databases based on predefined management logic for fast and easy retrieval of data.

Therefore, there is need for a solution for configuring hybrid databases that helps in faster data retrieval for applications at users' devices, especially for mobile applications without impacting or changing the current application environment.

SUMMARY

One or more shortcomings of the prior art are overcome and additional advantages are provided through the present disclosure. Additional features and advantages are realized through the techniques of the present disclosure. Other embodiments and aspects of the disclosure are described in detail herein and are considered a part of the claimed disclosure.

Disclosed herein are a method and a system for synchronization of Relational Database Management System (RDBMS) to non-Structured Query Language (noSQL) database. A database synchronization system receives a predefined business logic associated with a user request. The predefined business logic is segregated and one or more actions to be performed based on the segregated predefined business logic are assigned to the respective databases. The segregation helps in distributing the processing overhead and workload between the RDBMS and the noSQL database which in turn helps in faster retrieval of data. Also, since the user device is in contact with the noSQL database, the retrieved data is directly provided to the user device without any Object-Relation Mapping (ORM) conversion. Thus, a lot of time is reduced in retrieval of the data based on user's request and also a new application is used in combination with the existing legacy application and customer environment without any changes.

Accordingly, the present disclosure comprises a method for synchronization of Relational Database Management System (RDBMS) to non-Structured Query Language (noSQL) database. The method comprises receiving, by a database synchronization system, a user request and associated predefined business logic from a user device for retrieving one or more transactional data. The one or more transactional data is stored in the RDBMS. Thereafter, the database synchronization system synchronizes the RDBMS to the noSQL database based on the predefined business logic. Further, the database synchronization system segregates the predefined business logic into one or more processing divisions and assigning the one or more processing divisions to the RDBMS and the noSQL database. The segregation is based on one or more actions to be performed based on the predefined business logic. Upon segregating the predefined business logic, the database synchronization system prompts the noSQL database to retrieve data related to one or more elements of one or more tables related to the one or more transactional data from the RDBMS. The RDBMS performs the one or more actions associated with the one or more processing divisions assigned to the RDBMS on the data related to the one or more elements of the one or more tables. Thereafter, the database synchronization system receives a transformed data from the noSQL database. The transformed data is formed by the noSQL database by performing the one or more actions associated with the one or more processing divisions assigned to the noSQL database on the retrieved data related to the one or more elements of the one or more tables. Finally, the database synchronization system provides the transformed data to the user device.

Further, the present disclosure comprises a database synchronization system for synchronization of Relational Database Management System (RDBMS) to non-Structured Query Language (noSQL) database. The database synchronization system comprises a processor and a memory communicatively coupled to the processor. The memory stores the processor-executable instructions, which, on execution, causes the processor to receive a user request and associated predefined business logic from a user device for retrieving one or more transactional data. The one or more transactional data is stored in the RDBMS. Upon receiving the request and the associated predefined business logic, the processor synchronizes the RDBMS to the noSQL database based on the predefined business logic. Further, the processor segregates the predefined business logic into one or more processing divisions and assigning the one or more processing divisions to the RDBMS and the noSQL database. The segregation is based on one or more actions to be performed based on the predefined business logic. Upon segregating the business logic, the processor prompts the noSQL database to retrieve data related to one or more elements of one or more tables related to the one or more transactional data from the RDBMS. The RDBMS performs the one or more actions associated with the one or more processing divisions assigned to the RDBMS on the data related to the one or more elements of the one or more tables. Further, the processor receives a transformed data from the noSQL database. The transformed data is formed by the noSQL database by performing the one or more actions associated with the one or more processing divisions assigned to the noSQL database on the retrieved data related to the one or more elements of the one or more tables. Finally, the processor provides the transformed data to the user device.

DETAILED DESCRIPTION

The present disclosure comprises a method and a system or apparatus for synchronization of Relational Database Management System (RDBMS) to non-Structured Query Language (noSQL) database. The method comprises receiving, by a database synchronization system, also known in this example as a database synchronization computing apparatus, a user request and associated predefined business logic from a user device for retrieving one or more transactional data. The one or more transactional data is stored in the RDBMS. Thereafter, the database synchronization system synchronizes the RDBMS to the noSQL database based on the predefined business logic. Further, the database synchronization system segregates the predefined business logic into one or more processing divisions and assigning the one or more processing divisions to the RDBMS and the noSQL database. The segregation is based on one or more actions to be performed based on the predefined business logic. Upon segregating the predefined business logic, the database synchronization system prompts the noSQL database to retrieve data related to one or more elements of one or more tables related to the one or more transactional data from the RDBMS. The RDBMS performs the one or more actions associated with the one or more processing divisions assigned to the RDBMS on the data related to the one or more elements of the one or more tables. Thereafter, the database synchronization system receives a transformed data from the noSQL database. The transformed data is formed by the noSQL database by performing the one or more actions associated with the one or more processing divisions assigned to the noSQL database on the retrieved data related to the one or more elements of the one or more tables. Finally, the database synchronization system provides the transformed data to the user device.

FIG. 1Ashows an exemplary architecture for synchronization of Relational Database Management System (RDBMS) to non-Structured Query Language (noSQL) database in accordance with an embodiment of the present disclosure.

The architecture100comprises a user device103, a communication network104, a database synchronization system105, a Relational Database Management System (RDBMS)107and a non-Structured Query Language (noSQL) database108. As an example, the user device103may include, but not limited to, a mobile, a laptop, a tablet and a desktop. The communication network104may include, but not limited to, a wired communication network, a wireless communication network and a suitable combination thereof. As an example, the RDBMS107may include, but not limited to, Oracle, MySQL, SQL server and PostgreSQL. As an example, the noSQL database108may include, but not limited to MongoDB (Mongo Database), Lotusnotes, RethinkDB (Rethink Database) and CouchDB (Couch Database).

A user of the user device103sends a request to the database synchronization system105through the communication network104. As an example, the user may include, but not limited to, a customer, a shareholder, a manager and a developer. The user request is for retrieving one or more transactional data. In an embodiment, the one or more transactional data is stored in the RDBMS107. In an embodiment, the RDBMS107may be running on Z environment or a distributed environment. The request/user request is associated with predefined business logic by the database synchronization system105. As an example, the user may send a user request to retrieve the current account balance of the user's account using a bank website. The predefined business logic associated with the user's request to retrieve the current account balance may be “retrieve the column “current account balance”” from the table stored in the RDBMS107. In one embodiment, the database synchronization system105is present outside the noSQL database108as shown inFIG. 1A. In another embodiment, the database synchronization system105maybe present within the noSQL database108as shown inFIG. 1B.

The database synchronization system105comprises a processor109, an I/O interface111and a memory113. The I/O interface111is configured to receive the user request from the user device103via the communication network104. The memory113is communicatively combined to the processor109. The processor109synchronizes the RDBMS107to noSQL database108based on the predefined business logic. Since the synchronization of the RDBMS107and the noSQL database108is based on the predefined business logic, complete synchronization of the RDBMS107to the noSQL database108is not performed. Only a part of the RDBMS107associated with the predefined business logic is synchronized with the noSQL database108since the RDBMS107is a legacy database and handles large amounts of transaction workload. Also, data in the RDBMS107may keep getting updated, inserted or deleted as a result of which complete synchronization may be a complex process and time consuming. Based on frequency at which the data in the RDBMS107is getting updated, inserted or deleted, the noSQL database108may fail to be in sync with the RDBMS107. Therefore, to maintain the RDBMS107and the noSQL database108in sync, synchronization of the RDBMS107to the noSQL database108may be performed at real time or the synchronization may be time bound. The processor109captures the changes occurred in RDBMS107and updates the noSQL database108based on the captured changes.

Upon synchronizing the RDBMS107to the noSQL database108, the processor109segregates the predefined business logic into one or more processing divisions. The one or more processing divisions are the divisions generated for performing processing steps on the one or more transactional data using one or more actions. In an embodiment, the processor109learns the one or more actions to be performed on the one or more transactional data upon receiving the user request. As an example, the one or more actions may include, but not limited to, at least one of cleansing, validation, complex calculations, normalization, consolidation, grouping, filtering or conversion performed on the data related to one or more elements of the one or more tables. Upon segregating the predefined business logic into one or more processing divisions, the processor109assigns the one or more processing divisions to the RDBMS107and the noSQL database108. In an embodiment, segregating and assigning some part of the one or more processing divisions to RDBMS107and remaining part to the noSQL database108is configurable. As an example, the one or more processing divisions including the one or more actions like cleansing, complex calculations, validation and normalization may be assigned to the RDBMS107to eliminate the I/O overload through the communication network104. As an example, the rest of the one or more processing divisions including the one or more actions like consolidating, grouping, filtering and conversion may be assigned to the noSQL database108.

Upon assigning the one or more processing divisions, the processor109, prompts the noSQL database108to retrieve the one or more transactional data from the RDBMS107. The noSQL database108may select only data related to one or more elements of one or more tables related to the one or more transactional data from the RDBMS107for retrieval. The RDBMS107performs the one or more actions associated with the one or more processing divisions assigned to the RDBMS107on the data related to the one or more elements of the one or more tables before retrieval by the noSQL database108. In an embodiment, the RDBMS107may use stored procedures to perform the one or more actions. The noSQL database108retrieves the data related to the one or more elements of the one or more tables on which the RDBMS107has performed the one or more actions, using a predefined Application Program Interface (API). As an example, the predefined API may be a REST API. The REST API provides quick development cycles for the user as the REST API retrieves only the data related to one or more elements of the one or more tables based on the predefined business logic.

Upon retrieving the data related to one or more elements of the one or more tables on which the RDBMS107has performed the one or more actions, the noSQL database108transforms the retrieved data. The noSQL database108transforms the retrieved data by performing the one or more actions associated with the one or more processing divisions assigned to the noSQL database108. Upon transforming the retrieved data, the transformed data is sent to the database synchronization system105by the noSQL database108. The I/O interface111receives the transformed data from the noSQL database108. The transformed data is finally provided to the user device103as a response to the user request received.

As an example, consider a scenario where an enterprise has branches in 5 cities of India. The 5 cities where the enterprise has its branches are Bangalore, Hyderabad, Calcutta, Chennai and Mumbai. The user sends the request using the user device103. The user request is to get a consolidated report indicating average salary of all employees belonging to Computer Science (CS) department of the enterprise for Bangalore and Chennai branches and total amount spent for employees' salary for both the branches. The user request also comprises a request for individual reports of Bangalore and Chennai branches indicating the average salaries of the employees' belonging to the CS department. In an embodiment, all the departments available in the enterprise are CS, Electronics and Telecommunication (EC) and Telecommunication (TC). The predefined business logic associated with the user request may be “determine average salary of employees report for Bangalore branch: determine average salary of employees report for Chennai branch: consolidate employees report for Bangalore and Chennai branches: determine average salary of employees' report of both Bangalore: determine total amount spent on employees salary in both Bangalore and Chennai branches together and present the data to the user”. The predefined business logic is sent along with the user request to the database synchronization system105.

The Employee (also referred as Emp) table for Bangalore branch as stored in the RDBMS107is shown in the below Table 1.

The Employee (also referred as Emp) table for Chennai branch as stored in the RDBMS107is shown in the below Table 2.

As the processor109synchronizes the RDBMS107and the noSQL database108based on the predefined business logic i.e. only the data related to the user request may be synchronized using the predefined business logic. Therefore, the processor109synchronizes only the Table 1 and Table 2 present in the RDBMS107with the noSQL database108based on the predefined business logic. The predefined business logic is segregated into the one or more processing divisions based on the one or more actions to be performed based on the predefined business logic. Further, the one or more processing divisions are assigned to the RDBMS107and the noSQL database108. In this scenario, one of the one or more processing divisions of the predefined business logic comprising “determine average salary of employees report for Bangalore branch: determine average salary of employees report for Chennai branch” is assigned to the RDBMS107. The rest of the one or more processing divisions comprising “consolidate employees report for Bangalore and Chennai branches: determine average salary of employees' report of both Bangalore: determine total amount spent on employees' salary in both Bangalore and Chennai branches together and present the data to the user” is assigned to the noSQL database108. Thereafter, the database synchronization system105prompts the noSQL database108to retrieve the data related to one or more elements of the tables Table 1 and Table 2. The noSQL database108selects the data related to the one or more elements of the Table 1. The selected one or more elements are as shown in the below Table 3.

The noSQL database108selects the data related to the one or more elements of the Table 2. The selected one or more elements are as shown in the below Table 4.

The RDBMS107performs the mathematical calculations and determines the average salary of Bangalore branch based on the employee salary shown in Table 3. The average employee salary of the Bangalore branch obtained upon performing the mathematical calculations is as shown in the below Table 5.

The RDBMS107performs the mathematical calculations to determine the average salary of Chennai branch based on the employee salary shown in Table 4. The average employee salary of the Chennai branch obtained upon performing the mathematical calculations is as shown in the below Table 6.

Further, the RDBMS107performs the mathematical calculations to determine average salary of the employees of the CS department of both Bangalore and Chennai branches. The average employee salary of the Bangalore and Chennai branches together, obtained upon performing the mathematical calculations is as shown in the below Table 7.

Finally, the RDBMS107performs the mathematical calculations to determine total amount spent on employees' salary in both Bangalore and Chennai branches together. The total amount of the Bangalore and Chennai branches together, obtained upon performing the mathematical calculations is as shown in the below Table 8.

Upon performing the mathematical calculations, the RDBMS107allows the retrieval of Table 3, Table 4, Table 5, Table 6, Table 7 and Table 8 by the noSQL database108.

Upon retrieving the Table 5 and Table 6, noSQL database108first performs consolidation of the reports of the Bangalore and the Chennai branch. Bangalore_Chennai_Consolidated_Emp_report: [

Upon consolidating the reports of Bangalore and Chennai branches, the noSQL database108provides the information to the user of the user device103as shown below:

Average salary of CS employees in Bangalore branch: Rs.40666.67.

Average salary of CS employees in Bangalore branch: Rs.55000.

Average salary of CS employees in Bangalore and Chennai branch: Rs.48857.14.

Total amount spent on salary of CS employees in Bangalore and Chennai branch: Rs.3, 42,000.

As an example, consider another scenario where the user may request for 95thpercentile of salaries of all the employees for both Bangalore and Chennai branches. The predefined business logic associated with the user request may be “determine 95thpercentile of salaries for Bangalore and Chennai branches”. The predefined business logic is sent along with the user request to the database synchronization system105.

Based on the predefined business logic, the RDBMS107determines the 95thpercentile of the salaries of all the employees for both Bangalore and Chennai branches.

To calculate the 95thpercentile, the RDBMS107first combines the elements of Table 1 and Table 2 and sorts the elements in descending order of the employees' salary as shown in the below Table 9.

The RDBMS107uses the Equation 1 as shown below to determine the 95thpercentile.
95thpercentile value=((95/100)*n)  Equation 1

In the above Equation 1, n indicates the total number of employees from the Bangalore and the Chennai branches. Since there are 14 elements in the scenario, n is 14. The values are substituted to the Equation 1 and 95thpercentile is obtained as shown below:
95thpercentile value−((95/100)*14)=13.3=13

Therefore, the RDBMS selects the 13thvalue from list of the elements of Table 1 and Table 2 that have been sorted in the descending order of the employees' salary as shown in the below Table 10. The 13thvalue is second largest value in the list.

TABLE 1095thpercentile on employee SalaryRs.65000

The noSQL database108retrieves and stores the 95thpercentile value of all the employees of the Bangalore and the Chennai branch as shown below.

Further, the noSQL database108represents the 95thpercentile value of all the employees of the Bangalore and the Chennai branch to the user as shown below.

The 95thpercentile of employees' salary from Bangalore and Chennai branch: Rs.65000

FIG. 2shows a detailed block diagram of a database synchronization system for synchronization of Relational Database Management System (RDBMS) to non-Structured Query Language (noSQL) database in accordance with some embodiments of the present disclosure.

In one implementation, an I/O interface111configured in the database synchronization system105receives data203from a user device103. As an example, the data203is stored in a memory111configured in the database synchronization system105as shown inFIG. 2. In one embodiment, data203includes predefined business logic data207, retrieved data209, transformed data211and other data213.

In the illustratedFIG. 2, modules205are described herein in detail.

In one embodiment, the data203may be stored in the memory113in the form of various data structures. Additionally, the aforementioned data can be organized using data models, such as relational or hierarchical data models. The other data213may store data, including temporary data and temporary files, generated by modules205for performing the various functions of the database synchronization system105.

In an embodiment, the predefined business logic data207comprises predefined business logic. Each user request has a predefined business logic associated with it. When a user sends a user request for one or more transactional data, the predefined business logic associated with the user request is provided to the database synchronization system105along with the user request.

In an embodiment, the retrieved data209comprises the data retrieved by the noSQL database108from the Relational Database Management System (RDBMS)107. The retrieved data209from the RDBMS107by the noSQL database108comprises data related to one or more elements of the one or more tables related to the one or more transactional data. The retrieved data209is processed by the RDBMS107based on one or more processing divisions assigned to the RDBMS107.

In an embodiment, the transformed data211comprises the data transformed by the noSQL database108. The transformed data211is formed by processing the retrieved data209by the noSQL database108, based on one or more processing divisions assigned to the noSQL database108.

In an embodiment, the data203stored in the memory113is processed by the modules205of the database synchronization system105. The modules205may be stored within the memory113. In an example, the modules205, communicatively coupled to a processor109configured in the database synchronization system105, may also be present outside the memory113as shown inFIG. 2and implemented as hardware. As used herein, the term module may refers to an application specific integrated circuit (ASIC), an electronic circuit, a processor109(shared, dedicated, or group) and memory113that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality.

In an embodiment, the modules205may include, for example, a receiving module215, a synchronizing module217, a segregating module219, a prompting module221, a transmitting module223and other modules225. The other modules225may be used to perform various miscellaneous functionalities of the database synchronization system105. It will be appreciated that such aforementioned modules205may be represented as a single module or a combination of different modules.

In an embodiment, the receiving module215receives the user request from the user device103. The user request comprises a request for retrieving one or more transactional data. The processor109also receives the predefined business logic associated with the user request.

In an embodiment, the synchronizing module217synchronizes the RDBMS107and the noSQL database108based on the predefined business logic. The complete synchronization of the RDBMS107to the noSQL database108is not only a part of the RDBMS107associated with the predefined business logic is synchronized with the noSQL database108.

In an embodiment, the segregating module219segregates the predefined business logic into one or more processing divisions. In an embodiment, the predefined business logic is segregated by the segregating module219based on one or more actions to be performed on the one or more transactional data. As an example, the one or more actions may include, but not limited to, at least one of cleansing, validation, complex calculations, normalization, consolidation, grouping, filtering or conversion performed on the data related to one or more elements of the one or more tables. Upon segregating the predefined business logic into one or more processing divisions, the processor109assigns the one or more processing divisions to the RDBMS107and the noSQL database108. In an embodiment, segregating and assigning some part of the one or more processing divisions to RDBMS107and remaining part to the noSQL database108is configurable. In an embodiment, the prompting module221prompts the noSQL database108to retrieve the one or more transactional data from the RDBMS107. The noSQL database108may select only data related to one or more elements of one or more tables related to the one or more transactional data from the RDBMS107for retrieval. The RDBMS107performs the one or more actions associated with the one or more processing divisions assigned to the RDBMS107on the data related to the one or more elements of the one or more tables before retrieval by the noSQL database108. The noSQL database108retrieves the data related to the one or more elements of the one or more tables on which the RDBMS107has performed the one or more actions, using a predefined Application Program Interface (API). As an example, the predefined API may be a REST API. Further, the noSQL database108transforms the retrieved data209. The retrieved data209is transformed by performing the one or more actions associated with the one or more processing divisions assigned to the noSQL database108. As an example, the transformation may include consolidation of the retrieved data, making the retrieved data presentable etc. Upon transforming the retrieved data209, the transformed data211is sent to the database synchronization system105.

In an embodiment, the receiving module215further receives the transformed data211from the noSQL database108. As an example, consider the scenario as explained inFIG. 1. The transformation is done to the retrieved data for making the information presentable for user's understanding. The transformed data is as shown below:

Average salary of CS employees in Bangalore branch: Rs.40666.67.

Average salary of CS employees in Bangalore branch: Rs.55000.

Average salary of CS employees in Bangalore and Chennai branch: Rs.48857.14.

Total amount spent on salary of CS employees in Bangalore and Chennai branch: Rs.3, 42,000.

In an embodiment, the transmitting module223provides the transformed data211received from the noSQL database108to the user device103. The transformed data211is finally provided to the user device103as a response to the user request received by the receiving module215.

FIG. 3illustrates a flowchart for synchronization of Relational Database Management System (RDBMS) to non-Structured Query Language (noSQL) database in accordance with some embodiments of the present disclosure.

As illustrated inFIG. 3, the method300comprises one or more blocks illustrating a method for synchronization of Relational Database Management System (RDBMS) to non-Structured Query Language (noSQL) database. The method300may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform particular functions or implement particular abstract data types.

At block301, the database synchronization system105receives a user request and predefined business logic. The user request comprises a request for retrieving one or more transactional data. In an embodiment, the user request sent from a user device103is associated with the predefined business logic. As an example, the user device103may include, but not limited to, a mobile, a laptop, a tablet and a desktop. An I/O interface111configured in the database synchronization system105receives the user request and the predefined business logic associated with the user request.

At block305, the database synchronization system105segregates the predefined business logic and assigns to the RDBMS107and the noSQL database108. In an embodiment, the processor109segregates the predefined business logic into one or more processing divisions. The predefined business logic is segregated by the processor109based on one or more actions to be performed on the one or more transactional data. As an example, the one or more actions may include, but not limited to, at least one of cleansing, validation, complex calculations, normalization, consolidation, grouping, filtering or conversion performed on the data related to one or more elements of the one or more tables. Upon segregating the predefined business logic into one or more processing divisions, the processor109assigns the one or more processing divisions to the RDBMS107and the noSQL database108. In an embodiment, segregating and assigning some part of the one or more processing divisions to RDBMS107and remaining part to the noSQL database108is configurable. As an example, the one or more processing divisions including the one or more actions like cleansing, complex calculations, validation and normalization may be assigned to the RDBMS107to eliminate the I/O overload through the communication network104. As an example, the rest of the one or more processing divisions including the one or more actions like consolidating, grouping, filtering and conversion may be assigned to the noSQL database108.

At block307, the database synchronization system105prompts the noSQL database108to retrieve the one or more transactional data from the RDBMS107. The noSQL database108may select only data related to one or more elements of one or more tables related to the one or more transactional data from the RDBMS107for retrieval. The RDBMS107performs the one or more actions associated with the one or more processing divisions assigned to the RDBMS107on the data related to the one or more elements of the one or more tables before retrieval by the noSQL database108. The noSQL database108retrieves the data related to the one or more elements of the one or more tables on which the RDBMS107has performed the one or more actions, using a predefined Application Program Interface (API). As an example, the predefined API may be a REST API. At block309, the database synchronization system105receives transformed data211from the noSQL database108. In an embodiment, the noSQL database108transforms the data retrieved from the RDBMS107, i.e. retrieved data209. The noSQL database108transforms the retrieved data209by performing the one or more actions associated with the one or more processing divisions assigned to the noSQL database108. Upon transforming the retrieved data209, the transformed data211is sent to the database synchronization system105by the noSQL database108. The I/O interface111receives the transformed data211from the noSQL database108upon performing the transformation.

At block311, the database synchronization system105provides the transformed data211to the user device103. In an embodiment, the I/O interface111provides the transformed data211to the user device103as a response to the user request received from the user device103.

FIG. 4is a block diagram of an exemplary computer system for implementing embodiments consistent with the present disclosure.

In an embodiment, the database synchronization system400is used for synchronization of Relational Database Management System (RDBMS) to non-Structured Query Language (noSQL) database. The database synchronization system400may comprise a central processing unit (“CPU” or “processor”)402. The processor402may comprise at least one data processor for executing program components for executing user- or system-generated business processes. A user may include a person, a person using a device such as such as those included in this invention, or such a device itself. The processor402may include specialized processing units such as integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc.

Using the I/O interface401, the database synchronization system400may communicate with one or more I/O devices (411and412).

In some embodiments, the processor402may be disposed in communication with a communication network409via a network interface403. The network interface403may communicate with the communication network409. The network interface403may employ connection protocols including, without limitation, direct connect, Ethernet (e.g., twisted pair 10/100/1000 Base T), Transmission Control Protocol/Internet Protocol (TCP/IP), token ring, IEEE 802.11a/b/g/n/x, etc. Using the network interface403and the communication network409, the database synchronization system400may communicate with one or more data sources410(a, . . . , n). The communication network409can be implemented as one of the different types of networks, such as intranet or Local Area Network (LAN) and such within the organization. The communication network409may either be a dedicated network or a shared network, which represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), etc., to communicate with each other. Further, the communication network409may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, etc. The one or more data sources410(a, . . . , n) may include, without limitation, personal computer(s), mobile devices such as cellular telephones, smartphones, tablet computers, eBook readers, laptop computers, notebooks, gaming consoles, or the like.

The memory405may store a collection of program or database components, including, without limitation, user interface application406, an operating system407, web server408etc. In some embodiments, database synchronization system400may store user/application data406, such as the data, variables, records, etc. as described in this invention. Such databases may be implemented as fault-tolerant, relational, scalable, secure databases such as Oracle or Sybase.

ADVANTAGES OF THE EMBODIMENT OF THE PRESENT DISCLOSURE ARE ILLUSTRATED HEREIN

In an embodiment, the present disclosure provides a method and a system for synchronization of Relational Database Management System (RDBMS) to non-Structured Query Language (noSQL) database.

The present disclosure works in combination with legacy applications. Therefore, adapting to the method provided in the present disclosure is safe and reliable.

The present disclosure provides a feature wherein the predefined business logic is segregated into one or more processing divisions based on one or more actions to be performed on the one or more elements retrieved from one or more tables. Therefore, the processing overhead and the workload are distributed among the RDBMS and the noSQL database leading to faster retrieval of data.

The present disclosure provides a feature wherein the user is in connection with only noSQL database through the database synchronization system. Therefore, when the noSQL database provides the one or more transactional data to the user device, Object-Relation Mapping (ORM) conversion is not required.

The present disclosure provides quick response and high speed data process for communicating with the hybrid database especially for the user devices using mobile based technology.

The present disclosure may be implemented in any current customer environment without changing or impacting their current production environment. The present disclosure can be implemented for all relational databases running on Z or distributed environment.