[HN Gopher] Splitting Your Data and App APIs Up: Going Deeper
___________________________________________________________________
Splitting Your Data and App APIs Up: Going Deeper
Author : recursivedoubts
Score : 16 points
Date : 2021-09-20 12:07 UTC (1 days ago)
(HTM) web link (htmx.org)
(TXT) w3m dump (htmx.org)
| recursivedoubts wrote:
| heya HN: in this article I argue for using hypermedia for your
| application API, once you've realized that your app and your
| general data APIs have different needs
|
| would love feedback
| harryvederci wrote:
| Thanks for htmx! I recently noticed a similar issue in my side
| project, your timing with this article was perfect for me :)
| dang wrote:
| The other article mentioned was discussed here:
|
| _Don 't build a general-purpose API to power your own front end_
| - https://news.ycombinator.com/item?id=28511570 - Sept 2021 (106
| comments)
|
| Also the other other article:
|
| _Why I No Longer Use MVC Frameworks_ -
| https://news.ycombinator.com/item?id=11104356 - Feb 2016 (194
| comments)
|
| _Why I No Longer Use MVC Frameworks_ -
| https://news.ycombinator.com/item?id=11041999 - Feb 2016 (2
| comments)
|
| _Why I no longer use MVC frameworks_ -
| https://news.ycombinator.com/item?id=10740029 - Dec 2015 (92
| comments)
| bvrmn wrote:
| Yep, from one end backend devs don't want to provide API tied to
| current month UI, on other end they tend to religiously stick to
| "REST" API and frontend guys need to fetch zillion requests.
|
| You can do marvelous things with simple `GET
| /api/model?ids=1,2,3`.
___________________________________________________________________
(page generated 2021-09-21 23:01 UTC)