Intl-English
  • Intl-繁体中文
  • Intl-简体中文
Business Challenge

High database concurrency and the need for real-time expansion during peak periods

The rapid development of customer businesses necessitates on-demand expansion of database storage and machines

Lack of database ecosystem services

Database migration, synchronization and evaluation, DBA inspections, and transparent database link access are constant daily needs; open-source databases lack appropriate scenario-based features with visual ecosystem tools

Single point of failure in databases

Open-source MySQL and PostgreSQL lack enterprise-level high availability and read-write separation solutions, making databases prone to failures on a single machine

Database disaster recovery risk considerations

Core business data of enterprises requires disaster recovery; setting up and maintaining disaster recovery environments requires a professional technical team

Application Scenario
General database business scenario for the new energy manufacturing industry

The SDP system serves as an integrated data center system for new energy battery after-sales; new business plans involve large data volumes and require real-time queries. The original system used a monolithic open-source MySQL database, which cannot meet massive data and performance requirements, while the use of HANA commercial databases would incur huge costs and have certain technical learning barriers. Customers need a cost-effective, high-performance database capable of smooth upgrade and migration

Disaster recovery scenario for smart parking databases

The xx Group, in collaboration with China Telecom, developed the “xx City Brain Smart Parking System” to address urban parking challenges such as parking difficulty, exit difficulty, and payment difficulty. The system, relying on the “xx City” app, integrates mainstream payment channels and full-process information channels. The smart parking system was launched in 2020 on the “xx City” app and has been promoted in 20 cities, connecting nearly 50,000 public parking spaces and serving over 1.5 million vehicles and millions of users

Business scenario for de-IOE cloud transition

Starting from the IT investment cost and software autonomy of the enterprise, Tianyi Cloud uses the independently controllable TeleDB for MySQL to fully promote de-IOE. The core systems, focused on CRM and billing/accounting domains, extensively use Oracle’s complex multi-table association, multi-layer nested query features, as well as unique database objects and stored procedures, making the transition to MySQL highly difficult and requiring significant work

Overall Structure
Introduction
Massive high concurrency core data systems exceed the processing capacity limit of a single machine. TeleDB for HTAP has horizontal elastic scalability to handle rapid growth in data volume and throughput, also providing highly compatible MySQL protocol interfaces and features such as global transactions and unique indexes.
Architecture Characteristics

One-stop With high-performance, scalable real-time writing capabilities, it also has a powerful distributed query engine providing excellent complex query performance while ensuring data consistency and read-write real-time High availability Core components PD, TiDB, and TiKV are all multi-node distributed; failure of some component instances will not affect the availability of the entire cluster Scalability Both the computing layer TiDB and the storage layer TiKV can perform horizontal elastic scale-out, enhancing system data capacity and throughput ability

Contact Us

We use cookies to ensure your high-speed browsing experience. By continuing to browse this site, you agree to our use of cookies. Details