Why We Created DBPlusEngine #

With the advent of digital transformation, the business needs of enterprises iterate rapidly, and the amount of data and concurrent visits increased exponentially. The traditional relational database face challenges of limited expansion capacity and low big data processing performance.

Data is becoming more and more important to enterprises. On the one hand, enterprises have increasingly urgent demand for professional services with database as the core. On the other hand, enterprises are also waiting for the new database to meet the application needs of different data scenarios.

The database is rapidly evolving. However, due to the complex technical system of enterprise database, the gap between various databases is obvious and the management is difficult. Controlling cost and improving efficiency are the long-term and constant demands of enterprises for the underlying database. Therefore, under the multi-directional role, enterprises need service providers to be able to provide horizontal mainstream database products and vertical multi-version technical service coverage, to face the demands from insensitive to solve the diversified needs of users and the common problems on the industry side and form solutions. In this case, the utilization of data and the transformation of underlying architecture are particularly urgent. It may be a feasible way to improve the flexibility and scalability of the database and build a component database.

Based on the Database Plus concept proposed by Apache ShardingSphere, SphereEx-DBPlusEngine promotes the design and implementation of Apache ShardingSphere’s microkernel and pluggable architecture model, provides community users with lightweight and flexible component open source products, and also provides a unified entrance to incremental functions for enterprise products.

SphereEx-DBPlusEngine is not satisfied with the positioning of its database middleware tool, and began to transform towards platform and ecology. The practice of DatabasePlus makes the SphereEx-DBPlusEngine not only shield the underlying details between various databases, but also make up for the differences between various shardings of distributed database. Specifically, through the flexible adaptation of database protocol, SQL dialect and database storage, developers can quickly connect applications with heterogeneous databases, so that developers do not need to pay attention to the differentiation of SQL dialect and focus on business research and development.

Based on the ecology of this layer of database, SphereEx-DBPlusEngine takes the database as the final storage node and meets various database protocols, SQL dialects and database drop docking at the access end, so as to provide various incremental capabilities to the database application architecture on this layer of storage nodes. Therefore, users can regard SphereEx-DBPlusEngine as a “database gateway”, which can obtain the access traffic of the database and provide transparent functions such as traffic redirection (data sharding, read-write splitting, shadow DB), traffic deformation (data encryption, data desensitization), traffic authentication (security, audit, authority), traffic governance (fusing, flow restriction) and traffic analysis (service quality analysis, observability), these enhancements make SphereEx-DBPlusEngine the strongest partner of database products. Users do not need to worry about how to uniformly manage various databases. The mainstream authentication and governance functions can be completed through the expansion of DistSQL.