• CptOfEvilMinions

    CptOfEvilMinions

    10 months ago
    Question about Fleet's new feature to support MySQL read replicas. Can I spin up Fleet in a different region that only has access to a read-only database replica? Example architecture below for context:
    AWS Ohio region:
    - Fleet instances
    - Aurora MySQL read/write
    - Redis
    
    AWS London:
    - Fleet instances
    - Aurora MySQL read-only replica
    - Redis
  • Jocelyn Bothe

    Jocelyn Bothe

    10 months ago
    yup, that's the way we do it
  • CptOfEvilMinions

    CptOfEvilMinions

    10 months ago
    Excellent, thank you @Jocelyn Bothe
  • Jocelyn Bothe

    Jocelyn Bothe

    10 months ago
    we have our writer in us-west-1 and then 5 readers each in us-east-1 and us-west-2
  • (using aurora global cluster)
  • CptOfEvilMinions

    CptOfEvilMinions

    10 months ago
    @Jocelyn Bothe same question but with Elasticache, specifically Redis.
  • Jocelyn Bothe

    Jocelyn Bothe

    10 months ago
    we use redis global with primary in us-west-2 and the secondary in us-east-1, but that's just for redundancy, there's no read replica config for redis
  • (unless you do it yourself, using stunnel)
  • zwass

    zwass

    10 months ago
    The operation of a Fleet server that has access to only a read replica is going to be very limited. For example, hosts are not going to be able to write updates and users will only be able to continue using existing sessions, not logging in for new ones. I think what @Jocelyn Bothe is describing is writer/readers in different regions, but not Fleet servers attached in different regions as described in the original comment.
  • It's going to be similar with Redis -- it's fine for copies of data to be across different regions with clustering, but Fleet servers with no access to a writer will have very limited functionality.
  • Jocelyn Bothe

    Jocelyn Bothe

    10 months ago
    ah yes, every region is talking to the same writer