3 ms·
If anyone from the Timescale team is here, can you give a specific example of how this is different from the "DBaaS" services you reference? I get that you're g
by gneray 5y ago
If anyone from the Timescale team is here, can you give a specific example of how this is different from the "DBaaS" services you reference? I get that you're going to give transparency into what's behind the scenes, which is how it's different from serverless options. But what would be an example of how this "transparent box" is different from something like RDS or Aurora or...?
- clarkbw 5y agoFor the DBaaS services the problem is more of simplicity and developer experience; they are more of a transparent box which can make things more complicated than necessary. You should be able to have a clear paved path for an excellent general database experience with automatic backups, scale, and functionality to improve developer ergonomics. While at the same time, under the hood having this DBaaS like experience which allows you to take more control as needed. Of course it is not easy to offer both simplicity and flexibility, that's a fine line to draw but that is our goal.