springdoc-openapi
Flyway
Our great sponsors
springdoc-openapi | Flyway | |
---|---|---|
18 | 80 | |
3,086 | 7,763 | |
2.3% | 1.0% | |
8.9 | 7.2 | |
3 days ago | 3 days ago | |
Java | Java | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
springdoc-openapi
-
Creation and Usage of BOM in Gradle
The issue is that the springdoc-openapi BOM brings an old version of the Spring Framework 6.0, which is incompatible with Spring Boot 3.2. There are several ways to solve this problem: update springdoc, change the order of BOM imports, but the best, in my opinion, is to avoid using the io.spring.dependency-management plugin.
-
Setting up swagger
I would suggest using Springdoc
- How to deal with toxicity within the community, in context of big open source projects?
-
Spring Boot – Black Box Testing
The SpringDoc library comes with lots of annotations to tune your REST API specification precisely. Anyway, that's out of context of this article.
-
What do you think about generating OpenAPI specs from code?
I found SpringDoc, a library that automates the generation of the spec from the source code. It relies on annotations for textual bits (like tags and descriptions), but it also infers stuff from Spring annotations.
-
Removies
This is an API made with Spring Web, uses springdoc-openapi-ui to expose a swagger-ui on http://localhost:8080/swagger-ui/index.html
-
Pulling out OpenAPI 3.0 Specifications from SpringBoot
Libraries like Springdoc or Springfox can do this. These libraries generate the OpenAPI documentation based on your controllers (+ you can apply the OpenAPI annotations on your controllers). This documentation is then exposed as a REST API, for Springdoc these can be found at /v3/api-docs.
-
Eureka Service Registration and Discovery
Retrieving all endpoints of a service isn't the goal of a service registry like Eureka, so no, you can't get all endpoints of a service. You can use a library like Springfox or Springdoc to enable Swagger/OpenAPI for your project. These libraries generate a JSON REST API (and a user interface) to view all your endpoints. You can even provide additional information (eg. default values, descriptions, ...) by adding some additional annotations on your controllers.
-
OpenAPI Specification: The Complete Guide
The springdoc-openapi helps automating the generation of API documentation using Spring Boot projects GitHub - springdoc/springdoc-openapi
-
Java Spring EventSourcing and CQRS Clean Architecture microservice 👋⚡️💫
Our microservice accept http requests: For swagger used Swagger OpenAPI 3. The bank account REST controller, which accept requests, validate it using Hibernate Validator, then call command or query service. The main reason for CQRS gaining popularity is the ability to handle reads and writes separately due to severe differences in optimization techniques for those much more distinct operations.
Flyway
-
Ask HN: What tool(s) do you use to code review and deploy SQL scripts?
Also RedGate, but Flyway has some reasons to recommend it over RedGate Deploy depending on your DBAs/workflows: https://flywaydb.org/
(Though I don't think it is "complete" or "perfect", either.)
EF Migrations are in a really good place now if you like/don't mind C# as a language (and you can easily embed SQL inside the C#, too, but there are benefits to being able to also run high level C# code). With today's tooling you can package your migration "runner application" as a single deployable executable for most platforms. You can build the executable once and run it in all your environments. (The same tool that updates your QA and Staging updates your Prod, testably running the same migrations.) Given the single executable deployable I might even consider using it for projects not themselves written in C#.
-
PostgreSQL Is Enough
There is a bit of tooling needed but is already around. For Java for example I had very good experience with a combination of flyway [1] for migrations, testcontainers [2] for making integration tests as easy as unit tests and querydsl [3] for a query and mapping layer.
[1] https://github.com/flyway/flyway
[2] https://java.testcontainers.org/modules/databases/postgres/
[3] https://github.com/querydsl/querydsl
-
Using Flyway to version your database
When software starts using a database, it's advisable to have version control, just as we have Github to control our source code. This is all to be sure about what was executed for that specific version. For Java and Spring boot, we have the Flyway framework that aims to resolve this situation, free of charge.
-
CI/CD for Databricks
If you're looking for tools, like https://www.liquibase.com/ or https://flywaydb.org/, which are database-state-based schema migration toolkits - it might be relatively straightforward to build similar ones using Databricks SQL drivers.
-
Working with jOOQ and Flyway using Testcontainers
Honestly I kind of wish there was a Lukas Eder database migration library. Call it whatever jooq-migration. At least I would have more insight of what is going on (<-- seriously look at the commit history).
-
Strategy to run database scripts on Kubernetes
This is a 4th option, which should play nice with ArgoCD. The following example runs flyway as a k8s job. The desired migration changes are recorded as files within the chart. This helm chart can be integrated with your application (Using hooks to determine when the migration job is run) or run manually.
-
How do your teams run DB migrations?
By using an opinionated framework within the app/service (like Flyway, Migrate, Diesel, etc). Schema migrations happen on app/service start-up.
-
I've never created a production database from scratch and am wondering how much trouble it would be to transition a one-to-one relationship to a one-to-many relationship if I determine at some point that the latter is required.
Depending on the language or platform there are libraries you can use to manage this, such as Prisma on node and Flyway for Java/JVM.
-
How should I document and/or automate schema changes?
It's probably overkill but I've used github plus flyway at a couple places in the past which is pretty nice tool for tracking changes to a variety of db's, it's also very helpful if you ever need to replicate a db in a new region/environment.
-
Version control for database used by C# app
Flyway
What are some alternatives?
springfox - Automated JSON API documentation for API's built with Spring
alembic - A database migrations tool for SQLAlchemy.
swagger-core - Examples and server integrations for generating the Swagger API Specification, which enables easy access to your REST API
HikariCP - 光 HikariCP・A solid, high-performance, JDBC connection pool at last.
javalin - A simple and modern Java and Kotlin web framework [Moved to: https://github.com/javalin/javalin]
roundhouse - RoundhousE is a Database Migration Utility for .NET using sql files and versioning based on source control
hibernate-validator - Hibernate Validator - Jakarta Bean Validation Reference Implementation
H2 - H2 is an embeddable RDBMS written in Java.
Elide - Elide is a Java library that lets you stand up a GraphQL/JSON-API web service with minimal effort.
dbmate - :rocket: A lightweight, framework-agnostic database migration tool.
openapi-generator - OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3)
Hibernate - Hibernate's core Object/Relational Mapping functionality