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
Use AWS CloudFormation to create ShardingSphere HA clusters
What’s AWS CloudFormation? AWS CloudFormation is an infrastructure as code (IaC) service that allows you to easily model, provision, and manage all the cloud services provided by AWS by custom templates. Traditionally, when we create a new architecture, we need to manually configure it in AWS step by step which can cause some errors such forgetting some steps. Now with CloudFormation, we can use declarative configuration to define resources and then create and manage them without worrying about the dependency order of the resources.
ShardingSphere 5.3.0 is released: new features and improvements
After 1.5 months in development, Apache ShardingSphere 5.3.0 is released. Our community merged 687 PRs from contributors around the world. The new release has been improved in terms of features, performance, testing, documentation, examples, etc. The 5.3.0 release brings the following highlights: Support fuzzy query for CipherColumn. Support Datasource-level heterogeneous database. Support checkpoint resume for data consistency check. Automatically start a distributed transaction, while executing DML statements across multiple shards. Additionally, release 5.3.0 also brings the following adjustments:
ShardingSphere-on-Cloud & Pisanix replace Sidecar for a true cloud-native experience
Background For a while, many of our blog posts have shown that ShardingSphere consists of three independent products: ShardingSphere-JDBC, ShardingSphere-Proxy, and ShardingSphere-Sidecar. As ShardingSphere has become increasingly popular, JDBC and Proxy have been used in numerous production environments, but Sidecar’s status has remaining as “under planning”. you may have noticed this on our GitHub READ ME or our website. With cloud-native gaining momentum, many enterprises are choosing to use databases on the cloud or cloud native databases. This represents an excellent opportunity for ShardingSphere-Sidecar, which is positioned as a cloud-native database proxy in Kubernetes.
ElasticJob UI now supports Auth 2.0, OIDC and SAML single sign-on thanks to Casdoor
If you’re looking to add SSO to the administration console when using ElasticJob UI, this article will help you tackle this user management problem using ElasticJob UI’s built-in Casdoor. Background ElasticJob UI is the visual admin console of ElasticJob, whose target users are developers and DevOps teams rather than users. Generally, it is deployed only in the internal environment and thus its R&D focus more on its features.
Alibaba Cloud's OpenSergo & ShardingSphere release database governance standard for microservices - combining Database Plus and Database Mesh concepts
Background Recently, Alibaba Cloud’s OpenSergo and ShardingSphere jointly released the database governance standard for microservices. By combining the Database Plus and Database Mesh concepts, the two communities have standardized the existing database governance concepts, patterns, and paths, further completing the database governance ecosystem under the cloud-native environment. The founders of both communities expressed their opinions concerning the collaboration between the ShardingSphere community and the OpenSergo community: Zhang Liang, the PMC Chair of the Apache ShardingSphere community:
ElasticJob 3.0.2 is released including failover optimization, scheduling stability, and Java 19 compatibility
ElasticJob, one of the sub-projects of the Apache ShardingSphere community, is a distributed scheduling solution oriented towards Internet applications and massive tasks. Since ElasticJob 3.0.1 was released, we’ve received a lot of feedback from users on GitHub. After merging the code committed by the contributors, ElasticJob has been significantly optimized. The resulting ElasticJob 3.0.2 has been improved in terms of Failover, scheduling stability, job API, and Java 19 compatibility. Release 3.0.2 Key Features Failover Optimization Failover is an important ElasticJob feature.
ShardingSphere 5.2.1 is released — Here are the highlights
Our new 5.2.1 release brings new features and enhancements such as the ShardingSphere system database, SQL HINT mandatory sharding routing, asynchronous data consistency check, and support for Consul and Nacos governance center. Introduction Following 1.5 months in development, Apache ShardingSphere 5.2.1 is released. Our community merged 614 PRs from teams and individuals around the world. The resulting 5.2.1 release has been optimized in terms of features, performance, testing, documentation, examples, etc.
ShardingSphere 5.2.0: Audit for sharding intercepts unreasonable requests in multi-shards scenarios
1. Background Thanks to our continuous review of the ShardingSphere’s community feedback that we use to develop features such as data sharding and read/write splitting, we found that some users create a large number of shards when using the data sharding feature. In such cases, there can be 1,000 physical tables corresponding to a sharding logical table, which largely disturbs users. For instance, a SELECT * FROM t_order statement will lead to a full-route, which is obviously not the case for OLTP. This SQL can be placed in another Proxy to avoid blocking other requests.
How does ShardingSphere’s Show processlist & Kill Work?
For those of you who often use databases, you may wonder: How do I check what SQL is currently being executed by the database, and in what state? How do I terminate abnormal SQL? For instance, if a SELECT statement used to query a table with massive data does not carry query conditions, it would drag down the performance of the entire database. This may push to want to terminate this abnormal SQL.
Apache ShardingSphere 5.2.0 is Released!
Our new 5.2.0 release enhances features such as SQL audit, elastic migration, SQL execution process management, and data governance on the cloud. Introduction Since Apache ShardingSphere released version 5.1.2 at the end of June, our community has continued to optimize and enhance its product features. The community merged 1,728 PRs from teams and individuals around the world. The resulting 5.2.0 release has been optimized in terms of its features, performance, testing, documentation, examples, etc.