My straigh question is: can I rely on vertx-mysql-client as a database reactive driver? I have used Spring-data-Reactive based on R2DBC and I believe I have done a good decision so far but this time Spring-Data isn't an option.
It is my first contact with VERTX. I am looking for some reasonable way to code a reactive database client. I have coded few applications using Spring-Data and it was very straighforward. Now our directive is a stack that is based on Micronaut and we want to avoid Spring (nothing against Spring but it was decided to avoid reflection and take advantage of Micronaut AOT feature).
I am far away to be an expert in reactive paradgmas but I am convinced that, when designing a reactive solution, it must be reactive from begin to end. I mean, we must avoid mixing blocking code (ex. jdbc) with reactive (ex. Webflux) otherwise we lost the pros of the effort to code a reactive solution.
So, I am developing a a Kafka Consumer based on Micronaut and it is aimed to save reactivelly to a database (the database itself doesn't matter for this question. I believe NOSQLs are better than RELATIONALs for a reactive stack but let me leave this for other discussion). It is fine for my question be answer with either MySql or PostGres in mind.