Skip to content
vertyllPublic

Repository files navigation

FastProd

Project Assumptions

Production management application.

Technology Stack

Back-end

  • Spring Boot.
  • Java.
  • Gradle Kotlin DSL.
  • JDBC.
  • JPA.
  • Hibernate.
  • PostgreSQL.
  • JUnit.
  • Mockito.
  • Lombok.
  • Spring Security.
  • Spring Data.
  • Spring Web.
  • Keycloak.
  • Flyway.
  • OpenAPI (Swagger).

Front-end

  • Vaadin (Java-only – Flow).
  • Spring Boot.
  • Java.
  • Gradle Kotlin DSL.
  • JUnit.
  • Mockito.
  • Lombok.
  • Spring Web.

Authentication

  • Identity provider: Keycloak (realm fastprod); the application never sees a password.
  • Pattern: BFF; the Vaadin front-end keeps the tokens, the browser holds only a session cookie.
  • JWT: the back-end is a stateless resource server; roles come from the token.
  • Accounts: mirrored into PostgreSQL; employees are created by an admin through Keycloak.
  • Details: Authentication.

Core back-end

  • Gradle multi-module build system.
  • The application has an exception handling mechanism.
  • The application has a logging mechanism.
  • The application has separate environments for local and prod.
  • The application has a dedicated configuration file.
  • The application has RBAC (Role Based Access Control).
  • The application has an audit mechanism (who and when modified data).
  • The application has Flyway database migration mechanism.
  • And many other features that can be found in the application code.

Core front-end

  • Gradle build system.
  • Vaadin.
  • The application has separate environments for local and prod.
  • The application has a dedicated configuration file.
  • And many other features that can be found in the application code.

Other

  • Docker for development environment.
  • PMD for static code analysis.
  • SpotBugs for static code analysis.
  • JSpecify for null-safety annotations.
  • NullAway for null-safety checks.
  • Error Prone for static code analysis.
  • Spotless for code formatting.

Documentation

  • Contents – every document in the repository, the module it belongs to, and what it covers.
  • Glossary – every term the docs use, and where it is explained.
  • Standards – the RFCs and specifications the code implements or depends on.

Preview Screenshots

Project View Project View Project View Project View

Releases

Packages

Used by

Contributors

Languages