Ask questions and see you on October 6 at 8pm CET: youtube.com/c/bienadam
Also check out the latest episode:
Please keep the questions as short and as concise as only possible. Feel free to ask multiple, shorter questions. I will also answer some questions in my "shorts" youtube.com/@bienadam/shorts between the shows.
Upcoming airhacks.tv events will also be announced at meetup.com/airhacks
New: The airhacks.tv discord server: discord.gg/airhacks
LLM-driven development
100 episodes back time machine, questions from the 39th episode from May 6th, 2017:
"Follow up JSF modularization, Beautiful Java EE frontends, JWT Authentication With Java EE, Java EE CRUD Code Generators / bootstrap Frameworks, Are there still use cases for EARs?, Serialising a dynamic subset of fields / properties, JPA with WildFly, Testing @asynchronous methods, Fat WARs -- if you really need them, Use Cases and experiences with Java EE Batch, Multitenancy with JPA, Opinions about Multiple WARs, one server, one DB"
https://adambien.blog/roller/abien/entry/ear_use_cases_jsf_modularization
Hi Adam!
What approach would you recommend to improve the performance of a AWS serverless REST API current services used are Route53, rest API Gateway (with private VPC), Lambda and RDS (on the same private VPC).
The service takes about 11sec to start what it means is because of the timeout of 10sec of a Lambda it takes 21sec.
I already tried to remove Liquibase (and it improved 2/3 seconds) and changed the architecture to x86 and it also improved 1/2 sec so now the startup sometimes is bellow 10 secs, but its not consistent.
The project is very similar to your plain examples with Java and Quarkus.
Thanks in advance!
Serverless and serverful architectural styles are available