|
|
|
|
|
|
by DavidMankin
700 days ago
|
|
|
How does this compare to DataHub? I have been comparing the two and I don't have any pros/cons that really help me pick. What I've noticed: * It seems like DataHub has an async Kafka ingestion approach while OpenMetadata is API * It seems that the data model of OpenMetadata can be extended/modified by API calls while DataHub only allows for changes to be made in code (in a forked version, no less) and deployed. * It seems that DataHub comes with more data types out-of-the-box such as JSON Schema |
|
|
We do not use Kafka by default. If someone needs kafka they can add it. However for Metadata APIs, we do not feel like Kafka is needed. Lot of projects are getting dependent on Kafka and calling it as real-time. Its unnecessary burden on users who are going to operate in production for 99% of use-cases Kafka is not needed, coming from a Kafka committer :)
2. Yes all of our APIs and Entity definitions are generated using JsonSchema. For us, Json Schema has been awesome, all of our backend / ingestion and UI is generated from JsonSchema and its easy to extend and add new models when needed
3. IMO, we have much more coverage , you can look at the types available here https://github.com/open-metadata/OpenMetadata/tree/main/open... and we are support JsonSchema as a type from a long time