[awr]

Looks very cool. Can see a use-case for it at Sky Ledge (IoT/operational insights platform) [1]. To date, we've been building out data ingest from devices for our customers, and for that it's easy enough for us to spin up a service (for more complex use-cases) or a Lambda (for simpler use-cases) to perform the transformation.

However, we're at a stage where we're focusing on developer experience and allowing anybody to create their own "control rooms". Ingest is a particular pain point (we don't want users having to spin up their own servers/lambdas to handle ingest).

Something like DTL where users can define their own transformation schema would be ideal. The syntax might be a bit esoteric and we'd probably want to support both uploading the transformation schema and also composing it via UI for less technical users.

[1] https://skyledge.com

[jk0ne]

That's a very similar use case to where DTL started.

We needed a way to link arbitrary APIs together without having to resort to custom code to rewrite the data between formats. DTL was born as a way to handle that translation without having to worry about untrusted code or limiting the end-user's ability to define how to remap the data. DTL can only operate on the data it is provided and can not rewrite the input data as it runs, so it is pretty safe to use in that way.

I'd love to see DTL get used in the way it was originally built for. Happy to help / talk sometime if you want.