postmortem   2131

« earlier    

RethinkDB: why we failed
"When we announced that RethinkDB is shutting down, I promised to write a post-mortem. I took some time to process the experience, and I can now write about it clearly.

In the HN discussion thread people proposed many reasons for why RethinkDB failed, from inexplicable perversity of human nature and clever machinations of MongoDB's marketing people, to failure to build an experienced go-to-market team, to lack of numeric type support beyond 64-bit float. I aggregated the comments into a list of proposed failure reasons here.

Some of these reasons have a ring of truth to them, but they're symptoms rather than causes. For example, saying that we failed to monetize is tautological. It doesn't illuminate the reasons for why we failed.

In hindsight, two things went wrong -- we picked a terrible market and optimized the product for the wrong metrics of goodness. Each mistake likely cut RethinkDB's valuation by one to two orders of magnitude. So if we got either of these right, RethinkDB would have been the size of MongoDB, and if we got both of them right, we eventually could have been the size of RedHat[1]."
postmortems  failure  failures  postmortem  databases  products  productmanagement 
6 weeks ago by earth2marsh
What Really Happened in the UK Blackouts?
9th of August 2019. It’s 4:52pm on a Friday, people are getting ready to go home and enjoy their weekend, then…
click
5% of Great Britain goes dark.
Wide spread power outages, trains stop, an airport and hospital lose power.
What happened? This timeline is based on the interim report from National Grid, published on the 16th of August. It’s a pretty good read! Would recommend. It’s also worth pointing out briefly that all media reporting I’ve seen of the UK blackout have the events...
postmortem  failure  electricity 
10 weeks ago by geetarista

« earlier    

related tags

2019-05  2019  3d  accident  airplane  analysis  animation  anime  announcement  architecture  art  article  articles  autopsy  avionics  benjamintreynorsloss  best  bestpractices  bgp  bizarre  blameless  blog  boeing  brain  brain_banking  breakdown  btreynor  c  cassandra  cgi  chemistry  cloud  cloudcomputing  cloudflare  cloudposse  co2  crash  crdts  database  databases  debugging  design  devops  digital-ocean  digitalocean  disaster  django  do  ee  electricity  embedded  engineering  erlang  etsy  example  experience  failure  failures  falling-sand-games  fcc  fintech  flow-graph  game  gamedev  games  gcp  gcs  gmail  goback  google  googlecloud  grafana  grants  ha  hardware  hazard  heroku  humanengineering  immunology  incident-handling  incident-management  incident  incidentresponse  industry  infrastructure  installation  internet  investigation  ios  k8s  kubernetes  learning-from-incidents  lighttable  making-sandspiel  matrix  meetings  mistake  nenad_sestan  network  networking  news  openbsd  operations  ops  optimization  osdev  outage  paxos  performance  perfusion  pmz  post-analysis  post-mortem  postgres  postgresql  postmortems  problem  production  productmanagement  products  profiling  programming  raft  raph.levien  raspberry-pi  rca  reactnative  recovery  redis  reference  regex  reliability  rene_kahn  resources  retros  retrospective  retrospectives  rust  sand  schizophrenia  security  short  software  sre  ssh  startup  stories  sysadmin  systems  t_cells  tdc  tech  telecom  template  toread  train  travel  tutorials  type:collection  ultrasound  usa  usb-c  vfx  visualprogramming  w-hat  warstory  webassembly  webdev  weird  xi  xmpp  youtube 

Copy this bookmark:



description:


tags: