Article Selections
Welcome to pick up some of article selections to read. Moreover look forward to your contribution!
-
Following 6 months of development Apache ShardingSphere 5.0.0-beta has been officially released!
-
After years of stagnation, ElasticJob is back with the first Apache version 3.0.0-alpha
-
News! The distributed scheduling project ElasticJob is about to restart
-
Congratulations on graduation of Apache ShardingSphere as a Top-Level Project
-
Revealing Sharding-Proxy —— Database Middleware Oriented DBA
A Step-by-Step Guide to Data Migration: Unlocking Distributed Database Potential with ShardingSphere
As businesses grow and data volumes and concurrent transactions surge, traditional standalone databases often face challenges related to performance, scalability, and availability. To overcome these limitations, the industry has introduced NoSQL solutions, employing techniques like data sharding and horizontal scaling. However, NoSQL databases often lack support for transactions and structured query language (SQL). This is where ShardingSphere comes into play. Apache ShardingSphere offers a distributed SQL transaction & query engine capable of transforming any conventional database into a distributed one. By leveraging advanced features like data sharding, elastic scaling, and data encryption, ShardingSphere ensures improved performance, scalability, and data security.
AWS Summit China 2023: ShardingSphere Highlights and Data Security Insights
The AWS Summit China 2023, held in Shanghai from June 27th to June 28th, brought together global leaders in the cloud computing sector. This two-day event featured over 100 leading companies and organizations, along with industry experts who delivered insightful speeches on reliable technology and services. From emerging technologies like generative AI to discussions on cloud-native technology and enterprise digitalization, the summit provided a platform for knowledge sharing and collaboration.
Chaos Engineering: Efficient Way to Improve System Availability
Resilience is a crucial requirement for ShardingSphere-Proxy, an essential database infrastructure. Testing and verifying resilience can be efficiently achieved through the use of chaos engineering methodology. To support customized chaos engineering, the ShardingSphere-on-Cloud project is designing and implementing a new CustomResourceDefinition (CRD) called Chaos. This post provides a practical description of CRD’s concept and features, helping the community better understand its potential benefits. What is chaos engineering System availability is a critical metric for evaluating service reliability. Numerous methods can ensure high availability, including engineering resilience and techniques, and others. One such technique is chaos engineering, which involves introducing software faults into production systems to enhance availability.
How to Run SQL Trace with ShardingSphere-Agent
Apache ShardingSphere, a data service platform that follows the Database Plus concept for distributed database systems, offers a range of features, including data sharding, read/write splitting, data encryption, and shadow database. In production environment, especially in data-sharding scenarios, SQL tracing is critical for monitoring and analyzing slow queries and abnormal executions. Therefore, a thorough understanding of SQL rewriting and query execution is crucial. What is ShardingSphere-Agent ShardingSphere-Agent provides an observable framework for ShardingSphere. It is implemented based on Java Agent technology, using Byte Buddy to modify the target bytecode and weave them into data collection logic. Metrics, tracing and logging functions are integrated into the agent through plugins to obtain observable data of system status. Among them, the tracing plugin is used to obtain the tracing information of SQL parsing and SQL execution, which can help users analyze SQL trace when using Apache ShardingSphere-JDBC or Apache ShardingSphere-Proxy.
Enhancing Database Security: ShardingSphere-Proxy’s Authentication
ShardingSphere-Proxy is a transparent database proxy that supports interaction with any client using MySQL, PostgreSQL, or openGauss protocols. Proxy provides user authentication and can adapt to different authentication modes for various database protocols. However, there is a question that has been rarely addressed and has almost no corresponding issue even in the Github community: “How does ShardingSphere-Proxy authenticate its clients?” Note: this post only discusses password authentication, and does not include non-password authentication methods such as UDS (Unix Domain Socket).
Simplifying Learning: ShardingSphere’s Template Engine for Streamlined Examples
After years of rapid development, ShardingSphere has grown significantly, offering six core functional modules that cater to various needs. It is also compatible with different registries, such as ZooKeeper and Nacos, allowing for seamless integration. Moreover, it supports distributed transactions and various development frameworks, providing flexibility and convenience. To ensure a user-friendly experience, we have created an example module that showcases the diverse functionalities, registries, and service frameworks of ShardingSphere.
How South Korea’s Yogiyo Improved Scalability and Performance with Apache ShardingSphere
Yogiyo is South Korea’s leading mobile and online food delivery platform that seeks to offer customers powerful and convenient food ordering services. Formerly a subsidiary of Delivery Hero, Yogiyo was acquired by GS Retail, one of Korea’s top ten listed companies, for $684 million at the end of 2021. Hello! My name is Byungchul Kim, and I work as a backend developer at Yogiyo R&D Centre on Orderyo, an ordering service. In this post, I want to share our experience implementing Apache ShardingSphere for Yogiyo’s order service and explain how it helped us to solve technical debt and meet new requirements.
Revamped ShardingSphere-On-Cloud: What’s New in Version 0.2.0 with CRD ComputeNode
Apache ShardingSphere-On-Cloud recently released version 0.2.0, which includes a new CRD ComputeNode for ShardingSphere Operator. This new feature enables users to define computing nodes fully within the ShardingSphere architecture. Introduction to ComputeNode In the classic architecture of Apache ShardingSphere, computing nodes, storage nodes, and governance nodes are the primary components. The computing node refers to the ShardingSphere Proxy, which acts as the entry point for all data traffic and is responsible for data governance capabilities such as distribution and balancing.
Monitoring SQL Performance with ShardingSphere-Agent, Prometheus and Grafana
As business systems become more complex, users are increasingly concerned about system performance and the need to monitor relevant metrics during system operation. This includes obtaining real-time monitoring metric information, monitoring and warning of relevant issues, and combining business analysis to locate anomalies. Application Performance Monitoring (APM) monitors and diagnoses system performance by collecting, storing, and analyzing system data that can be observed. Its main functions include performance metric monitoring, call chain analysis, and application topology maps. Generally, system operation status performance data is obtained through Metrics, Tracing, and Logging.
ShardingSphere 5.3.2 Release: Apollo Integration, Better Data Migration, and Stronger Encryption
Apache ShardingSphere has recently released version 5.3.2 after two months of development, which includes 797 PRs from teams and individuals worldwide. The new version includes significant improvements in functionality, performance, testing, documentation, and examples. With this update, users can experience an enhanced and problem-solving version. Let’s take a quick preview of what’s new: ShardingSphere Driver now supports Apollo, which is a great addition for users. Data migration now supports migrating tables with any index structure, including tables without an index, making it more convenient for users. The data encryption fuzzy query now supports the CONCAT function, improving the user’s experience. One of the highlights of this update is that the ShardingSphere Driver now supports Apollo. In version 5.3.0, ShardingSphere removed modules such as Spring Boot Starter and standardized the use of the standard JDBC Driver to specify configuration files. However, the ShardingSphere Driver could only read configuration from the file system, which was limited to scenarios where the configuration was managed uniformly in the configuration center. With the recent update, ShardingSphere 5.3.2 adjusted the configuration reading of the Driver to an SPI interface and achieved configuration reading from the Apollo configuration center.