Feedback
Liking it so far.
It would be nice if it was possible to configure custom domains for pipelines. Yeah, I know workers can do this, but with one use case, I am potentially throwing billions of events at it a week and the compute cost on the workers would be 99% of the cost of it.
Still, pretty neat stuff.
It would also be nice to be able to potentially use Wrangler json/file files to manage deployments so that I can keep all the configs in a version controlled repo.
Easy enough to handle with shell scripts for now, but these little niceties would make deployment a heck of a lot easier.
Terraform deployment would be cool too, but I'm happy to have some baby steps on the first few items.
My use cases: Basically want to replace an expensive pipeline like FiveTran, Snowplow or Segment.
3 Replies
Love this feedback. When you say custom domains, are you talking about the ingest endpoint? Or something else?
Totally agree with the CI/CD feedback as well. We’ll need a story for that before GA. Especially for things like schema evolution as well
Oh and terraform is coming
If you’d ever feel like hopping in a call with myself and someone from the Eng team to discuss more (even around pricing because we’re working on that as we speak and we want to be fairly competitive here) we’re always happy and ready
Yes, I mean the ingestion endpoints.
Would be nice to be something like events.your-domain.com
Not just for the vanity URL of having it on our own domain (which has benefits in terms of tracking performance), but having static endpoints for any libraries that may be sending data to a stream.
And this kinda is a good example of schema evolution. Once I have set something up and running I may want to change it and if this means generating a new stream, which generates a new URL, and then I have this messy process of having to have my developers change the endpoints. Which wouldn't even take effect on mobile apps until the app is updated.
Perfect thank you for that