H

Hexagonal Architecture

Java-based microservice template built with Spring Boot, following Hexagonal Architecture (Ports and Adapters). Provides a modular REST API suitable for creating scalable, maintainable, and testable services.

Sistema modular y orientado a eventos para gestionar artistas, usuarios, conciertos, reservas con caducidad y pagos mediante Stripe o un emulador local. Construido con Java 25, Spring Boot 4.0.6, Spring Cloud, Kafka y PostgreSQL, siguiendo DDD y Arquitectura Hexagonal. Incluye seguridad OAuth2/JWT y notificaciones en tiempo real mediante SSE.

Modular, event-driven system for managing artists, users, concerts, expiring reservations, and payments through Stripe or a local emulator. Built with Java 25, Spring Boot 4.0.6, Spring Cloud, Kafka, and PostgreSQL, following DDD and Hexagonal Architecture. Includes OAuth2/JWT security and real-time notifications via SSE.

Modular monolith that exposes a GraphQL API and REST API. It is created with C# and .NET, EF, Hexagonal Architecture, Vertical Slicing, Screaming Architecture, Specification Pattern, Unit Of Work Pattern, Repository Pattern, CQRS, DDD, OIDC with Casdoor, IaC with Pulumi, Oceanbase (HTAP Database), Nats broker, Opentelemetry and docker for the development environment.

This is a back-end, Spring Boot project, hexagonal architecture based, that tries to show my own skills and knowledge level, designing and implementing Java applications by the Spring Framework.

Un kata pour tester les compétences et les bonnes pratiques d'architecture logicielle

-> Contenu -Un seul topic order-events sur lequel sont publiés trois types d’événements : OrderCreated, PaymentValidated, OrderShipped. -Producer (REST API) : publie les événements ; Consumer : écoute le topic avec trois consumer groups (groupIds distincts) et délègue au domaine via des handlers. -Architecture : hexagonale + template method ; contrats partagés dans le module kafka-contracts (OpenAPI). -> Stack: -Java 21, Spring Boot 3.2, Spring Kafka -Kafka (Zookeeper), Kafka UI -Maven multi-module : kafka-contracts, order-event-producer, order-event-consumer -Docker / Docker Compose pour l’infra et les apps -CI/CD GitLab : build Maven, tests unitaires, build & push des images sur Docker Hub, déploiement par SSH + docker compose sur le serveur. -> Dépôts d’images -Images poussées sur Docker Hub par la CI : kafka-kata-producer, kafka-kata-consumer.

This project is used as an example for this blog post → https://zestedesavoir.com/billets/4991/parlons-darchitecture-hexagonale/

E-commerce backend built with Java 17 + Spring Boot 3, Clean Architecture, Kafka, Elasticsearch, MySQL, JWT auth and observability (Filebeat + Elasticsearch).

An concurrency app that generate ticket number sequentially

any message received will be echoed as a websocket message

Hexagonal Architecture vs Onion Architecture vs Clean Architecture vs Layered Architecture vs Component-Based Architecture