TIL the term "Zero-API" which is a synonym of the architectural style I described in my blog post. Thanks @moonbeamlabs and @stilkov. Episode 95 of your @INNOQ podcast was fun to listen to. dev.to/olibutzki/do-you-real…

Do you really need an API?

Maintaining an API is expensive. The post explains how you can get rid of an API between the backend and the frontend wihout the need to renounce modern frontend technolgies.

dev.to
1
7
Interesting blog! That's why i like @vaadin . There Zero-API (I didn't knew this term before) is a core concept.
3
1
1/ While this may be true, I assume Vaadin would be one of the most bloated solutions for Zero-API.
2
Bloated, why do you think so? vaadin.com/fusion

Fusion | Vaadin

A framework for building beautiful reactive client-side web apps with a Java backend. Secure. End-to-end type safety. Single deployment.

vaadin.com
1
1
The baseline to achieve zero-API is a single servlet and some HTML/JS. Of course you can add additional complexity on top. You probably want to have better abstractions, fair. But this is mainly to address DevUX, not to enable zero-API.
3
1
So Zero-API is just a fancy new name for server-side rendering like Spring Boot with Thymeleaf or PHP or Python/Django ? Or is it something else?
1
1
It was a joke. No API is often the best approach.
1
2
Replying to @stilkov @wimdeblauwe @taval @simas_ch @OliverLibutzki @moonbeamlabs @INNOQ @vaadin
And by that, I most definitely did not mean adding a ton of complexity to hide the fact that you’re building a web app :)

Nov 23, 2021 · 2:52 PM UTC
2