🎯 What You'll Learn

  • What Dione actually is (and isn't)
  • The real technology stack you'll be working with
  • Multi-tenant architecture patterns
  • Platform strengths and limitations
  • Business context for architectural decisions

What Dione Actually Is

Dione is a financial services platform for foreign exchange (FX) transactions, specifically built for companies like Currencies Direct, TorFX, and other financial service providers. It's been in production for over a decade, which means you'll find both modern patterns and legacy decisions that made sense at the time.

Core Business: Currency exchange, international money transfers, payment processing, and regulatory compliance (including Open Banking).

💡 Key Insight

This platform processes millions of dollars in FX transactions daily. When you see "weird" code patterns, remember they're often solving real financial compliance or performance requirements.

The Tech Stack Reality

Technology Stack
Frontend: JSP + jQuery (yes, really)
Backend: Java + Spring Framework (3.2/4.3 - not the latest)
Web Services: SOAP + Apache CXF (no REST APIs)
Database: Microsoft SQL Server
Build: Maven (with some manual steps)
Deploy: Jenkins + Ansible + JBoss EAP 7.0
Cache: Infinispan

⚠️ Reality Check

This is not a modern microservices architecture. It's a monolithic, multi-tenant SOAP-based platform. Don't expect GraphQL, REST APIs, or container orchestration.

Multi-Tenant Architecture

The platform serves multiple organizations from a single codebase:

  • Organization ID filters everything
  • Site-specific branding and configuration
  • Shared infrastructure with isolated data
ngop.properties (lines 225-232)
1.ngop.homecurrency=GBP     # TorFX UK
2.ngop.homecurrency=GBP     # Currencies Direct UK  
3.ngop.homecurrency=AUD     # TorFX Australia
6.ngop.homecurrency=GBP     # Currencies Direct Legacy
8.ngop.homecurrency=GBP     # Ramsdens
9.ngop.homecurrency=GBP     # FCG

Each organization has its own:

  • Currency configurations
  • Compliance rules
  • Branding and messaging
  • External service integrations
  • User workflows

What The Platform Does Well

🏛️

Financial compliance

Open Banking, PCI compliance, regulatory reporting - all handled correctly in production

💱

Multi-currency support

Handles 30+ currencies with complex pricing, margin calculations, and settlement

High availability

Production uptime is actually good - the platform rarely goes down

📊

Audit trails

Everything is logged and traceable for regulatory compliance

🔗

Integration

Connects to 10+ external systems reliably (Salesforce, payment processors, banks)

What The Platform Doesn't Do

🚫 No REST APIs

Everything is SOAP - no JSON REST endpoints exist

🚫 No Modern Frontend

JSP and jQuery - no React, Vue, or Angular

🚫 No Container Deployment

Traditional JBoss deployment - no Docker or Kubernetes

🚫 No Comprehensive Testing

Unit tests exist but integration/e2e testing is limited

🚫 No API Versioning

Single version APIs - changes must be backward compatible

🎯 The Bottom Line

Dione is a functional, profitable platform that has been serving customers for over a decade. It works. Your job is to work with it, not against it.

📝 Chapter Quiz

Test your understanding of the Dione platform overview with these questions:

Question 1: What type of architecture does Dione use?

Question 2: Which database does Dione primarily use?

Question 3: What is the main business focus of the Dione platform?