-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Domain model / data schema in Scala, Protobuf and Avro #91
Comments
Hey @SemanticBeeng , glad to see you're interested in Skeuomorph! Everything you've mentioned right there is possible to do right now using Skeuomorph, however, maybe you're more interested in https://github.com/higherkindness/compendium. Compendium is, more or less, what the post you've mentioned above calls a schema registry. Right now is in a very early stage, but we're planning to make it a nice utility providing the following:
Right now, I repeat, is in an early stage, but we welcome new contributors, and beta testers too once it's usable. |
For that it relies fully on Or will there be some reusable morphisms in here? |
Side question : What is the reason? I stand corrected, just found https://github.com/higherkindness/skeuomorph/blob/master/src/test/scala/higherkindness/skeuomorph/openapi/OpenApiSchemaSpec.scala. |
Related topics:
Would be great to have an unifying way to manage
Then it would be good to have support for reshaping between Currently there are:
Wondering if these morphisms can also be specified at the schema level? |
Looking to develop a combination of
gRPC
services withmu-RPC
and REST endpoints which share a common domain model.Would like to reduce boiler plate of maintaining multiple versions of the model and wondering if
skeumorph
can help. This provides more context for the motivation https://medium.com/@sugarpirate/exploring-the-strongly-typed-graph-31fc27512326.Do you see a problem in principle with attempting this?
Is
skeumorph
mature enough to make possible1, maintaining the truth model in
protobuf
2. generating Scala domain classes and
@message
classes (through a few custom morphisms)3. generating Avro version of same model from 1.
Or some combination of the above.
The text was updated successfully, but these errors were encountered: