feat: add redis cache to transaction summary endpoint - #2
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
1 participant
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.
Adiciona cache Redis ao endpoint de resumo financeiro.
O que esse PR implementa
RedisConfig— configura RedisCacheManager com TTL de 5 minutos e serialização JSONTransactionSummary— DTO com totalIncome, totalExpense, balance e monthGET /transactions/summary— endpoint novo que agrega transações do mês@Cacheableno getSummary() — resultado cacheado no Redis por 5 minutos@CacheEvictno save() — cache invalidado automaticamente ao criar nova transaçãoComo funciona
Primera requisição → consulta banco → salva no Redis
Requisições seguintes → retorna do Redis sem tocar no banco
Nova transação criada → cache invalidado → próxima requisição recalcula