93rdAirhacksQ&A.md

93rdAirhacksQ&A.md

Ask questions and see you at December, 2nd, 8.PM. CET: youtube.com/c/bienadam/live

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

Hello sir,

What is your approach to development, test, production stages when it comes to persistence.xml file, how do you use the schema creation feature, and how to protect production from deploying some artifact with a wrongly attributed persistence.xml where javax.persistence.schema-generation.database.action is set to drop-and-create option?

Thank you very much.

Hey! What do you think of the one container one process approach? And multithreading is taken over by the orchestration system through the creation of the required number of containers. Is this approach good for Java applications?

The microprofile fault tolerance api will allow us to limit the number of concurrent calls to our business method with Bulkhead annotation. Is it possible to use the same annotation for the microprofile rest client method in interface definition?

Graviton and Ampere will reduce the cost of cloud services?

Hi Adam, thanks for the great Q&A sessions.

Since your Devflex session "Hey Enterprise EJB Developers Now Is The Time To Go Serverless" I can't get this topic Serverless Computing out of my head. I have already migrated parts of our modular monolith (Jakarta EE 8) to Quarkus as part of a POC and tried it out as an Azure Function. It was very exciting and interesting.

I would be interested if it is realistic to migrate a modular monolith completely to Serverless. Do you have any experience with such projects?

Can you possibly show an example how the orchestration of such a serverless architecture in production can look like? Communication between the functions, 0-downtime deployment etc.

Greetings
Denis