Update README Featured Section with AWS Blog on RDS, XA Transactions #485
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Description:
This PR updates the README's "Featured" section by adding a new AWS blog post.
The post details the use of Amazon RDS, XA transactions, Amazon Kinesis, and AWS Lambda for data replication to Amazon OpenSearch Service.
You can check the source code used in the example here
Why Include This Post?
First Post : Focuses on real-time MySQL binary log replication via Kinesis.
Second Post : Discusses Kinesis and Lambda for data transfer to DynamoDB.
New Post : Adds complexity by covering XA transactions and OpenSearch Service replication.
This new entry complements our existing featured posts by showcasing another layer of data replication complexity. More importantly, these posts collectively highlight the versatility and robustness of python-mysql-replication across different data pipeline scenarios.
We look forward to your feedback and additional suggestions.