Escolar Documentos
Profissional Documentos
Cultura Documentos
SSL can be used to provide HTTPS. Can either use CloudFronts own
certificate or use your own
Alias records can then have evaluate target set to yes so that
existing health checks are used to ensure the underlying resources are
up before sending traffic onwards. If a health check for the underlying
resource does not exist, evaluate target settings have no effect
Device detection can serve different content based on the User Agent
string in the header request
for a marketing e-mail and signed cookies for web site streaming or
whole site authentication
Set a low TTL for dynamic content as most content can be cached
even if its only for a few seconds. CloudFront can also present stale
data if TTL is long
Popular Objects report and cache statistics can help you tune
CloudFront behaviour
Only forward cookies that are used to vary or tailor user based
content
Only Redis is multi-AZ and has backup and restore and persistence
capabilities, sorting, publisher/subscriber, failover
Redis has backup and restore and automatic failover and is best used
for frequently changing data in a complex scale
Redis can be configured to use an Append Only File (AOF) that will
repopulate the cache in case all nodes are lost and cache is cleared.
This is disabled by default. AOF is like a replay log
Redis has a primary node and read only nodes. If the primary fails, a
read only node is promoted to primary. Writes done to primary node,
reads done from read replicas (asynchronous replication)
Redis snapshots are used to increase the size of nodes. This is not
the same as EC2 snapshots, the snapshot creates a new node based
on the snapshot and size is picked when launching
Memcached uses lazy loading, so if an app doesnt get a hit from the
cache, it requests it from the DB and then puts that into cache. Write
through updates the cache when the database is updated
TTL can be used to expire out stale or unread data from the cache
Memcache nodes are empty when first provisioned, bear this in mind
when scaling out as this will affect cache performance while the nodes
warm up
Are you looking for more advanced data types, such as lists,
hashes, and sets? If so, use Redis.
Do you want to run in multiple AWS Availability Zones (MultiAZ) with failover? If so, use Redis.
Amazon Kinesis is a managed service that scales elastically for realtime processing of streaming data at a massive scale. The service
collects large streams of data records that can then be consumed in real
time by multiple data-processing applications that can be run on Amazon
EC2 instances.
You can use Streams for rapid and continuous data intake and
aggregation. The type of data used includes IT infrastructure log data,
application logs, social media, market data feeds, and web clickstream
data. Because the response time for the data intake and processing is in
real time, the processing is typically lightweight
Sequence number
Partition key
Data BLOB
Producers put records into Amazon Kinesis Streams. For example, a
web server sending log data to a stream is a producer
There are two different operations in the Streams API that add data to
a stream, PutRecords and PutRecord. The PutRecords operation sends
multiple records to your stream per HTTP request, and the singular
PutRecord operation sends records to your stream one at a time (a
separate HTTP request is required for each record). You should prefer
using PutRecords for most applications because it will achieve higher
throughput per data producer
Distributed workloads
custom settings. Pipelines can only have one source and one
destination bucket