Dagster / Dagster Hot Takes

Getting an on-call page is the worst. Unfortunately most task-based orchestrators page teams frequently, whenever jobs fail. With Dagster you can reduce this alert fatigue by using retry strategies and only getting notified when SLAs are violated.

Resources:
- *Star Us*: https://github.com/dagster-io/dagster
- *Example*: https://github.com/dagster-io/hooli-data-eng-pipelines

Logging is great, but it isn't the only tool. With dagster, data engineers can also tap into debuggers, unit tests, and local development best practices.

Prefer to read: https://gist.github.com/slopp/7c64973c70b12ffbd506d4e64d80d65e

Resources posted below, or star us on GitHub to get started.

- Star Us: https://gitub.com/dagster-io/dagster
- Example Project: https://gist.github.com/slopp/359ba324a4d6ccfb3bf23d0e9554c080

No more dependency hell or Orchestrators for your orchestrator

Prefer to read: https://gist.github.com/slopp/7c64973c70b12ffbd506d4e64d80d65e

Resources posted below, or star us on GitHub to get started.

- Star Us: https://gitub.com/dagster-io/dagster
- Example Project: https://github.com/slopp/dagteam

IStop guesstimating when your Notebooks should run

Prefer to read: https://gist.github.com/slopp/7c64973c70b12ffbd506d4e64d80d65e

Resources posted below, or star us on GitHub to get started.

- Star Us: https://gitub.com/dagster-io/dagster
- Full Example Project: https://github.com/dagster-io/hooli-data-eng-pipelines