1 Answer
- Newest
- Most votes
- Most comments
0
Depends on how your customer defines near-real-time you have few options but there are various costs and consideration with all that :
- WAL replication to kinesis : https://aws.amazon.com/blogs/database/stream-changes-from-amazon-rds-for-postgresql-using-amazon-kinesis-data-streams-and-aws-lambda/. This will take up resources from your primary but you can reduce that by setting up replica.
- Scheduled Jobs that does S3 exports of changed data. This is the least expensive as you can decide what tables to export data from and how often. You can decide to do that every 10 mins or so. AWS Batch can be used with Lambda to accomplish this.
- Upgrade to Aurora and utilize database streams. This way you have minimal impact on writer and you can just convert SQL statements to data files using lambda.
- Use DMS with RDS as source and S3 as target. Like #1 i would recommend you set it up on replica.
answered 3 years ago
Relevant content
- asked 5 months ago
- asked 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago