As my Vert.x microservices grow in complexity, I’ve felt the need for dependency injection to keep things modular and maintainable. But instead of bringing in the weight of Spring, I looked for lighter alternatives—and that’s where Dagger 2 comes in.
https://t.co/A53MRBTfHk
Yeah it’s all good as long as there is no ORM, Spring or any EE for that matter. Vert.x and JDBC all the way and we use Lombok to keep the classes clean.
The best ways to waste time in discussions in the Java world:
- Lombok VS. non-Lombok
- ORMs VS. JDBC
- Spring VS. JakartaEE
PSA: All of them are pointless. Save your time. Go ahead and work on stuff you consider important instead.
Does anyone know how you can turn off chunked transfer encoding in #vertx 4.1.2 WebClient? It’s causing issues for one IBM product which apparently doesn’t support it. In Vert.x 3.8.x the same exact WebClient call didn’t use chunked transfer encoding.
I'm really trying to like @Dynatrace but it's just not working well with @vertx_project & OpenTelemetry. Traces look like this with no info and it's not propagated to the receiving service via Vert.x WebClient. OpenTracing is even worse and that worked perfectly with @datadoghq
MTLS & payload signing with caller IP limitation make it already quite hard to exploit but that should never be an excuse for not writing secure code.
It’s always nice to hear from security auditor they couldn’t find any holes in your API but it makes me always suspicious when there isn’t a single finding. Thanks to all the stuff I learned while working with @topolik we were able to plug the attack surface xml & SOAP brings.
@mtaivai Not having proper constraints and well defined errors in the REST APIs is bad but with OpenAPI you can describe those to certain extent but if you do any generated client will probably be crap.
In the year 2020 who in their right mind still uses SOAP web services for a brand new API. It’s of course for the govenment bank data API. Despite the horrible API we managed to implement it with Vert.x and minimal SOAP dependencies while leveraging work we did for our REST APIs.