94thAirhacksQ&A.md

Ask questions and see you at January, 10th, 8.PM. CET: youtube.com/c/bienadam

Also checkout recent episode:

Please keep the questions Jakarta EE-stic. Means: as short and as concise as only possible. Feel free to ask several, shorter questions. Upcoming airhacks.tv events are also going to be announced at meetup.com/airhacks

When requesting HTTP PATCH on Java 17 (JAX RS client) using the I get: java.net.ProtocolException: Invalid HTTP method: PATCH
The same does not happen on JDK 11. The new HTTPClient does not seem to support PATCH at all.

How do you work around this problem? Is using the HTTP method override in the request header the only option?

Hi Adam,
If my goal is to avoid using the JPA on a project as developers need to know what is going under the hood to exclude performance issues.
As a JPA alternative, it could be a plain JDBC, JPA native query.
Spring ecosystem has the jdbcTemplate library.
What would be your recommendation for writing SQL (including the "database-specific SQL" use case) on the Microprofile stack with Quarkus?
Regards, Aleksandr T.

Hi Adam, my question is about GlassFish vs Payara. I thought the name GlassFish was abandoned and continued as Payara. But now many new GlassFish versions are coming out and they have more updated components and support new JDK versions. Like I tried compiling Payara on JDK 17 and JDK 11, but it failed all the time. GlassFish compiles without issues on JDK 17.

Can you tell us more about how they relate now?

@sm-a if I remember well from back in the days, @AdamBien hosts his websites in his basements on his own server. I remember that he used to post specs (and sometimes pictures) of the configuration of his servers when he bought or upgraded some of them.

@BreDenro Payara is fully based on the open source Glassfish for which you can have a enterprise level technical support, it came to life after Oracle ceased to provide technical support for Glassfish and since support is very important for entreprises, Payara was born and is fully Glashfish-based.

@dwamara the only difference between Payara and GlassFish is the support option?

@BreDenro the main difference yes, that was what brought them to the market then they added some other features but as said, they are based in glassfish.
In case you would like to see more features, you can visit this page but it was for the version 5, no idea what they now have since I completely moved from payara micro to quarkus when it got out: https://www.payara.fish/glassfish-vs-payara-server-5

Hey Adam,
We have an interesting use case that might be a good fit for Message Queues,
An application needs to call around 5-7 operations(web hooks) per event on some write to the database, these writes could be around 2000 per hour and we need to individually retry the web hooks if they fail. Do you think that it is overkill to use a message queue? Would you recommend setting it up (the queue) ourselves or use some hosted solution?
We are using Aws for most of our hosting.

What we don't need is persistence (hence not Kafka) but reliable messages that we can after a successful external call we can say (OK this one is processed) however since this is not the core application but some external services that if are failing should not interfere with the actual code hence I was thinking no simple query for the list of hooks and call them.
Also did you recently use JMS? Do you know any recent changes?

Thanks in advance,
Guru

Did you have a look at hasura? https://hasura.io/ its very interesting to give crud from a Database + fine grained row + column access control using roles-> what is your experience with graphQL?