Tutorial release: how to create a complete Vert.x web application with OpenAPI, PostgreSQL & Redis

[Francesco Guardiani]

Hello to everybody!

I'm publishing on my blog a tutorial step by step on how to create a complete Vert.x application. For the REST API part I'm going to use vertx-web, vertx-web-api-contract and the shiny new vertx-web-api-service. For the DB Access I'm going to use vertx-redis and reactive-pg-client from reactiverse.

Here is the introduction post: https://slinkydeveloper.github.io/Debts-Manager-Tutorial-Introduction/

And the first post, Contract design: https://slinkydeveloper.github.io/Debts-Manager-Tutorial-Contract-Design/

Note that for me this is an experiment, I'm not a professional blogger. If you want to give me any feedback just open an issue on GH blog repo :) https://github.com/slinkydeveloper/slinkydeveloper.github.io

Francesco

[Sam]

Great initiative!!

I would be happy if the tutorial series also focuses on performance improvement. Benchmarking kind of experiments.👍

[Francesco Guardiani]

Thank you! For now I want to complete all the posts i planned, maybe in future I can add a post using wrk2, like i did in this experiment: https://github.com/slinkydeveloper/json-validator-http-tests

[Francesco Guardiani]

Hi, I just published the next chapter of the series: https://slinkydeveloper.com/Debts-Manager-Tutorial-Vert-x-Web-API-Contract-Service/

The aim of this chapter is to show you Vert.x Web, Vert.x Web API Contract and Vert.x Web API Service. The combination of these three packages provides all functionalities you need to create a REST API. Then I’m going to use pmlopes’ vertx-starter to scaffold the project.

Let me know for any feedback!

Francesco

[apat...@redhat.com]

Great work.

I really think OpenAPI + Web API contract|service is an incredibly powerful combo.

Btw, any reason why why Web API contract|service are not called OpenAPI contract|service, I think this brings some confusion.

I didn't know about: https://vertx-starter.jetdrone.xyz/#maven

This is the sort of fancy stuff that can boost user adoption.

[Francesco Guardiani]

Btw, any reason why why Web API contract|service are not called OpenAPI contract|service, I think this brings some confusion.

Because my initial idea was to support in the same package with mostly same logic all old api specs: RAML, Swagger 2, ... Then OpenAPI 3 came out and these specs disapperead. I'm planning to hugely refactor web api contract for 4.0, so maybe a name change  could be interesting :)

 

I didn't know about: https://vertx-starter.jetdrone.xyz/#maven

This is the sort of fancy stuff that can boost user adoption.

If you are interested there was a discussion about it at last F2F: https://groups.google.com/forum/#!topic/vertx-dev/jiViJXz93XU