What is our primary use case?
In my company, we have data that needs to be stored, at least in some kind of time series database. We used to get the telemetry data from the devices in real-time, so we have to store them with Amazon Timestream whenever the data is coming in the stream in real-time.
What is most valuable?
I would say that considering the version that the tool provides, we don't have to do any kind of merge operation or any other update. If some different value comes, like if you want a data value, we can keep the key dimension value the same. It will update the rest of the values, measurement values, and all, so this is why we don't have to do anything extra to merge the tool and all the updates.
What needs improvement?
There are disadvantages when it comes to time series databases since you can't delete anything from Amazon Timestream data. You can just have the retention profiles on it, after which it will delete itself, but you can't forcefully delete it, making it an area where improvements are required.
For how long have I used the solution?
I have been using Amazon Timestream for six months. My company has a partnership with Amazon.
What do I think about the scalability of the solution?
It is an easily scalable solution. When it comes to the retention period, if someone wants to change, they have to define it at the start. Later on, if users want to change it again, like, or increase the retention policy, then they have to create the table again and do so, and if it is not done, then we face problems. It will increase the retention, but when you try to insert a record or an older record that is not included in the range of your retention period, then you can face some problems and, like, it will throw some errors. The tool is scalable, but it should be defined at the start as to how much retention you want.
For scalability, I rate the tool a six or seven out of ten.
How are customer service and support?
If you drop a message, the solution's technical support will definitely reply. My company only uses support for some use cases, but not most of the time.
How was the initial setup?
When it comes to the product's deployment phase, everything is managed by AWS, so it is a managed service. If someone doesn't know about the time series database, they might face some difficulties or some challenges. If a person keeps on working on the tool, then such a person will find out how the product works and can work on it.
What other advice do I have?
The tool is not really easy to use. If someone wants to use the tool, they can research and use it, and it won't take much long.
I don't think my company maintains the tool.
I can recommend the tool to others based on their use cases. If someone has a use case where they have some kind of Amazon Timestream data coming in, they can definitely use it, but they have to be cautious about some update and deletion parts. People need to think before using the tool.
I rate the tool an eight and a half out of ten.
