Design Tutorials

Copy Markdown View Source

Long-form design essays. Bodies live on GitHub; this index is on HexDocs.

For how-to docs, start with Quick Start.

  1. Why put consumer groups in front of a database?
  2. What is a consumer group?
  3. Why ACK is harder than it looks
  4. Building Rheo as an Elixir/OTP library
  5. Demand, backpressure, and database consumers
  6. MongoDB as a searchable event log
  7. Killing consumers on purpose
  8. Searching the stream
  9. Why Rheo 0.2 broke its 0.1 API
  10. If Rheo really is database-agnostic, prove it with ETS
  11. Search and replay the event history
  12. ACKs are not a cursor — partitions, frontier, lag
  13. One consumer API, PostgreSQL and SQLite underneath
  14. Rheo is not Broadway — it feeds Broadway
  15. Breaking Rheo before anyone depends on the wrong abstraction
  16. Rheo on Redis Streams: portable sequence, native PEL
  17. Freezing Rheo before 1.0

Hands-on: Livebook demos (source index).

Upgrading: Upgrading index.