- Notifications
You must be signed in to change notification settings - Fork41
Dagger is an easy-to-use, configuration over code, cloud-native framework built on top of Apache Flink for stateful processing of real-time streaming data.
License
raystack/dagger
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
Dagger or Data Aggregator is an easy-to-use, configuration over code, cloud-native framework built on top of Apache Flinkfor stateful processing of data. With Dagger, you don't need to write custom applications or complicated code to processdata as a stream. Instead, you can write SQL queries and UDFs to do the processing and analysis on streaming data.
Discover why to use Dagger
- Processing: Dagger can transform, aggregate, join and enrich streaming data, both real-time and historical.
- Scale: Dagger scales in an instant, both vertically and horizontally for high performance streaming sink and zero data drops.
- Extensibility: Add your own sink to dagger with a clearly defined interface or choose from already provided ones. Use Kafka and/or Parquet Files as stream sources.
- Flexibility: Add custom business logic in form of plugins (UDFs, Transformers, Preprocessors and Post Processors) independent of the core logic.
- Metrics: Always know what’s going on with your deployment with built-inmonitoring of throughput, response times, errors and more.
- Map reduce ->SQL
- Enrichment ->Post Processors
- Aggregation ->SQL,UDFs
- Masking ->Hash Transformer
- Deduplication ->Deduplication Transformer
- Realtime long window processing ->Longbow
To know more, follow the detaileddocumentation.
Explore the following resources to get started with Dagger:
- Guides provides guidance oncreating Dagger with different sinks.
- Concepts describes all important Dagger concepts.
- Advance contains details regarding advance features of Dagger.
- Reference contains details about configurations, metrics and other aspects of Dagger.
- Contribute contains resources for anyone who wants to contribute to Dagger.
- Usecase describes examples use cases which can be solved via Dagger.
- Examples contains tutorials to try out some of Dagger's features with real-world usecases
Please follow thisDagger Quickstart Guide for setting up a local running Dagger consuming from Kafka or to set up a Docker Compose for Dagger.
Note: Sample configuration for running a basic dagger can be foundhere. For detailed configurations, referhere.
Find more detailed steps on local setuphere.
Referhere for details regarding Dagger deployment.
# Running unit tests$ ./gradlew cleantest# Run code quality checks$ ./gradlew checkstyleMain checkstyleTest# Cleaning the build$ ./gradlew clean
Development of Dagger happens in the open on GitHub, and we are grateful to the community for contributing bug fixes and improvements. Read below to learn how you can take part in improving Dagger.
Read ourcontributing guide to learn about our development process, how to propose bug fixes and improvements, and how to build and test your changes to Dagger.
To help you get your feet wet and get you familiar with our contribution process, we have a list ofgood first issues that contain bugs which have a relatively limited scope. This is a great place to get started.
This project exists thanks to all thecontributors.
Dagger isApache 2.0 licensed.
About
Dagger is an easy-to-use, configuration over code, cloud-native framework built on top of Apache Flink for stateful processing of real-time streaming data.