Bayern International & Invest in Bavaria Websites¶

~by port-neo~

Architecture overview¶

The Bayern International ecosystem consists of two independent systems with distinct architectures.

System Context (C4 L1)¶

Key System Characteristics¶

Bayern International System

• Architecture: Traditional TYPO3 12.4.25 with server-side rendering
• Complexity: 24+ custom extensions with sophisticated business logic
• Infrastructure: Hetzner dedicated server with Docker containers
• Traffic: ~240 GB/month (spikes to 1TB during events)

Invest in Bavaria System

• Architecture: Headless TYPO3 backend + Next.js 14 frontend PWA
• Infrastructure: Digital Ocean backend, Vercel frontend
• Traffic: ~443 GB/month
• Workflow: Custom content release with approval process

2. Data Flow Summary (Simplified for Stakeholders)¶

Critical Data Exchanges¶

High-Frequency Data Flows

1. GEFAK ↔ Bayern International

   • Frequency: Every 5 minutes
   • Data Type: Business directory information (XML)
   • Security: GPG encryption
   • Business Impact: Real-time business listings and search functionality

2. Both Systems → Microsoft Dynamics 365

   • Frequency: On-demand (lead generation events)
   • Data Type: Customer leads and contact information
   • Processing: Queue-based to handle API latency
   • Business Impact: Sales pipeline and customer relationship management

Communication Flows

1. Both Systems → CleverReach
   • Frequency: Campaign-based
   • Data Type: Newsletter content and subscriber lists
   • Business Impact: Email marketing and stakeholder communication

Data Volume & Performance¶

• Total Annual Transfer: 8.2TB across both systems
• Peak Traffic: Event-driven spikes (up to 1TB/month during major events)
• Critical Dependencies: GEFAK integration (business continuity risk if interrupted)

3. Integration Risk Matrix¶

Risk Categories Explained¶

🔴 HIGH RISK - Immediate Action Required

• GEFAK: 5-minute data sync critical for business directory accuracy
• Dynamics 365: Lead generation directly impacts revenue

🟡 MEDIUM RISK - Planned Mitigation

• Translation/AI Services: Workarounds available but impact efficiency
• Search Engine: Affects user experience but not business continuity

🟢 LOW RISK - Monitor & Plan

• Booking Integration: Limited scope, manual alternatives exist

Recommended Risk Mitigation Actions¶

1. Implement monitoring alerts for GEFAK and Dynamics 365 integrations
2. Create backup data sync procedures for critical integrations
3. Document manual fallback processes for all external services
4. Establish SLA monitoring for all high-risk integrations

4. Stakeholder Communication Guide¶

For Marketing Department (Non-Technical)¶

What You Need to Know:

• Two Websites: Bayern International (traditional) and Invest in Bavaria (modern)
• Automatic Features: Translation, content generation, business directory updates
• Dependencies: Some features rely on external services (may occasionally be unavailable)

When Things Go Wrong:

• Business Directory Issues: Contact development team immediately (affects core functionality)
• Translation Problems: Manual translation may be needed temporarily
• Newsletter Issues: Alternative sending methods available

Planning Considerations:

• Major Events: Expect higher system load, plan content updates in advance
• New Features: Technical complexity varies, discuss timeline expectations early

For Design & Project Management (Non-Technical)¶

System Boundaries:

• In Our Control: Website content, design, user experience
• External Dependencies: Translation services, CRM integration, business data
• Shared Responsibility: Content approval workflows, performance optimization

Project Planning Guidelines:

• Simple Changes: Content updates, design modifications (low complexity)
• Medium Changes: New features using existing integrations (medium complexity)
• Complex Changes: New external integrations, architectural changes (high complexity)

Risk Communication:

• Green Light: Changes within our systems only
• Yellow Light: Changes affecting external integrations (requires testing)
• Red Light: Changes to critical data flows (requires careful planning)

For Development Team (Technical)¶

Architecture Overview:

• System 1: Traditional TYPO3 with 24+ custom extensions
• System 2: Headless TYPO3 + Next.js PWA
• Critical Integrations: GEFAK (GPG/XML), Dynamics 365 (REST/Queue)
• Infrastructure: Multi-platform (Hetzner, Digital Ocean, Vercel)

Monitoring Priorities:

1. GEFAK data sync status and timing
2. Dynamics 365 API response times and queue health
3. System performance during traffic spikes
4. External service availability and response times

Documentation References:

• Detailed Analysis: /assist/output/01_starting_result.md
• Project Roadmap: /assist/progress/01_project_roadmap.md
• Technical Specifications: Available in current documentation directory

Entrypoints¶

User/Developer Guides¶