Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>First consider this is a good place to apply bounded context: <a href="http://dddcommunity.org/discussion/messageboardarchive/BoundedContext.html" rel="nofollow noreferrer">http://dddcommunity.org/discussion/messageboardarchive/BoundedContext.html</a>. Ideally you shouldn't be integrating different (sub)systems through the database. This should be happening at the api level. You might already have it structured like that, assuming:</p> <ul> <li>The "table" all the sites are populating isn't a single shared information for all the sites. What it is really about is each site saving whatever info it needs about the process it is about to start, and getting an ID that will hand to the payment system. </li> <li>The payment system shouldn't force unique Ids across different web sites. It can force that each web site sends an unique id in their own context.</li> <li>If the payment system needs extra information, it should also require it at the API level, instead of forcing a db relation between all the sites and the payment system.</li> </ul> <p>You can have the sites call an API on the payment site to start the payment process and then redirect to the site. You can use either an ID controlled by each web site, or a common ID that the payment site returns after the initial payment call.</p> <p>With that in mind, the repositories would be use internally and independent by the sites and the payment service to persist information. This doesn't necessarily means it has to be a DB, as you can persist information to other places/mechanisms.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload