Feature/backend infrastructure#3
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Descrição
Este Pull Request implementa a Camada de Infrastructure, fornecendo as implementações concretas (adaptadores) para as interfaces definidas no domínio.
Foram configurados:
Mudanças Realizadas
A implementação focou em transformar os modelos de domínio em entidades persistentes e integrar os serviços do ecossistema Quarkus:
1. Persistência de Dados (
persistence)PanacheEntity) para todos os contextos:RepositoryImpl) com Hibernate Panache2. Segurança e JWT (
security)3. Mensageria e Monitoramento (
messaging,monitoring)ContactMessagingAdapterintegrado ao Kafka4. Gestão de Exceções (
exceptions)5. Configurações (
resources,config)application.properties(suporte a variáveis de ambiente / K8s)application-development.propertiespara facilitar o setup localDecisões de Arquitetura
Database Mapping
Uso do padrão Repository para desacoplar entidades Panache da lógica de aplicação.
Segurança
Adoção de chaves PEM e PK8, seguindo boas práticas de criptografia.
Cloud Native
Configurações preparadas para execução em containers, com suporte à injeção de dependências do Quarkus (Arc).
✅ Checklist