Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There are numerous issues with the design that I think are a bit naive. </p> <p>For example in the Backing Services section they state that you should be able to swap out datastores without regard for code changes.</p> <p>The problem is that in order to leverage the performance and capability benefits of any particular data store you will naturally gravitate towards utilizing the specific features of the store you've started with. </p> <p>Further, not every datastore supports a common set of commands such that you could easily move from one to another. Their particular example of using MySql or CouchDB is, well, interesting because those two DB systems are <em>conceptually</em> very different: one is more of a traditional RDBMS, the other is document based. You can't just take your table structure and apply it directly to a CouchDB and expect to throw SQL commands at it.</p> <p>Which means that you have to put a front end in place to essentially wrap each particular datastore with a set of commands exposed as a web service... Which, imho, makes development much more difficult for very little (if any) benefit.</p> <p>Now, if they are limiting it down to exchanging a like server (local mysql) to a remote one (Amazon RDS) then the requirement that the datastore resources be accessed via a url is immaterial. Further the requirement that no code changes occur for that move is unnecessary as you shouldn't have to change code just to support having your exact DB running on a different server.</p> <hr> <p>The above is just the first area I honestly looked at. As John Saunders said, the config one also shows a complete lack of understanding of tech like .Net. Quite frankly the whole thing looks like it was written by someone who has been in the Ruby world for awhile, and hasn't looked at what else is out there.</p>
    singulars
    1. This table or related slice is empty.
    1. POIs there an example of a twelve-factor app with tweaks specifically for a .NET/TFS environment?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USNotMe
    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. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks, Chris this is valuable criticism. Based on the answers so far from yourself, Matt and John I would suggest that the 12-factor methodology is great for "decoupled" environments with a mix of interchangeable technologies (PHP, Ruby, MySQL etc) but not for a strongly connected stack like the MS stack where each tier has benefits that can be realised by sticking to environment specific best practices.
      singulars
      1. PO
      1. USAdrian Hope-Bailie
    2. COChris, the example used in the Backing Services section says one should be able to swap out a malfunctioning data-store with a new instance restored from a backup. To me, this implies that it would be the same flavor of data store, as your penultimate point addresses.
      singulars
      1. PO
      1. USRyan Long
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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