You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 22, 2022. It is now read-only.
Amazon Timestream is a fast, scalable, fully managed, purpose-built time series database that makes it easy to store and analyze trillions of time series data points per day.
Timestream’s purpose-built query engine lets you access and analyze recent and historical data together. Amazon Timestream has built-in time series analytics functions, helping you identify trends and patterns in your data in near real-time. Timestream is also Serverless.
It would be nice if all DomainEvents were automatically pushed to Timestream. This would allow developers to quickly provide time series Read Models using window functions with Timestream queries.
Without Timestream these sorts of read models might be challenging for some developers to create.
I also believe it should be a design goal of ours to avoid Lambda when possible and instead leverage services.
The text was updated successfully, but these errors were encountered:
Amazon Timestream is a fast, scalable, fully managed, purpose-built time series database that makes it easy to store and analyze trillions of time series data points per day.
Timestream’s purpose-built query engine lets you access and analyze recent and historical data together. Amazon Timestream has built-in time series analytics functions, helping you identify trends and patterns in your data in near real-time. Timestream is also Serverless.
It would be nice if all DomainEvents were automatically pushed to Timestream. This would allow developers to quickly provide time series Read Models using window functions with Timestream queries.
Without Timestream these sorts of read models might be challenging for some developers to create.
I also believe it should be a design goal of ours to avoid Lambda when possible and instead leverage services.
The text was updated successfully, but these errors were encountered: