Forum Discussion
Options for High‑Frequency, Low‑Latency API Ingestion
The above approaches did not work since my API requires dynamic paramters like start date and end dates which can not be handled in other ways as we dont have control of API.
If I use Eventhouse, how to get the data back in my medallion data layers?
I checked the Fabric ideas and found an idea from last year about HTTP endpoint ingestion. I added your usecase.
Please upvote this idea so your case can be added when enough users upvote this idea.
Regarding Eventhouse usage, first an Eventhouse has its own way of doing data transformation in a medallion architecture via table update policies and materialized views.
Then Eventhouse data can end up into a Lakehouse or Warehouse via the Eventhouse endpoint method.
This is a nice solution for merging two worlds, real-time data and static (slow moving, batched) data.
---
If this answer helps you, a thumbs-up or marking it as accepted answer is appreaciated. All community members with similar questions will benefit by doing so. Your contribution is highly appreciated.
