Feature/backend application#2
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 Application, responsável pela orquestração da lógica de negócio.
Foram criados:
Mudanças Realizadas
A camada foi estruturada para suportar todas as funcionalidades do portfólio e do painel administrativo:
1. Autenticação e Usuários (
auth,users)LoginUseCasepara validação de credenciais2. Gestão de Estatísticas (
stats)3. Gestão de Tecnologias (
stacks)4. Conteúdo Dinâmico (
contents)5. Portfólio Core (
projects,experiences,educations)6. Mensageria (
messages)Decisões de Arquitetura
Desacoplamento
Os casos de uso dependem apenas de interfaces (abstrações) definidas no domínio, sem conhecimento de implementações específicas (ex: Panache, Kafka).
Imutabilidade
Uso de DTOs para evitar exposição direta do estado interno do domínio.
Single Responsibility Principle (SRP)
Cada Use Case é responsável por uma única ação de negócio.
✅ Checklist