What's the difference between Traditional and DXAPI

Please find the details below,

Feature DX API V1 DX API V2
UI Architecture Section & Harness-based (traditional UI) View-based authoring (React-powered Constellation)
Response Data All values returned as strings Returns type values (Boolean, Integer, Date, etc.)
Chattiness High – multiple API calls needed for screen flows (Create case → Get assignment → Action → Submit) Low – reduced calls; e.g., PATCH response includes next view, minimizing round trips
Performance Slower response; more HTTP overhead Improved rendering speed and fewer HTTP requests
Supported Rules Harness, Sections (must be autogenerated) Views (Constellation UI), modular UI components
UI Technology Works with Theme-Cosmos & traditional UI Designed for Constellation (React-based fully modern architecture)
Metadata Support Limited Rich metadata for custom front-end rendering and channel independence
Sessions Requires sticky session in some scenarios Stateless → No sticky session required
Extensibility Limited for custom components Easier extensibility; supports personalization, enhanced social collaboration features (Followers, Pulse)
End-point Categories Case, Assignment basic calls Expanded endpoints: Data Views, Social (mentions, messages), Attachments, Personalization, Audit
Best Practice Direction Deprecated for new builds; only for legacy apps Recommended for all new apps for future-proofing