Capital Market Trading Infrastructure — Bangladesh

Systems connected to a stock exchange leave no room for improvisation. Order sessions must stay connected for the whole trading day, market data must arrive without gaps, and every production change has to be planned around market hours. A mistake is not just downtime — it affects real trades.

1. L1Exchange connectivity
   • FIX sessions (orders & executions)
   • FAST market data feeds
2. L2Exchange platforms
   • Nasdaq-based trading systems
   • DSE
   • CSE
3. L3Services
   • Order handling services
   • Market data processing
4. L4Operations
   • Monitoring & alerting
   • Controlled release process
   • Test environments

Plan every change around the market

Production changes happen outside trading hours, with a tested rollback ready before the market opens. During trading hours, stability comes first.

Treat session health as a first-class signal

FIX session state, heartbeats, and message sequence numbers, plus gaps in FAST market data, are watched as closely as CPU or memory — they are the first sign something is wrong.

Test against non-production environments first

Changes are validated in test environments before they reach production, so protocol or configuration issues surface before they can affect trading.

• Supported deployment and operation of services connected to DSE and CSE trading systems.
• Worked with FIX protocol sessions for order flow and FAST-encoded market data feeds.
• Followed strict change control, with releases scheduled around market hours.
• Monitored connectivity and service health throughout the trading day.
• Documented operational procedures for day-to-day running and incident response.

• Client, system, and network details are kept confidential and are not published here.
• Access to production restricted to what each role requires.
• Changes tracked and reviewable, with a clear audit trail.

• Stable operations across the trading day.
• Predictable, low-risk releases outside market hours.
• Faster diagnosis of issues thanks to protocol-level visibility.

• In capital markets, reliability is measured trading day by trading day — not by uptime percentages.
• Understanding the protocols themselves (FIX sequence numbers, FAST templates) makes incidents far quicker to diagnose.
• Discipline around change windows matters more than any single tool.