How we are trying to reduce the pains of building a data application using Dozer
1 comments
How do you plan to monetize Dozer? Will it become a platform where the company will seek to increase lock-in and revenue extraction from customers? The open source model with support contracts? Something else?
The overall idea sounds awesome. As a data engineer I’m interested.
The overall idea sounds awesome. As a data engineer I’m interested.
I'm Matteo, one of the co-founder of Dozer. I have posted here before about our project, but we were very early and only had just a bit more of a prototype. The project has evolved quite a lot and I'm quite happy with the experience we are building.
Fundamentally, with Dozer it's now possible to define all connections to your databases, data warehouses or object stores, provide some SQL transformations (WASM and TypeScript coming soon) and declare how data should be exposed as APIs. We take care of pretty much anything in the middle: sourcing the data, transforming in real time (we have built our own streaming SQL engine) and exposing it as REST and gRPC APIs.
We have built a full UI experience that allow a user to inspect the transformations and the data in real-time. Our vision is for Dozer to become a full data-application backend. Imagine you have multiple sources of data and you need to stitch them together to create a webapp. Connecting to the data sources, moving the data, keeping it fresh, cache in an a low latency store is a lot of work. That is what we want to solve with Dozer.
I'm sharing a short video of our latest release (https://www.youtube.com/watch?v=jS-Rdqn1NYw) and I'd be really interested to know your thoughts and how you would use it.
Thanks Matteo