Skip to content

Teams

Welcome to the Tamedia Core Engineering teams overview. This page provides information about each product team using the Fission platform.

Overview

All teams leverage dai for shared infrastructure while maintaining their own AWS accounts for product-specific resources.

Team Members Services AWS Account Kubernetes Namespace
Disco 12 8 disco-prod disco
Unity 15 12 unity-prod unity
Discovery 10 6 discovery-prod discovery
Jazz 8 5 jazz-prod jazz
dai 6 15 dai platform

Disco

Content Management & Publishing Platform

Disco is the core content management system powering Tamedia's digital publications.

Focus Areas:

  • Article publishing and workflow
  • Multi-brand content distribution
  • Editorial tools and interfaces
  • Media asset management

Tech Stack:

  • Backend: Python, Django
  • Frontend: React, TypeScript
  • Database: PostgreSQL (RDS)
  • Cache: Valkey (Redis-compatible)
  • Storage: S3 + CloudFront CDN

Infrastructure:

  • Kubernetes Namespace: disco
  • AWS Account: disco-prod
  • Deployed Services: 8 microservices
  • Team Size: 12 engineers (Disco + FUW teams)

Key Services:

  • disco-api - Core content API
  • disco-cms - Editorial interface
  • disco-worker - Background job processing
  • disco-search - Content search service

Resources:

Contact:

  • Product Owner: TBA
  • Tech Lead: TBA
  • Office Hours: Wednesdays 14:00-15:00 CET

Unity

Multi-Brand Publishing Platform

Unity provides unified content distribution across Tamedia's portfolio of brands.

Focus Areas:

  • Cross-brand content syndication
  • Feed aggregation and distribution
  • Brand-specific customization
  • Performance optimization

Tech Stack:

  • Backend: Node.js, TypeScript
  • Frontend: React, Next.js
  • Database: PostgreSQL (RDS)
  • Storage: S3
  • API: GraphQL

Infrastructure:

  • Kubernetes Namespace: unity
  • AWS Account: unity-prod
  • Deployed Services: 12 microservices
  • Team Size: 15 engineers (Unity + Feed teams)

Key Services:

  • unity-api - Unified content API
  • unity-frontend - Web application
  • unity-feed - Feed aggregation service
  • unity-cache - Caching layer

Resources:

Contact:

  • Product Owner: TBA
  • Tech Lead: TBA
  • Office Hours: Tuesdays 10:00-11:00 CET

Discovery

Content Discovery & Recommendations

Discovery powers personalized content recommendations and user engagement features.

Focus Areas:

  • Machine learning recommendations
  • User behavior analytics
  • A/B testing framework
  • Personalization engine

Tech Stack:

  • Backend: Python, FastAPI
  • ML: TensorFlow, scikit-learn
  • Database: PostgreSQL (RDS)
  • Cache: Redis
  • Analytics: Amazon Athena

Infrastructure:

  • Kubernetes Namespace: discovery
  • AWS Account: discovery-prod
  • Deployed Services: 6 microservices
  • Team Size: 10 engineers

Key Services:

  • discovery-api - Recommendation API
  • discovery-ml - ML model serving
  • discovery-worker - Training pipeline
  • discovery-analytics - Analytics processing

Resources:

Contact:

  • Product Owner: TBA
  • Tech Lead: TBA
  • Office Hours: Thursdays 15:00-16:00 CET

Jazz

Audio & Multimedia Platform

Jazz handles audio content, podcasts, and multimedia distribution.

Focus Areas:

  • Podcast hosting and distribution
  • Audio streaming infrastructure
  • Multimedia asset management
  • Analytics and metrics

Tech Stack:

  • Backend: Go
  • Frontend: React
  • Database: PostgreSQL (RDS)
  • Storage: S3 + CloudFront
  • Streaming: AWS MediaConvert

Infrastructure:

  • Kubernetes Namespace: jazz
  • AWS Account: jazz-prod
  • Deployed Services: 5 microservices
  • Team Size: 8 engineers

Key Services:

  • jazz-api - Audio content API
  • jazz-player - Web player
  • jazz-transcoder - Media processing
  • jazz-analytics - Usage analytics

Resources:

Contact:

  • Product Owner: TBA
  • Tech Lead: TBA
  • Office Hours: Fridays 13:00-14:00 CET

dai

Internal Developer Platform

dai builds and maintains the shared infrastructure that powers all Tamedia engineering teams.

Focus Areas:

  • Kubernetes cluster management
  • CI/CD pipeline automation
  • Observability and monitoring
  • Developer experience tools
  • GenAI platform integration

Tech Stack:

  • Infrastructure: Terraform, AWS
  • Orchestration: Kubernetes, ArgoCD
  • Observability: Datadog, OpenCost
  • Portal: Backstage
  • Automation: Python, Go

Infrastructure:

  • Kubernetes Namespace: platform
  • AWS Account: dai
  • Managed Services: 15+ platform services
  • Team Size: 6 engineers

Platform Services:

  • Amazon EKS (Kubernetes)
  • ArgoCD (GitOps)
  • Datadog (Observability)
  • Backstage (Developer Portal)
  • VPC Lattice (Service Mesh)
  • Lacework (Security)
  • OpenCost (Cost Management)

Resources:

Contact:

  • Platform Lead: TBA
  • Office Hours: Tuesdays 14:00-15:00 CET
  • On-call: PagerDuty rotation

Getting Started with a Team

New to a team? Here's how to get onboarded:

1. Access Setup

Request access via #dai:

  • [ ] AWS SSO credentials
  • [ ] Kubernetes namespace access
  • [ ] GitHub organization membership
  • [ ] Datadog team dashboard
  • [ ] Team Slack channels

2. Local Development

# Configure AWS CLI
aws configure sso
# SSO Start URL: https://tamedia.awsapps.com/start

# Configure kubectl
aws eks update-kubeconfig \
  --region eu-central-1 \
  --name dai-platform-cluster

# Verify access
kubectl get pods -n <your-team-namespace>

3. Team Resources

Each team has:

  • GitHub Repositories - Source code and documentation
  • Kubernetes Namespace - Isolated deployment environment
  • Datadog Dashboard - Pre-configured monitoring
  • Slack Channels - Team communication
  • Confluence Space - Team wiki and runbooks

4. Deploy Your First Service

Follow the Getting Started Guide to deploy a service to your team's namespace.


Team Collaboration

Cross-Team Communication

  • dai: Infrastructure, deployment, monitoring help
  • Security: Compliance, vulnerability scanning, access management
  • Architecture: Design reviews, technical decisions
  • Product: Feature planning, roadmap alignment

Shared Resources

All teams share:

  • Kubernetes cluster
  • ArgoCD for deployments
  • Datadog for observability
  • Backstage for service catalog
  • VPC Lattice for cross-account networking

Support Channels

Need Channel Response Time
Platform issues #dai < 1 hour
Security concerns #security < 2 hours
General questions #engineering Best effort
Incidents PagerDuty Immediate

Teams page v1.0 - Last updated: 2025-01-05