#hateoas — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #hateoas, aggregated by home.social.
-
In the June issue I went full #HATEOAS – a pattern considered as unnecessary bloat finding new purpose in LLMs interacting with APIs: https://www.bitoff.org/the-api-dispatch-12/
-
REST и RESTful API для QA Engineer
REST API является одним из наиболее распространённых способов взаимодействия между компонентами современных систем. В этой статье разберём основные принципы REST, HTTP-методы, статус-коды, идемпотентность, HATEOAS и особенности тестирования REST API. Материал будет полезен начинающим QA Engineer, разработчикам и всем, кто интересуется устройством веб-сервисов.
https://habr.com/ru/articles/1047104/
#REST #REST_API #RESTful_API #HTTP #API_тестирование #QA_Engineer #Postman #Swagger #HATEOAS #идемпотентность
-
🥁📢 Spring HATEOAS 3.1 GA, 3.0.4, and 2.5.3 released. Usual dependency upgrades, two CVEs fixed… https://spring.io/blog/2026/06/08/spring-hateoas-3-1-GA-3-0-7-and-2-5-3-released #Spring #HATEOAS 🍃🔗
-
Happy 14th birthday, Spring HATEOAS! 🍃🔗🥳 https://github.com/spring-projects/spring-hateoas/commit/21b1a4ec8cd76653fc49a6d7bc6b2c38a6d7685c #hypermedia #hateoas
-
I just released version 3.1.0 of "JSON:API for Spring HATEOAS". This is a feature release with dependency updates to Spring Boot 4.0.3, and Spring HATEOAS 3.0.2.
See https://github.com/toedter/spring-hateoas-jsonapi
Release Notes: https://github.com/toedter/spring-hateoas-jsonapi/releases/tag/v3.1.0 -
Todays challenge: remove FastAPI and SQLModel. Its a great framework with great DX. But with the prototyping phase I learned that taking the "usual" choice is contrary to my approach of #HATEOAS. The cracks were showing.
IMHO FastAPI is a great tool for small apps. However, I can see already unnecessary complexity in keeping front and backend components flexible. Still sticking with Starlette (also great DX) and SQLAlchemy (SQLModel lacks behind in async).
-
I just released version 3.0.1 of "JSON:API for Spring HATEOAS". This is a patch release with dependency updates to Spring Boot 4.0.1, and Spring HATEOAS 3.0.1.
See https://github.com/toedter/spring-hateoas-jsonapi
Release Notes: https://github.com/toedter/spring-hateoas-jsonapi/releases/tag/v3.0.1
-
I just released version 3.0.0 of "JSON:API for Spring HATEOAS". This is a major release with dependency updates to Spring Boot 4.0.0, Spring HATEOAS 3.0.0 and Jackson 3.
See https://github.com/toedter/spring-hateoas-jsonapi.
Version 3.0.0 removes all deprecated APIs from version 2.x.x. See the Migration Guide for details: https://toedter.github.io/spring-hateoas-jsonapi/3.0.0/reference/#migration-3-0-0
-
I just released version 2.2.0 of "JSON:API for Spring HATEOAS". This is a minor release with 2 new features and dependency updates to Spring Boot 3.5.8.
-
Migrating from Spring Boot to Quarkus?
I just published a hands-on tutorial that takes the classic Spring HATEOAS example and rebuilds it in Quarkus—covering both Link headers and HAL+JSON. Full code, tests, and production notes included.https://www.the-main-thread.com/p/spring-hateoas-to-quarkus-hypermedia-migration
-
URLs should be able to include HTTP verbs and headers.
They say "URLs define the "what" not the "how"" but protocol prefixes, file extensions, and query parameters are part of the how and yet they all exist in the URL.
Leaving HTTP verbs and headers out of URLs was an arbitrary decision.
#web #http #hypermedia #hateoas #webStandards #html #programming #networking
-
I just released version 2.1.4 of "JSON:API for Spring HATEOAS". This is a patch release with dependency updates to Spring Boot 3.5.0.
-
Det är en fröjd att arbeta med ett #API som följer #HATEOAS fullt ut. Jag slipper bläddra runt i källsystemet för att hitta rätt referenser eller rentav data som behövs för att färdigställa en komplex operation med flera anrop av olika typer som ska bli en del av lösningen. #livetSomITKonsult
-
I just released version 2.1.3 of "JSON:API for Spring HATEOAS". This is a bug fix release with dependency updates to the latest Spring libraries.
-
I just released version 2.1.2 of "JSON:API for Spring HATEOAS". This is a patch release with dependency updates to the latest Spring libraries.
-
New in "API Design Matters": "Wherefore HATEOAS", my views and commentary on Hypermedia APIs. https://apidesignmatters.substack.com/p/wherefore-hateoas
#APIDesignMatters #APIs #HATEOAS -
I released version 2.1.1 of JSON:API for Spring HATEOAS, see https://github.com/toedter/spring-hateoas-jsonapi/. This is a patch release, based on Spring Boot 3.4.0 and Spring HATEOAS 2.4.0.
-
People just like HTMX because it allows them use a language other than #JavaScript
There's no reason to use it if you like #JS
-
@colindean we used to be a proper #hypermedia!
-
I released version 2.1.0 of JSON:API for Spring HATEOAS, see https://github.com/toedter/spring-hateoas-jsonapi/. This is a feature release, based on Spring Boot 3.3.2 and Spring HATEOAS 2.3.1.
-
@wyatt8740 I too used to apply #HATEOAS: anything accessible through URLs in HTML documents was fair game. That was until I encountered a whole captchalogue of methods that websites use to deter scraping.
1. #RateLimit per IPv4 address and /24 and publish no AAAA record for IPv6, with 24-hour fail2ban penalties for exceeding a limit
2. #CAPTCHA
3. #LoginWall (what Twitter tried and still uses in a scaled-back form) -
I released version 2.0.8 of JSON:API for Spring HATEOAS, see https://github.com/toedter/spring-hateoas-jsonapi/. This is a patch release, based on Spring Boot 3.3.1 and Spring HATEOAS 2.3.0.
-
I've seen quite a few intriguing links recently discussing "progressive web apps" (#PWA) as preferable to "single page apps" (SPA) and getting back to fundamental web technology (html and css) rather than frameworks.
Today I've bumped in to #htmx which argues for preferring hypermedia applications and emphasising #HATEOAS principles. It seems like a great fit with PWA.
-
Have been playing around with #HATEOAS
Thinking it as document synchronization (i.e alpine-ajax) make it easier to maintain than html swapping (i.e htmx). And, I ended up having less endpoints. It's kinda inconvenience because it based on html `id` and it needs to be unique. But that's why it's predictable.
Tips: some framework has useId(key) to generate html `id`. If not then you can do
```go
const myID = "ident-" + uuidv4() // global
```