Skip to main content

Developer vs. production mode

Please refer to the architecture page for a detailed description of the superduperdb architecture.

There are several important services in a superduperdb setup which may be run in-process, or in their own micro-services and containers:

  • jupyter notebook/ client
  • change-data-capture (CDC) service
  • compute
    • scheduler
    • workers
  • vector-searcher service

Development mode

With the default settings of superduperdb, all of these items run in a single process. This is great for:

  • Debugging
  • Prototyping
  • Experimentation
  • Exploration
  • Querying superduperdb


There are several gradations of a more productionized deployment. In the most distributed case we have:

In the remainder of this section we describe the use of each of these services