Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Your choices are fairly binary:</p> <ol> <li>Use push notification</li> <li>Use Polling</li> </ol> <p>With Push Notification:</p> <ul> <li>You control when you contact your users... Heavy Load means you can slow updates down to avoid taxing your infrastructure</li> <li>Contrariwise, you have to push to clients that may not even be there anymore (And thus may need some sort of register model), high load may mean that clients don't get immediate update </li> <li>You can leverage things like <a href="http://aws.amazon.com/ec2/" rel="nofollow noreferrer" title="Amazon&#39;s EC2">Amazon's EC2</a> to give you more processing power</li> <li>Unless you're out of capacity, users are almost certain to be receiving updates as they happen</li> <li>To pick up messages missed while offline, the SERVER needs to know what message was last successfully received, store older messages and forward many all at once</li> </ul> <p>If you choose to use polling:</p> <ul> <li>You must have a stable address to be polled</li> <li>You need the ability to have lots of quick query connections checking for new data, then returning that data if required.</li> <li>If your application becomes popular enough you may find you don't have enough resources</li> <li>If your resources are taxed your application will go down, rather then just slow down</li> <li>You don't need to register clients and keep track of their on/offline state</li> <li>Parallelizing on the fly is a bit trickier</li> <li>To pick up older messages, the CLIENT needs to know when they last received a message and then request the server send any message since that time</li> </ul> <p>Both can be fast, but they come with different bandwidth and processing profiles. I prefer push for everything that's real-time.</p>
    singulars
    1. This table or related slice is empty.
    1. POCreating a constantly updating feed like Twitter
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USDylan Lacey
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCreating a constantly updating feed like Twitter
      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. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThere's also the third possibility of keeping an open IP connection with the server.
      singulars
      1. PO
      1. USjtbandes
    2. COSounds like push may be for me. For now, I don't need to notify people when the app is closed. Updates to a feed might be about one very minute and could become more. Is push good for that? I've updated the question in regards to database.
      singulars
      1. PO
      1. US4thSpace
    3. CO@jtbandes good point. Since we're looking at that for work, you'd think I would've realized. Doh. @4thSpace - You're going to have NumberOfUsers worth of transactions a minute. Whether your servers can handle that depends on your server infrastructure, hosting, bandwidth et al. I don't foresee any issues with reasonable numbers of users. Allow open devices to register then just push to them until they stop responding to new pushes, at which point wait for them to re-register ('cause they're likely closed or incommunicado).
      singulars
      1. PO
      1. USDylan Lacey
 

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