itsscb/htmx
1
0
Fork 0
mirror of https://github.com/bigskysoftware/htmx.git synced 2025-10-03 07:45:21 +00:00
Code Issues Packages Projects Releases Wiki Activity

update essay

Browse Source
This commit is contained in:
Carson Gross 2023-05-01 08:33:02 -06:00
parent 659942cc87
commit 2aa5b89f72
2 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
www/content/essays/_index.md
View File

@ -15,6 +15,7 @@ insert_anchor_links = "left"
* [Hypermedia APIs vs. Data APIs](@/essays/hypermedia-apis-vs-data-apis.md) * [Hypermedia APIs vs. Data APIs](@/essays/hypermedia-apis-vs-data-apis.md)
* [Complexity Budget](@/essays/complexity-budget.md) * [Complexity Budget](@/essays/complexity-budget.md)
* [SPA Alternative](@/essays/spa-alternative.md) * [SPA Alternative](@/essays/spa-alternative.md)
* [Two Approaches To Decoupling](@/essays/two-approaches-to-decoupling.md)
* [A Response To "Have SPAs Ruined The Web"](@/essays/a-response-to-rich-harris.md) * [A Response To "Have SPAs Ruined The Web"](@/essays/a-response-to-rich-harris.md)
* [Template Fragments](@/essays/template-fragments.md) * [Template Fragments](@/essays/template-fragments.md)
* [View Transitions](@/essays/view-transitions.md) * [View Transitions](@/essays/view-transitions.md)

10
www/content/essays/two-approaches-to-decoupling.md
View File

@ -1,8 +1,9 @@
+++ +++
title = "Two Approaches To Decoupling" title = "Two Approaches To Decoupling"
date = 2022-10-23 date = 2022-05-01
updated = 2023-02-03 updated = 2022-05-01
[taxonomies] [taxonomies]
tag = ["posts"]
+++ +++
> The central feature that distinguishes the REST architectural style from other network-based styles is its emphasis on > The central feature that distinguishes the REST architectural style from other network-based styles is its emphasis on
@ -17,7 +18,7 @@ In this essay we will look at two different types of decoupling in the context o
* Decoupling at the _application level_ via a generic JSON Data API * Decoupling at the _application level_ via a generic JSON Data API
* Decoupling at the _network architecture level_ via a hypermedia API * Decoupling at the _network architecture level_ via a hypermedia API
We will see that, at the application level, a hypermedia API tighlty couples your front-end and back-end. Despite this We will see that, at the application level, a hypermedia API tightly couples your front-end and back-end. Despite this
fact, surprisingly, the hypermedia API is in fact more resilient in the face of change. fact, surprisingly, the hypermedia API is in fact more resilient in the face of change.
## Coupling ## Coupling
@ -157,6 +158,9 @@ client (in the case of the web, the browser) from the hypermedia server.
This is accomplished primarily via the Uniform Interface constraint of REST and, in particular, by using This is accomplished primarily via the Uniform Interface constraint of REST and, in particular, by using
Hypermedia As The Engine of Application State ([HATOEAS](/essays/hateoas)). Hypermedia As The Engine of Application State ([HATOEAS](/essays/hateoas)).
This style of decoupling allows tighter coupling at the higher, application level, which we have seen may be an
_inherent_ coupling, while still retaining the benefits of decoupling for the overall system.
### Decoupling Via Hypermedia In Practice ### Decoupling Via Hypermedia In Practice
How does this sort of decoupling work in practice? Well, let's say that we wish to remove the ability to transfer money How does this sort of decoupling work in practice? Well, let's say that we wish to remove the ability to transfer money