Lesson 2.2 - Broker System Overview¶
A client presses Buy XAUUSD and sees one click. Behind that click, the broker environment checks access, account status, margin, risk rules, quote availability, routing, execution and record storage.
Dealer training should focus on the operating question: which layer may explain the symptom?
High-Level Operating Layers¶
| Layer | What it does | Dealer question |
|---|---|---|
| Client access | Login, session and connection | Can the client connect normally? |
| Trade platform | Orders, positions, margin and account state | Is the platform processing trades normally? |
| Quote layer | Bid/ask, spread and price freshness | Are prices current and reasonable? |
| Bridge / routing | Sends validated orders to execution destinations | Is queue, routing or transfer delayed? |
| Quote source / execution | Provides reference quotes and execution-quality signals | Are fill time, latency, timeout or available quote depth abnormal? |
| Risk tools | Exposure, risk status and control rules | Did a risk rule or control affect the trade? |
| Reporting / history | Stores and reports trade records | Do reports match platform records? |
Dealer Investigation Pattern¶
When a problem appears, avoid broad statements such as "MT5 is broken." Use a layer-based check:
- What exactly is the symptom?
- Which platform, symbol, account or group is affected?
- Is the issue about login, quote, order processing, execution, risk control or reporting?
- What evidence supports that layer?
- Who owns the next action?
Example: XAUUSD Execution Delay¶
If XAUUSD orders are delayed while clients can still log in, Access Server is unlikely to be the first focus. The Dealer should check order timestamps, Bridge queue, routing latency, quote-source status, platform-rule rejects, timeout rates and related market conditions.
Boundary¶
Dealers monitor and investigate. Technology owns infrastructure diagnosis. Risk owns risk-control approval. Production-impacting changes require formal approval and must be carried out by personnel authorised for the specific action.
Practical Training¶
Scenario
A client can log in to MT4, but XAUUSD orders are taking longer than expected to complete.
What to check
Access status, Trade Server timestamps, Bridge queue, routing latency, quote-source status, platform-rule rejects and timeout evidence.
Common mistake
Checking only whether the client can log in and assuming that normal access means the entire order path is healthy.
Correct handling
Separate the access path from the execution path. Focus the review on order timestamps and the movement from the platform through the Bridge and quote-source or execution layers.
Summary¶
A Dealer does not need to diagnose every technical root cause. The Dealer must identify the likely affected layer, preserve evidence, remain within authority and route the issue to the correct owner.
Completion Criteria¶
- Can explain the key risk or operational objective of this lesson
- Can identify the required systems, data, or evidence to review
- Can describe the correct escalation or handling process
- Can apply the lesson correctly in a supervised scenario