Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It really is relative to what you mean workflow.</p> <p>Hypermedia as the engine of application state will give you a directed graph of states/resources. It is not necessary that these graphs form a workflow (e.g have a specific start and end point). They may well form a cycle, have bidirectional links and whatnot. I assume this graph is somehow derrived from the business logic.</p> <p>If you include your workflow (a specific path from one point to another via the graph) in you UI, you make some assumptions about the REST API therefore tightly coupling your UI with the business logic, therefore throwing the discoverability of REST away.</p> <p>In general mixing workflows (imperative programming) with REST (declarative programming) is very problematic. The best approach would be to have an adaptive UI that can allow the user to navigate the network of states instead of constraining them through bespoke, predetermined workflows. That is how a browser works, anyways.</p> <p>If you really need to have some workflows though, you could implement them by creating a chain of interconnected resources and guiding the user to the first one. In this sense, your first option would be valid although I find the seperation of business logic and workflow to be a grey area. Workflows <i>are</i> part of the business logic or, to state it better, are derrived <i>from</i> the business logic.</p> <p>These opinions are my own, however a good, relevant article on the topic can be found here: <a href="http://www.infoq.com/articles/webber-rest-workflow" rel="nofollow noreferrer">http://www.infoq.com/articles/webber-rest-workflow</a></p>
    singulars
    1. This table or related slice is empty.
    1. POIn which layer are you putting your REST api?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USAlexandros Marinos
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIn which layer are you putting your REST api?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI agree that the separation of business logic and workflow is a bit fuzzy. I needed to make the distinction to ensure that readers did not think I was inferring that the second scenario was directly exposing the database.
      singulars
      1. PO
      1. USDarrel Miller
    2. COI tend to view the term Workflow from the Microsoft Workflow Foundation perspective which includes state machines as well as sequential workflows and therefore in my mind HATEOAS maps quite well to the notion of workflow.
      singulars
      1. PO
      1. USDarrel Miller
 

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