This can be a visitor put up by Jake J. Dalli, Information Platform Group Lead at Tipico, in partnership with AWS.
Tipico is the primary title in sports activities betting in Germany. On daily basis, we join thousands and thousands of followers to the fun of sport, combining know-how, ardour, and belief to ship quick, safe, and thrilling betting, each on-line and in additional than a thousand retail retailers throughout Germany. We additionally deliver this expertise to Austria, the place we proudly function a powerful sports activities betting enterprise.
On this put up, we present how Tipico constructed a unified knowledge transformation platform utilizing Amazon Managed Workflows for Apache Airflow (Amazon MWAA) and AWS Batch.
Resolution overview
To help crucial wants akin to product monitoring, buyer insights, and income assurance, our central knowledge operate wanted to supply the instruments for a number of cross-functional analytics and knowledge science groups to run scalable batch workloads on the prevailing knowledge warehouse, powered by Amazon Redshift. The workloads of Tipico’s knowledge neighborhood included extract, rework, and cargo (ELT), statistical modeling, machine studying (ML) coaching, and reporting throughout various frameworks and languages.
Previously, analytics groups operated in isolation, distinct from one another and the central knowledge operate. Completely different groups maintained their very own set of instruments, typically performing the identical operate and creating knowledge silos. Lack of visibility meant a scarcity of standardization. This siloed method slowed down the supply of insights and prevented the corporate from reaching a unified knowledge technique that ensured availability and scalability.
The necessity to introduce a single, unified platform that promoted visibility and collaboration turned clear. Nevertheless, the variety of workloads introduced one other layer of complexity. Groups wanted to sort out several types of issues and introduced distinct skillsets and preferences in tooling. Analysts may rely closely on SQL and enterprise intelligence (BI) platforms, whereas knowledge scientists most well-liked Python or R, and engineers leaned on containerized workflows or orchestration frameworks.
Our purpose was to architect a brand new system that helps variety whereas sustaining operational management, delivering an open orchestration platform with built-in safety isolation, scheduling, retry mechanisms, fine-grained role-based entry management (RBAC), and governance options akin to two-person approval for manufacturing workflows. We achieved this by designing a system with the next rules:
- Convey Your Personal Container (BYOC) – Groups are given the pliability to package deal their workloads as containers and are free to decide on dependencies, libraries, or runtime environments. For groups with extremely specialised workloads, this meant that they may work in a setup tailor-made to their wants whereas additionally working inside a harmonized platform. Alternatively, groups that didn’t require absolutely personalized environments might redesign their workloads to align with current workloads.
- Centralized orchestration for full transparency – All groups can see all workflows and construct interdependencies between them
- Shared orchestration, remoted compute – Workloads run in team-specific Docker containers inside a unified compute setting, offering scalability whereas retaining execution traceable to every workforce.
- Standardized interfaces, versatile execution – Widespread patterns (operators, hooks, logging, or monitoring) scale back complexity, and groups retain freedom to innovate inside their containers.
- Cross-team approvals for crucial workflows saved inside model management – Modifications observe a four-eye precept, requiring evaluation and approval from one other workforce earlier than execution, offering accountability and lowering threat. This allowed our core knowledge operate to observe and contribute strategies to work throughout completely different analytics groups.
We devised a system whereby orchestration and execution of duties function on shared infrastructure, which groups work together with by way of domain-specific infrastructure. In Tipico’s case, every workforce pushes photos to team-owned container situations. Such containers present code for workflows, together with execution of ELT pipelines or transformations on high of domain-specific knowledge lakes.
The next diagram exhibits the answer structure.
The technical problem was to architect a versatile and high-performance orchestration layer that might scale reliably whereas additionally remaining framework-agnostic, integrating seamlessly with current infrastructure.
When designing our system, we had been conscious of the a number of container orchestration options provided by Amazon Net Companies (AWS), together with Amazon Elastic Kubernetes Service (Amazon EKS), Amazon Elastic Container Service (Amazon ECS), and AWS Batch, amongst others. Ultimately, the workforce chosen AWS Batch as a result of it abstracts away cluster administration, gives elastic scaling, and inherently helps batch workloads as a design function.
Resolution particulars
Earlier than adopting the present answer, Tipico experimented with working a self-managed Apache Airflow setup. Though it was purposeful, it turned more and more burdensome to keep up. The shift towards a managed and scalable answer was pushed by the necessity to focus extra on empowering groups to ship moderately than sustaining the infrastructure. Tipico replatformed the central orchestration answer utilizing Amazon MWAA and AWS Batch.
Amazon MWAA is a totally managed service that simplifies working open supply Apache Airflow on AWS. Customers can construct and execute knowledge processing workflows whereas integrating seamlessly with numerous AWS providers, which implies builders and knowledge engineers can focus on constructing workflows moderately than managing infrastructure.
AWS Batch is a totally managed service that simplifies batch computing within the cloud so customers can run batch jobs without having to provision, handle, or keep clusters. It automates useful resource provisioning and workload distribution, with customers solely paying for the underlying AWS assets consumed.
The brand new design gives a unified framework the place analytics workloads are containerized, orchestrated, and executed on scalable compute and built-in with persistent storage:
- Containerization – Analytics workloads are packaged into Docker containers, with dependencies bundled to supply reproducibility. These photos are versioned and saved in Amazon Elastic Container Registry (Amazon ECR). This method decouples execution from infrastructure and allows constant habits throughout environments.
- Workflow orchestration – Airflow Directed Acyclic Graphs (DAGs) are version-controlled in Git and deployed to Amazon MWAA utilizing a steady integration and steady supply (CI/CD) pipeline. Amazon MWAA schedules and orchestrates duties, triggering AWS Batch jobs utilizing customized operators. Logs and metrics are streamed to Amazon CloudWatch, enabling real-time observability and alerting.
- Information persistence – Workflows work together with Amazon Easy Storage Service (Amazon S3) for sturdy storage of inputs, outputs, and intermediate artifacts. Amazon Elastic File System (Amazon EFS) is mounted to Amazon MWAA for quick entry to shared code and configuration recordsdata, synchronized repeatedly from the Git repository.
- Scalable compute – Amazon MWAA triggers AWS Batch jobs utilizing standardized job definitions. These jobs run in elastic compute environments akin to Amazon Elastic Compute Cloud (Amazon EC2) or AWS Fargate, with secrets and techniques securely injected utilizing AWS Secrets and techniques Supervisor. AWS Batch environments auto scale based mostly on workload demand, optimizing price and efficiency.
- Safety and governance – AWS Identification and Entry Administration (IAM) roles are scoped per workforce and workload, offering least-privilege entry. Job executions are logged and auditable, with fine-grained entry management enforced throughout Amazon S3, Amazon ECR, and AWS Batch.
Widespread operators
To streamline the execution of batch jobs throughout groups, we developed a shared operator that wraps the built-in Airflow AWS Batch operator. This abstraction simplifies the execution of containerized workloads by encapsulating frequent logic akin to:
- Job definition choice
- Job queue concentrating on
- Setting variable injection
- Secrets and techniques decision
- Retry insurance policies and logging configuration
Parameterization is dealt with utilizing Airflow Variables and XComs, enabling dynamic habits throughout DAG runs. The operator is maintained in a shared Git repository, versioned and centrally ruled, however accessible to all groups.
To additional speed up growth, some groups use a DAG Manufacturing unit sample, which programmatically generates DAGs from configuration recordsdata. This reduces boilerplate and enforces consistency so groups can outline new workflows declaratively.
By standardizing this operator and supporting patterns, Tipico reduces onboarding friction, promotes reuse, and gives constant observability and error dealing with throughout the analytics ecosystem.
Governance
Governance is enforced by way of a mix of fine-grained IAM roles, AWS IAM Identification Heart and automatic function mapping. Every workforce is assigned a devoted IAM function, which governs entry to AWS providers akin to Amazon S3, Amazon ECR, AWS Batch and Secrets and techniques Supervisor. These roles are tightly scoped to attenuate the extent of harm and supply traceability.
On condition that the airflow setting runs model 2.9.2, which doesn’t help multi-tenant entry, Tipico developed a customized part that dynamically maps AWS IAM roles to Airflow roles. The part, which executes periodically utilizing Airflow itself, dynamically syncs IAM function assignments with Airflow’s inside RBAC mannequin. Airflow tags are used to manipulate entry to completely different DAGs, governing which groups have entry to execute or modify the settings on the DAG. This aligns entry permissions stay with organizational construction and workforce duties.
Adoption
The shift towards a managed, scalable answer was pushed by the necessity for better workforce autonomy, standardization, and scalability. The journey started with a single analytics workforce validating the brand new method. When it was profitable, the platform workforce generalized the answer and rolled it out incrementally to different groups, refining it with every iteration.One of many greatest challenges was migrating legacy code, which regularly included outdated logic and undocumented dependencies. To help adoption, Tipico launched a structured onboarding course of with hands-on coaching, actual use circumstances, and inside champions. In some circumstances, groups additionally needed to undertake Git for the primary time—marking a broader shift towards trendy engineering practices inside the analytics group.
Key advantages
Some of the useful outcomes of our new structure that’s primarily constructed round Amazon MWAA and AWS Batch is to speed up analytics groups’ time to worth. Analysts can now give attention to constructing transformation logic and workloads with out worrying in regards to the underlying infrastructure. With this method, analysts can depend on preprepared integrations and analytics patterns used throughout completely different groups, supported by commonplace interfaces developed by the core knowledge workforce.
Other than constructing analytics on Amazon Redshift, the orchestration answer additionally interfaces with a number of different analytics providers akin to Amazon Athena and AWS Glue ETL, offering most flexibility on the kind of workloads being delivered. Groups inside the group have additionally shared practices in utilizing completely different frameworks, akin to dbt Labs, to reuse customized developments to hold out commonplace processes.
One other useful final result is the flexibility to obviously segregate prices throughout groups. Throughout the structure, Airflow delegates heavy lifting to AWS Batch, offering process isolation that spans past Airflow’s built-in staff. By means of this, we achieve granular visibility into useful resource utilization and correct price attribution, selling monetary accountability throughout the group.
Lastly, the platform additionally gives embedded governance and safety, with RBAC and standardized secrets and techniques administration offering an operationalized mannequin for securing and governing working flows throughout completely different groups.
Groups can now give attention to constructing and iterating rapidly, understanding that the encompassing constructions present full transparency and are coherent with the group’s governance, structure, and FinOps objectives. On the identical time, centralized orchestration fosters a collaborative setting the place groups can uncover, reuse, and construct upon one another’s workflows, driving innovation and lowering duplication throughout the information panorama.
Conclusion
By reimagining our orchestration layer with Amazon MWAA and AWS Batch, Tipico has unlocked a brand new stage of agility and transparency throughout its knowledge workflows.
Beforehand, analytics groups confronted lengthy lead instances, typically stretching into weeks, to implement new reporting use circumstances. A lot of this time was spent figuring out datasets, aligning transformation logic, discovering integration choices, and navigating inconsistent high quality assurance processes. In the present day, that has modified. Analysts can now develop and deploy a use case inside a single enterprise day, shifting their focus from groundwork to motion.
The fashionable structure empowers groups to maneuver quicker and extra independently inside a safe, ruled, and scalable framework. The result’s a collaborative knowledge ecosystem the place experimentation is inspired, operational overhead is decreased, and insights are delivered at pace.
To start out constructing your individual orchestrated knowledge platform, discover the Get began with Amazon Managed Workflows for Apache Airflow and AWS Batch Consumer Information. These providers might help you obtain comparable ends in democratizing knowledge transformations throughout your group. For hands-on expertise with these options, attempt our Amazon MWAA for Analytics Workshop or contact your AWS account workforce to be taught extra.
Concerning the authors