1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Hi, many thanks for your question.
I'd suggest taking a look at AWS Database Migration Service that can stream changes from PostgreSQL (https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.PostgreSQL.html) database to a number of destinations, including Amazon Kinesis Data Stream (https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Target.Kinesis.html) . Then you can use Amazon Kinesis Data Analytics for Apache Flink to enrich your data and send it to Amazon TimeStream DB.
Hope it helps.
beantwortet vor 3 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 9 Monaten
- AWS OFFICIALAktualisiert vor 2 Jahren
- Wie kann ich CloudWatch Logs kontoübergreifend an Amazon Data Firehose mithilfe von Push übertragen?AWS OFFICIALAktualisiert vor 2 Monaten
Thanks for your suggestion and really appreciated . Both the links make sense to us . Here , Team want to try to load postgre db logs into Timestream DB (through write access logs) using Lambda and then Kinesis data streams , But they donot want to use Kinesis Data Analytics for apache flink , as per my understanding Kinesis Data analytics for apache flink is required here and even you have also suggested above . and we are not sure about How Postgre database - write access logs can configured in Postgre and any mandatory postgre db version is required to enabled write access logs. As per my understanding , Kinesis data streams , kinesis fire hose , kinesis data analytics for apache flink services are ideal aws services to read real time/IoT Data (sensor, device , web logs) data through some protocol and it loads data into Time Series DB and after that we can some analytics query on time series database based on timestamp partition. this is my understanding .
this is my thought , Just reading postgre DB logs through Lambda and pushing it to Time Series Database won't be a ideal scenario for Real time Data reading / Event driven scenario. here we are creating many data hubs .
one more thought , Time Series DB data always good to capture event data as it captures Dimension and Measures of a device / sensor in one table so analytical would be easy . i think , Time Series DB table won't support Joins with another time series db table.