aws-samples / aws-samples/java-spring-boot-ecs-fargate-redis-caching

Redis on Fargate vs ElastiCache

Open
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
8
Forks
10
PR merge metrics
No merged PRs in 30d

Description

Could you provide some explanation on the differences in running Redis on Fargate as in this example, or using the same Spring Boot application with ElastiCache (AWS-managed Redis)? Is there any documentation on this, or articles discussing the benefits and tradeoffs?

Actually I'm a bit confused whether this example is showing running Redis in Fargate or via ElastiCache. There is a CloudFormation template for ElastiCache, but the `fargate_metadata.json` seems to refer to Redis as a Fargate image.

Could you give an explanation on which approach this example uses to access Redis, and what factors should be considered when choosing between Redis on Fargate vs ElastiCache?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the CloudFormation template for ElastiCache with fargate_metadata.json, which appears to refer to Redis as a Fargate image. Trace how the Spring Boot application accesses Redis in this example. Done means the documentation clearly identifies the deployed approach and explains the relevant benefits and tradeoffs of Fargate-hosted Redis versus ElastiCache.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, java, redis, spring-boot
Domain
backend, cloud, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.