On 2019-02-04 06:49, API Dev wrote:
> @MattM, @Peter Williams and @dret - any further thoughts on this? Given
> the situation we are in, do you think we could do something to ease the
> integration effort without knowing the exact use cases that clients have?
nothing further, just repeating: if you have zero ideas about users or
use cases, delay doing anything until you have first teams or at least
ideas what users and use cases look like.
from my experience, it is rather unlikely that anybody will have an
interest in gaining access to the implementation details of a data
model. if anybody does, i would still recommend to stay clear of this.
loose coupling is a vague term, but almost everybody agrees that it is a
good thing. being able to rip out and replace an implementation without
consumers having to know is one good indicator of loose coupling. i am
not quite sure what your "higher level table model" looks like, but
maybe you can test it against this constraint?
another useful thing to do might be to practice "API Archaeology" as we
describe it in our CAM book (https://twitter.com/thecambook
). while you
might not have APIs yet, you very likely have existing integrations.
looking at why they exist and what they try to do might give you a
better understanding of actual integration needs, instead of exposing
too many details.