We were promised that microservices would make our software more stable and easier to scale horizontally. But the added complexity often creates a lot of shared code and complex infrastructure. Dapr promises a solution by placing these cross-cutting concerns outside your code.
Writing JPQL queries can be annoying, because you cannot test them in a database tool or in your IDE. But with IntelliJ Ultimate, you can!
There are a lot of how-tos on how to use OpenAPI to document the REST APIs of a Quarkus microservice. However, none of them show you how to document the schema of your API response.
In this blog post I’ll show you two ways to add schema documentation to your OpenAPI spec.
Spring REST docs and Swagger are great ways to document your API, but both have their strong and weak points. I prefer the test-driven way of documenting an API of Spring REST docs over the "Magic and Annotations" approach of Swagger, but on the other hand the output of Spring REST docs just doesn’t look as nice as the interactive UI of Swagger. Wouldn’t it be nice if we could combine both frameworks to create the most awesome API docs ever?
