5id

One of the biggest benefits imo of using Postgres as your application queue, is that any async work you schedule benefits from transactionality.

That is, say you have a relatively complex backend mutation that needs to schedule some async work (eg sending an email after signup). With a Postgres queue, if you insert the job to send the email and then in a later part of the transaction, something fails and the transaction rollbacks, the email is never queued to be sent.

According to @dang (https://news.ycombinator.com/item?id=28479595) via @sctb (https://news.ycombinator.com/item?id=16076041)

  We’re recently running two machines (master and standby) at M5 Hosting. All of HN runs on a single box, nothing exotic:
  CPU: Intel(R) Xeon(R) CPU E5-2637 v4 @ 3.50GHz (3500.07-MHz K8-class CPU)
  FreeBSD/SMP: 2 package(s) x 4 core(s) x 2 hardware threads
  Mirrored SSDs for data, mirrored magnetic for logs (UFS)

It's sad to think that with these laws being passed, regardless of what position you take, that we still don't have any Fair Use provisions in Australia. There was even a discussion paper [http://www.alrc.gov.au/publications/4-case-fair-use-australi...] put forward by our Law Reform Commission suggesting this. I would have though the productivity benefits associated with education and innovation alone would make this a no brainer

Go to cloud.digitalocean.com/support and create a new ticket, giving them your promo code and asking nicely, and they'll put it through promptly in my experience