SC

Strategy Canon

RethinkDB: sourced choices

22 product and go-to-market choices, oldest first. Back to the case study

  1. 2015-04-14Product · Production readiness RethinkDB designated version 2.0 production ready. RE2
  2. 2015-04-14Product · Realtime data The database supported changefeeds for realtime updates. RE2
  3. 2015-11-12Product · Changefeed consistency Version 2.2 added atomic changefeeds combining initial results with subsequent updates. RE7
  4. 2015-11-12Product · Query execution Version 2.2 introduced parallel scans. RE7
  5. 2015-11-12Product · Index operations Version 2.2 improved background index construction. RE7
  6. 2016-05-17Product · Application backend Horizon packaged an open-source backend around RethinkDB. RE3
  7. 2016-05-17Product · Client interface Horizon provided a JavaScript client with a fluent API and RxJS integration. RE3
  8. 2016-05-17Product · Common app functions Horizon supplied authentication, sessions and data operations. RE3
  9. 2016-05-17Product · Deployment flexibility Horizon could run locally, on a VPS, in a cloud or on bare metal. RE3
  10. 2016-05-17Product · Developer setup Horizon supplied command-line scaffolding through npm. RE3
  11. 2016-05-17Product · Extensibility Developers could embed Horizon in a custom Node application. RE3
  12. 2016-05-17Product · Managed product state Horizon Cloud was in private beta, rather than generally available. RE3
  13. 2016-05-17Go_To_Market · Buyer focus Horizon addressed JavaScript developers building realtime applications. RE3
  14. 2016-05-17Go_To_Market · Open distribution Developers could obtain and run Horizon as open-source software. RE3
  15. 2016-05-17Go_To_Market · Cloud access The company offered sign-up for Horizon Cloud’s private beta. RE3
  16. 2017-01-19Go_To_Market · Initial audience The founder described developers adopting the open-source database as the entry point to the business. RE1
  17. 2017-01-19Go_To_Market · Initial pitch The founder recalled emphasizing correctness and technical elegance in the early pitch. RE1
  18. 2017-01-19Go_To_Market · Positioning change The founder dated a move toward realtime application use cases to mid-2014. RE1
  19. 2017-01-19Go_To_Market · Commercial capability The founder said the original team lacked go-to-market experience. RE1
  20. 2017-01-19Go_To_Market · Hosted option declined The team considered basic managed hosting and rejected it as too small a revenue opportunity. RE1
  21. 2017-01-19Go_To_Market · Database-service option declined The founder described declining a conventional database-as-a-service approach because of incumbent competition and customer trust requirements. RE1
  22. 2017-01-19Go_To_Market · Paid-service direction The team instead chose a higher-level cloud application platform as its intended commercial route. RE1