StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Some tips I would like to give you:</p> <ul> <li><p>Don't use a RDBMS, but an in-memory(FAST) database like for example <a href="http://redis.io" rel="nofollow">redis</a>. As hopefully you agree with me from the redis <a href="http://redis.io/topics/benchmarks" rel="nofollow">benchmarks</a>, redis is pretty fast. As another sidenote I would like to point out installing redis is child's play :).</p> <p>make</p></li> </ul> <p>There is a <a href="https://github.com/owlient/phpredis" rel="nofollow">redis-client</a> for PHP which uses C so that is also going to be very fast. - If I understand you correctly you think that pubsubhubbub is the same as a message queue but they aren't:</p> <blockquote> <p>Parties (servers) speaking the PubSubHubbub protocol can get near-instant notifications (via webhook callbacks) when a topic (feed URL) they're interested in is updated.</p> </blockquote> <p>Versus message queue:</p> <blockquote> <p>In computer science, message queues and mailboxes are software-engineering components used for interprocess communication, or for inter-thread communication within the same process. They use a queue for messaging – the passing of control or of content.</p> </blockquote> <p>You might think they are the same(they have some similarities), but they aren't the same. For my message queue I would redis(redis is very powerfull because it also has a basic message queue :)). You could put message(unit of work) onto a queue using <a href="http://redis.io/commands/rpush" rel="nofollow">rpush</a>. </p> <pre><code>rpush <name of queue> <message> </code></pre> <p>Then from your worker processes you could receive messages from the queue using <a href="http://redis.io/commands/brpop" rel="nofollow">brpop</a>(blocking pop :))</p> <pre><code>brpop <name of queue> 0 </code></pre> <p>The workers process spawn are going to be started from the <a href="http://articles.sitepoint.com/article/php-command-line-1" rel="nofollow">cli</a> to stay in memory so aren't going to have overhead loading PHP in memory again and again.</p> <pre><code>php worker.php </code></pre> <p>I hope this is hopefully for you and if you might have any question I am very willing to answer them ;)</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