Hilla 2.2 is out with React form support

Middleware is also an interesting word for the work the annotation does

“and then I use the X to fetch items to show from the server”

“and then I use X to send the changes to the server and store then in the db”

Now I wanna go back to endpoint

I’m in team Endpoint :wink:

Difficult crowd :sweat_smile:

If we zoom in on “endpoint”, then how could we help people avoid the association with REST? We have observed that many make this association subconsciously and are then confused about details like HTTP verbs.

One thought that we had at some point was to refer to them as “RPC endpoints”. Any other perspectives?

:thinking: you also call it Backend for Frontend architecture… so the frontend is typescript and the backend are the entry points on the server with hilla.

@BackendForFrontend? Even tho nobody would wanna type it

Has @FrontendService already been proposed (and rejected) ?

Haven’t heard it here at least :slightly_smiling_face:

It is a “service” but might be distinct enough to stand out from the regular business logic services

I think @EntryPoint was also suggested many years ago when we settled on the current name

Google has gRPC so maybe we should have hRPC?

I’m still debating with myself what speaks against HillaEndpoint or HillaController. Looking at spring boot, it also uses “itself” to name things… like SpringBootApplication, -Test and so on… so naming the annotation with Hilla could increase recognition of the pattern… additionally people know the term RestController from spring which you wanna make sure they don’t mix up with hilla… so adding hilla in the mix could even help with autocorrect there when people type controller

Yet another perspective is that your intent is still to call the business service. It just an irrelevant detail that you call it through a converter/adapter/handler/something that takes care of the DTO stuff

What about @WebService :wink:

it looks so SOAP :grin:

Naming, the hardest part of software development :smile:

It’s exactly like SOAP except that you define the API in Java instead of in XML

@Shampoo

Perfect, now I can advertise it to our government agencies as SOAP-like :sunglasses: they gonna love it!

That’s code first WebService style