Dragon & Garuda Network

A cross-border API + CDN framework to improve digital access for ticketing and itineraries between China ↔ Indonesia.

Table of Contents

• Overview
• Current Focus
• Development Stages
• Cost/Time Matrix
• Key Insights
• Documentation
• Repository Structure
• Getting Started
• Next Steps
• Contributing

---

Overview

The Dragon & Garuda Network is a two-way consumer bridge between China and Indonesia, starting with tourism ticketing and itineraries:

• China → Indonesia: Wanda Theme Parks offered to Indonesian travelers.
• Indonesia → China: National Parks (Komodo, Raja Ampat, Bromo, etc.) offered to Chinese travelers.

The framework uses CDN-first delivery:

• China: Aliyun or Tencent CDN.
• Indonesia: Telkomsigma, CDNetworks, or Cloudflare.
• Neutral origins: GitHub Pages at prototype stage, moving to Jakarta and China data centers.
• Payments: Alipay/WeChat Pay (China) ↔ OVO, DANA, GoPay, Midtrans (Indonesia).

---

Current Focus

• Wanda Theme Parks (China) ⇄ Indonesian National Parks.
• Prototype with mock APIs: /itinerary, /availability, /book, /order.
• Lightweight CDN delivery on both sides (Aliyun for CN, Telkom/CDNetworks for ID).

---

Development Stages

1. Prototype – Mock APIs + sandbox payments (Midtrans/WeChat).
2. Pilot – Integrate OTA APIs (Trip.com, Traveloka).
3. Scale-up – Direct partner APIs + localized payments.
4. Mature Ops – Cancel/refund endpoints, analytics, partner dashboards.

---

Future Scope

This framework is designed to scale beyond China–Indonesia into other APAC markets:
South Korea, Japan, Taiwan, Singapore, Hong Kong, and Australia/New Zealand.

See docs/apac_expansion.md for details.

---

Cost/Time Matrix

Stage	Infra setup	CDN delivery	Origin hosting	API integration	Cost (monthly)	Time to set up	What you can demo
Prototype	GitHub Pages origins	Aliyun (CN dev) + CDNetworks (ID)	Repos with mock JSON + HTML	Mock APIs + sandbox payments	~$40–70	1–2 weeks	Cached itineraries, simulated bookings
Pilot	Add 1 VM in Jakarta/Singapore	Same CDNs	GitHub + VM	OTA APIs (Trip.com, Traveloka, Fliggy)	~$100–150	4–6 weeks	Live availability + test bookings
Scale-up	CN origin (Aliyun OSS) + ID DC	Aliyun/Tencent (CN) + Telkom/CDNs (ID)	Regional hosting	Direct partner APIs, live payments	~$300–500+	3–6 months	Production-grade flow + dashboards
Mature ops	Redundant multi-CDN + PoPs	Aliyun + Tencent + CDNetworks + CF	Dedicated clusters	All partner APIs, analytics, cancellations	$500–1,000+	6–12 months	Enterprise-grade ops

---

Key Insights

• Prototype is fast & low-cost (<$70/month, ~2 weeks).
• Pilot unlocks real OTA data (~$150/month, ~1 month).
• Scale-up requires regional hosting (~$300–500/month).
• Mature ops = enterprise readiness ($500–1,000+/month, 6–12 months).

---

Next Steps

• Continue building prototype with GitHub origins + dual CDNs.
• Identify and engage technical contacts at Wanda Group and Indonesian National Parks.
• Transition APIs from mock → OTA → direct partner.
• Prepare partner pitch materials.

---

Documentation

📖 Complete Documentation Index – Comprehensive guide to all documentation

Comprehensive technical documentation is available in the docs/ directory:

Core Documentation

• API Specification – Unified API contract for all endpoints
• Architecture Guide – CDN + API layer design and authentication flows
• Codebase Architecture – Repository structure and development guide
• Roadmap – Staged development path from prototype to production

Strategic Planning

• APAC Expansion – Future scope for regional expansion
• Partner Pitch Deck – Presentation materials for partner engagement
• Commit Style Guide – Contribution conventions

Quick Links

• API endpoints: /itinerary, /availability, /book, /order
• Supported regions: China (CN) ↔ Indonesia (ID)
• Payment providers: Alipay/WeChat Pay ↔ OVO/DANA/GoPay/Midtrans

---

Repository Structure

Dragon_Garuda_Network/
├── README.md                    # This file - project overview
├── CONTRIBUTING.md              # Contribution guidelines
├── LICENSE                      # Project license
├── docs/                        # Technical documentation
│   ├── architecture.md          # System architecture
│   ├── codebase_architecture.md # Development guide
│   ├── roadmap.md              # Development roadmap
│   ├── apac_expansion.md       # Regional expansion plans
│   ├── partner_pitch_deck.md   # Partner materials
│   └── commit_style.md         # Git conventions
└── shared/                      # Shared specifications
    └── api_spec.md             # Unified API contract

---

Getting Started

For Developers

1. Review the API Specification to understand the unified API contract
2. Read the Codebase Architecture for repository organization
3. Check the Roadmap for current development stage
4. Follow the Commit Style Guide when contributing

For Partners

1. Start with the Partner Pitch Deck for an overview
2. Review the Architecture Guide for technical integration details
3. See the Cost/Time Matrix above for implementation estimates
4. Contact us to discuss pilot integration opportunities

---

Contributing

See CONTRIBUTING.md for guidelines on adding regional flows or documentation.