Note that there are some explanatory texts on larger screens.

plurals
  1. POUnifying Database Storage
    primarykey
    data
    text
    <p>First of all, sorry for the question title - I was unable to think about something better.</p> <p>I have an interesting problem.</p> <p>There are three web applications: </p> <pre><code>1. ApplicationA =&gt; example.com -&gt; hosted in Germany 2. ApplicationB =&gt; example2.net -&gt; hosted in Australia 3. ApplicationC =&gt; anotherexample.com -&gt; hosted in United States </code></pre> <p>All of them are completely free however owner is planning to implement some paid options. The main issue is that applications are hosted on separate servers, in three different locations.</p> <p>Now, if owner wants to implement any paid options, he needs to created unified invoicing system (as invoices numbering order needs to be correct).</p> <p>So, we have situation:</p> <pre><code>1. user buys a premium option on example.com 2. another user buys a premium option on example2.net 3. third and fourth users buy extra options on anotherexample.com </code></pre> <p>So we have 4 invoices, so they numbering should be as following: 2011/01, 2011/02, 2011/03, 2001/04.</p> <p>As mentioned above, the main issue is to unify invoicing system as applications use different databases and are hosted on different servers. Of course, invoices should be stored in application-specified database.</p> <p>Theoretically we have only one issue: invoices numbers. Obviously we need to create a unified system for invoices storage. </p> <p>There might be few possible issues: </p> <blockquote> <ul> <li>there might be a lot of API requests to invoicing system </li> <li>every single invoice needs to be stored in the database </li> <li>while creating every single invoice in every external application, we need to query invoicing system for the latest invoice number.</li> </ul> </blockquote> <p>I'm really interested in your knowing your approaches and suggestions. Any activity in this case is highly appreciated.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

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