> For the complete documentation index, see [llms.txt](https://docs.4dsky.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.4dsky.com/adex-framework/benefits.md).

# Benefits

The ADEX framework has been explicitly designed to meet the core requirements for drone detect & avoid (DAA) systems, and airport flight information displays (FIDs). Unlike traditional centralised architectures, which concentrate data handling and routing within a small number of cloud or enterprise systems, ADEX distributes decision-making and data ownership across a framework of independently operated clients and servers. This structural difference allows it to better satisfy key operational objectives:

| <p> </p><p>Comparison</p><p> </p>   | <p> </p><p>Centralised Services</p><p> </p>                                                                                | <p> </p><p>ADEX</p><p> </p>                                                                                                         |
| ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| <p> </p><p>Latency</p><p> </p>      | <p> </p><p>Delays from network hops and cloud buffering, particularly in peak periods, can compromise latency.</p><p> </p> | <p> </p><p>Point-to-point architecture easily achieves sub-2 second latency, even during peak periods</p><p> </p>                   |
| <p> </p><p>Availability</p><p> </p> | <p> </p><p>Failure at the central hub causes loss of surveillance data across all dependent systems.</p><p> </p>           | <p> </p><p>Independent server/client operation with local processing localises faults and maintains service continuity.</p><p> </p> |
| <p> </p><p>Scalability</p><p> </p>  | <p> </p><p>Requires vertically integrated expansion, which can bottleneck growth.</p><p> </p>                              | <p> </p><p>Horizontally scalable through independent deployment of sensors, data servers, and display providers.</p><p> </p>        |
| <p> </p><p>Openness</p><p> </p>     | <p> </p><p>Closed interfaces limit integration and competitive innovation.</p><p> </p>                                     | <p> </p><p>Standards-based interfaces enable plug-and-play interoperability across the surveillance ecosystem.</p><p> </p>          |
| <p> </p><p>Agency</p><p> </p>       | <p> </p><p>External domain data handling reduces control for local stakeholders.</p><p> </p>                               | <p> </p><p>Servers and clients can be locally hosted, giving full control over data governance and security.</p><p> </p>            |
| <p> </p><p>Federation</p><p> </p>   | <p> </p><p>Limited compatibility with federated or independent systems.</p><p> </p>                                        | <p> </p><p>Supports discovery and coordination among independently managed systems.</p><p> </p>                                     |
| <p> </p><p>Resilience</p><p> </p>   | <p> </p><p>Central points of failure are vulnerable to cyber threats and outages.</p><p> </p>                              | <p> </p><p>Distributed architecture eliminates single points of failure and enables graceful degradation.</p><p> </p>               |