i'm creating simple web app needs deployed multiple regions in aws. application requires dynamic configuration managed separate service. when configuration changed through service, need changes propagate web app instances across regions.
i considered using cross-region replication dynamodb this, not want incur added cost of running dynamodb in every region, , replication console. thought occurred me of using s3 inherently cross-region.
basically, configuration service write configurations s3 static json files. each web app instance periodically check s3 see if of config files have changed since last check, , download new config if necessary. configuration changes not time-sensitive, polling changes every 5/10 mins should suffice.
have of used similar approach manage app configurations before? think smart solution, or have better recommendations?
the right tool configuration depends on size of configuration , granularity need it.
you can use both dynamodb , s3 single region serve application in regions. can read configuration file in s3 regions, , can read configuration records single dynamodb table regions. there latency due distance around globe, reading configuration shouldn't of issue.
if need whole set of configuration every time loading configuration, might make more sense use s3. if need read small parts of large configuration, different parts of application , in different times , schedule, makes more sense store in dynamodb.
in both options, cost of configuration tiny, cost of text file in s3 , few gets file, should free. same low cost expected in dynamodb have few kb of data , number of reads per second low (5 read capacity per second more enough). if decide replicate data regions still free.
Comments
Post a Comment