Please enable JavaScript.
Coggle requires JavaScript to display documents.
M10 caching (cloudfront (webscocket (it is long-held TCP connection. By…
M10 caching
cloudfront
-
cloudfront expire slide
- change object name by applying version ?
immediate refresh
Versioning enables you to control which file a request returns even when the user has a version cached either locally or behind a corporate caching proxy.
CloudFront access logs include the names of your files, so versioning makes it easier to analyze the results of file changes.
-
-
Versioning is less expensive. You still have to pay for CloudFront to transfer new versions of your files to edge locations, but you don't have to pay for invalidating files.
Don't have to wait for an object to expire before CloudFront begins to serve a new version of it,
-
invalidate the object
If you invalidate the file, the user might continue to see the old version until it expires from those caches.
-
security PT ?
CloudFront integrates seamlessly with AWS Shield for Layer 3/4 DDoS mitigation and AWS WAF for Layer 7 protection. In addition,
CloudFront negotiates TLS connections with the highest security ciphers, and authenticates viewers with signed URLs.
You can also use our advanced feature Field-Level Encryption to protect most sensitive data throughout your enterprise, so the information can only be viewed by certain components and services
in your application stack. CloudFront also integrates with AWS Identity and Access Management (IAM) to control access, with AWS CloudTrail to log access to your configuration, and with Amazon Certificate Manager (ACM) for automated certificate renewals.
-
-
webscocket
it is long-held TCP connection. By using a persistent open connection, the client and the server can send real-time data to each other without the client having to frequently reinitiate connections checking for new data to exchange.
bi-directional, on by default and no need ot pay
WebSocket connections are often used in chat applications, collaboration platforms, multiplayer games, and financial trading platforms.
generic concept
-
-
-
client side caching ?
cache in browser. ex: html pages, and image
-
reverse proxy cache ?
can be placed in front of client and web servers in order to serve a cached version of the HTTP responses
-
-
-
server side caching
Types of server caching include, but aren’t limited to:
Object caching – Storing database queries in a server-side cache for quick retrieval on subsequent page loads.
CDN caching – A Content Delivery Network (CDN) is a cluster of servers that are geographically located all around the world. They cache content that’s loaded using the server that’s closest to the end user for much faster loading times
-
-
-
-
2 type
Memcache
-
-
-
Mitigating Node failure
-
as Memcached does not support replication, a node failure will always result in some data loss from the cluster
-
memcache and redi slide
comparison
-
Not support Multi AZ
Allocate the nodes in as many availability zones as possible, only the data cached in that AZ is lost, not the data cached in the other
-
Memcache no persistent
-
Mitigating Node failure
-
as Memcached does not support replication, a node failure will always result in some data loss from the cluster
-
redis can persistent
Backup and Restore allows users to create snapshots of the Redis clusters
Snapshots can be used for recovery, restoration, archiving purpose or warm start an ElastiCache for Redis cluster
-
pub/sub
-
knowing who, if anyone, receives it. Recipients of the message are those who are subscribed to the channels
-
-
-
both support broad set of programming language for their clients: C++, phython, Java script, PHP
-
Advanced data type
In addition to strings, Redis supports lists, sets, sorted sets, hashes, bit arrays, and hyperloglog
-
Redis
-
feature
support primary DB, read replica, Multi-AZ
-
-
-
-