StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p><em>Hi - not sure if I'm covering the exact points you want answered - but it's a start; ask for clarification if you want, and I'll update my answer accordingly.</em></p> <p>In terms of <strong>data management</strong> you might want to start thinking along <a href="http://en.wikipedia.org/wiki/Master_Data_Management" rel="nofollow">Master Data Management</a> lines. The first thought that leaps to mind is that you don't want inconsistent <a href="http://en.wikipedia.org/wiki/Reference_data" rel="nofollow">Reference Data</a>; this would suggest you use a single shared instance of the data - alternatively you could have multiple copies assuming the management and custodial processes around that data is crystal clear.</p> <p>In terms of <strong>integration</strong>, reuse depends on the Non-Functional Requirements of the various systems. A single shared service makes it easy to manage the data (in that there's only a single copy to worry about) but it means that it can become a bottle-neck; further more the "weakest link in the chain" rule applies - what's the impact if the shared service goes down?</p> <p><strong>Possible Solution Options</strong></p> <p>It's hard to know what to recommened without more info, but my thoughts are: </p> <ul> <li>Keep your three apps separate.</li> <li>Use a single shared service for shared data.</li> <li>Access to the shared data can be via a "service" - this would give you the most control and options.</li> <li>The shared service might exist as a single instance - or - you might have mutliple instances of the service deployed (but only one instance of the DB).</li> </ul> <p>The key point is tht you should be able to abstract out the shared service without affecting the other apps - specifcially, you shouldn't be thinking of making an uber app.</p> <p>One more thing - thinking of there being one "service" in a business sense doesn't preclude having multiple ways of technically exposing and consuming it. </p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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