Skip to content

Commit e1d39e2

Browse files
authored
Update over_the_wire.md
1 parent 410b966 commit e1d39e2

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

docs/advanced/technical/over_the_wire.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ The core principle of **abap2UI5** is to apply the proven **Over-the-Wire** conc
66

77
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.
88

9-
## Concept Overview
9+
#### Concept Overview
1010

1111
```plaintext
1212
+------------------------+ +-----------------------+ +--------------------+
@@ -21,7 +21,7 @@ Flow:
2121
- The browser renders these definitions using a static UI5 application
2222
- Users interact with the UI — the backend handles logic and updates
2323

24-
## From SSR to Over-the-Wire: A Brief History
24+
### From SSR to Over-the-Wire: A Brief History
2525

2626
In early web development, **Server-Side Rendering (SSR)** was the default. Every user action triggered a full-page reload with a complete HTML response.
2727

@@ -37,15 +37,15 @@ As a reaction, the **Over-the-Wire** paradigm re-emerged:
3737
- Browsers update only specific parts of the page.
3838
- Frontends stay simple and declarative.
3939

40-
### Architectural Comparison
40+
#### Architectural Comparison
4141

4242
| Approach | Data Flow | Rendering Location | Period |
4343
|----------|-----------|-------------------|--------|
4444
| **SSR** | Full-page HTML responses | Entirely on the server | 1990s – 2010s |
4545
| **SPA** | Raw data (JSON), client builds UI | Client-side (JavaScript) | 2010s – today |
4646
| **Over-the-Wire** | HTML fragments for partial updates | Server renders, browser inserts | 2020s (re-emerging) |
4747

48-
## Over-the-Wire Frameworks
48+
#### Over-the-Wire Frameworks
4949

5050
Several frameworks successfully implement this pattern:
5151

@@ -59,42 +59,42 @@ Several frameworks successfully implement this pattern:
5959
| [Blazor Server](https://learn.microsoft.com/en-us/aspnet/core/blazor/) | Server-side UI rendering with SignalR | .NET / C# |
6060
| [Inertia.js](https://inertiajs.com/) | SPA-like experience with server-driven UI | JavaScript + Laravel/Rails |
6161

62-
## abap2UI5: Over-the-Wire for SAP
62+
### abap2UI5: Over-the-Wire for SAP
6363

6464
**abap2UI5** transfers the Over-the-Wire idea into SAP’s world by combining:
6565
- ABAP-based UI definitions (XML Views & JSON View-Models)
6666
- A static SAP UI5 frontend app for rendering
6767
- Backend-controlled UI logic and state management
6868

69-
### Key Characteristics
69+
#### Key Characteristics
7070
- Static UI5 frontend delivered once.
7171
- Backend defines and controls UI structure and behavior.
7272
- Pure ABAP development — no custom JavaScript needed.
7373
- Seamless alignment with SAP's UI5 and ABAP technology stack.
7474

75-
### Benefits for SAP Applications
75+
#### Benefits for SAP Applications
7676

7777
- **Simplified Frontend**: No custom JavaScript, no separate frontend development.
7878
- **Faster Development Cycles**: All logic and UI changes are managed in ABAP.
7979
- **Maintainable Architecture**: UI definitions reside in ABAP Classes — no frontend builds required.
8080
- **Full SAP Integration**: Runs on any ERP or S/4HANA release, compatible with standard SAP infrastructure.
8181
- **Perfect for Business Apps**: Ideal for CRUD-heavy applications, forms, tables, and dashboards.
8282

83-
### Limitations to Consider
83+
#### Limitations to Consider
8484

8585
- Not suitable for highly interactive, real-time collaboration apps.
8686
- Offline functionality or complex client-side interactions are not covered.
8787
- Less effective if frontend and backend teams work independently.
8888

89-
## Conclusion
89+
### Conclusion
9090

9191
The **key idea of abap2UI5** is to bring the simplicity and efficiency of the Over-the-Wire pattern into the SAP ecosystem.
9292

9393
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.
9494

9595
For typical enterprise apps — forms, dashboards, transactions — abap2UI5 offers a clean, backend-driven alternative with faster time-to-market and lower complexity.
9696

97-
## Further Reading
97+
### Further Reading
9898
- [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)
9999
- [htmx in a nutshell](https://htmx.org/docs/#introduction)
100100
- [HTML Over the Wire – Basecamp’s approach](https://signalvnoise.com/svn3/html-over-the-wire/)

0 commit comments

Comments
 (0)