You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/advanced/technical/over_the_wire.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ The core principle of **abap2UI5** is to apply the proven **Over-the-Wire** conc
6
6
7
7
While popular frameworks like Hotwire, Livewire, and Phoenix LiveView follow this approach, **abap2UI5 adapts it to SAP’s technological environment**, using SAP UI5 for frontend rendering and ABAP for backend-driven UI definitions.
- The browser renders these definitions using a static UI5 application
22
22
- Users interact with the UI — the backend handles logic and updates
23
23
24
-
## From SSR to Over-the-Wire: A Brief History
24
+
###From SSR to Over-the-Wire: A Brief History
25
25
26
26
In early web development, **Server-Side Rendering (SSR)** was the default. Every user action triggered a full-page reload with a complete HTML response.
27
27
@@ -37,15 +37,15 @@ As a reaction, the **Over-the-Wire** paradigm re-emerged:
37
37
- Browsers update only specific parts of the page.
38
38
- Frontends stay simple and declarative.
39
39
40
-
### Architectural Comparison
40
+
####Architectural Comparison
41
41
42
42
| Approach | Data Flow | Rendering Location | Period |
- Backend-controlled UI logic and state management
68
68
69
-
### Key Characteristics
69
+
####Key Characteristics
70
70
- Static UI5 frontend delivered once.
71
71
- Backend defines and controls UI structure and behavior.
72
72
- Pure ABAP development — no custom JavaScript needed.
73
73
- Seamless alignment with SAP's UI5 and ABAP technology stack.
74
74
75
-
### Benefits for SAP Applications
75
+
####Benefits for SAP Applications
76
76
77
77
-**Simplified Frontend**: No custom JavaScript, no separate frontend development.
78
78
-**Faster Development Cycles**: All logic and UI changes are managed in ABAP.
79
79
-**Maintainable Architecture**: UI definitions reside in ABAP Classes — no frontend builds required.
80
80
-**Full SAP Integration**: Runs on any ERP or S/4HANA release, compatible with standard SAP infrastructure.
81
81
-**Perfect for Business Apps**: Ideal for CRUD-heavy applications, forms, tables, and dashboards.
82
82
83
-
### Limitations to Consider
83
+
####Limitations to Consider
84
84
85
85
- Not suitable for highly interactive, real-time collaboration apps.
86
86
- Offline functionality or complex client-side interactions are not covered.
87
87
- Less effective if frontend and backend teams work independently.
88
88
89
-
## Conclusion
89
+
###Conclusion
90
90
91
91
The **key idea of abap2UI5** is to bring the simplicity and efficiency of the Over-the-Wire pattern into the SAP ecosystem.
92
92
93
93
By shifting UI control back to the ABAP backend and leveraging SAP UI5 for rendering, abap2UI5 enables maintainable, pragmatic business applications — without the overhead of SPA architectures.
94
94
95
95
For typical enterprise apps — forms, dashboards, transactions — abap2UI5 offers a clean, backend-driven alternative with faster time-to-market and lower complexity.
96
96
97
-
## Further Reading
97
+
###Further Reading
98
98
-[Fiori-like web app development in pure ABAP with htmx and Fundamental](https://community.sap.com/t5/technology-blog-posts-by-members/fiori-like-web-app-development-in-pure-abap-with-htmx-and-fundamental/ba-p/13500763)
99
99
-[htmx in a nutshell](https://htmx.org/docs/#introduction)
100
100
-[HTML Over the Wire – Basecamp’s approach](https://signalvnoise.com/svn3/html-over-the-wire/)
0 commit comments