Ask questions and see you at December, 7th, 8.PM. CET: https://vimeo.com/event/154379
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
Hi Adam!
I watched your latest videos and I'm interested in a question about a rest client fault. For example, the task is to periodically send data through the scheduler using rest client, how to properly handle the case of a client crash (fault) so that the scheduler can stop before the client is restored to work? I am thinking of a global flag that stores client state information, maybe failover has a more elegant solution?
I building code where there are data models in different layers of the application which are very much alike. This causes a lot of boilerplate code and unittests which is hard to maintain.
I would like to use some mechanism from which I could generate the model classes and use mapping software to get data from model1 to model2.
What would be a good library which can be configured to
I know about odata but this has its own data model which is another extra model from which I need to map to my internal model(s).
I also know about graphql but I want to use plain REST resources from my client software for now.
I want to be able to configure for a user how many request per second he can fire onto my server.
And my server then should return the nr of possible requests in a response header.
And of course my server should return http response code 429 (too many request) when the max nr requests/sec is depleted.
How would you do this?
@thephi did you have a look at Mapstruct (https://mapstruct.org/)?
@ashburnere yes I am investigating it, it is a very elaborate tool but I'm not sure yet if I can use it but it looks promising.
@AdamBien
As creator of Jwtenizer do you recommend to you clients to implement in-house authentication and authorization workflows? Quarkus JPA Security and JWT Security makes it look like an easy job initially, but I fear things get tough when you realize you need:
- self-registration
- login
- passwordless login
- profile update
- forgotten password workflow
- multi-factor authentication
- email verification
- user management UI console
... Or do you recommend external providers such as Okta, Auth0, AWS Cogito?
There is also this up-and-coming German middleware ORY/Kratos, but they are very opinionated, do not recommend JWT tokens and do a lot fo server-side rendering to implement workflows.
What do your clients usually end up doing?
Have you had a look at https://gluu.org/? It probably suites you better?
Adam, I've heard you recently mention both OData and GraphQL on your podcast along with some pros/cons for each. Have you heard of or used the JSON:API specification? It has a clean representation for both URLs and requests/responses and is intuitive to use. Certainly not as popular as either OData/GraphQL, but I find it to be more in alignment with RESTful and HTTP conventions.
I have a work-in-progress library (jsonapi-rvp) that drops in to Jakarta EE-stic runtime environments to expose JPA entities via JSON:API. The only dependencies are runtime Jakarta EE specs and it requires Java 11. Just posting in case you or any listeners would like to play with it and suggest improvements if it's found to be useful.