Github user kaspersorensen commented on the issue:
https://github.com/apache/metamodel/pull/120
The way I see it is that Docker apps or microservices should try to do just
a few things, and do them great. But the question is "what is the thing" then,
because I think your interpretation is a bit different than mine there. In my
opinion the "thing it does" is present a unified/federated view of your
databases. The individual databases will exist elsewhere (maybe as other docker
apps, but that's besides the point) but the thing that MM brings to the table
is a way to discover them all and use them via a single interface that applies
to them all. A common denominator (with all the bad stuff that that means), and
a unification layer too. If that is the "thing it does" then it is really still
a microservice approach to the webapp to have the collection since if it didn't
have a collection there would only be a common denominator of one, and that
wouldn't improve anything really?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
