Re: DDD and cross domain AR references for UI

Thanks Thomas.


The Ticket BC has no behaviour relating to whether the TicketHolder is a
User or a Company.


My worry (or DDD misunderstanding) is that when the front end fetches the
Ticket, e.g. `GET /tickets/:id` the TicketHolder will be just an ID and
therefore it will not know the next resource to fetch, i.e. `GET
/companies/:id` or `GET /users/:id`. The TicketHolder can definitely be
represented by a referential ID but that will mean (a) that the front end
will need to call some sort of Social BC object discovery endpoint and (b)
it will not be able to supply the end user with any affordance relating to
whether the TicketHolder is a Company or a Profile prior to aforementioned
discovery.


Perhaps part of my issue is that a single front end is spanning BC's? This
is may be a modelling mistake, but it is very beneficial for maintenance
and agility.






On 28 July 2015 at 07:02, Thomas Presthus [email protected]
[domaindrivendesign] <[email protected]> wrote:


>
>
> Does the Ticket BC need to know whether the TicketHolder is a User or
> Company?
>
> If not, could the TicketHolder in Ticket BC simply be a referential id
> to the entity in your social BC, and the social BC render the appropiate
> profile knowing which type of holder it is?
>
> --
>
> Thomas Presthus
>
>  
>