- AWS Elasticache If the same read query is performed over and over again. AWS RDS Read Replica if the read query changes dynamically or has dynamic elements such as NOW().
- AWS Elasticache is speed is required, since data is stored in RAM.
- AWS Read Replicas is there is a low tolerance for stale data.
- AWS Read Replica if the data returned by a read query is huge since RAM is not unlimited.
AWS Application Load Balancer VS Network Load Balancer Distribution of Traffic: Application Load Balancer: Based on attributes of OSI Layer 7 (Application Layer). Network Load Balancer: Based on attributes of OSI Layer 4 (Transport Layer). Application Health Application Load Balancer: Since it works at the Application Layer of the OSI the health of the target application can be verified and the application health is taken into distribution decision. Network Load Balancer: Since it works at the Transport Later of the OSI level the health of the application can not be verified (it uses IP address , port etc). So it is possible that a request gets sent to a server even the the target application on that server is having some issues. Speed: Since Network Load Balancers work at a lower layer of the OSI they are faster then Application Load Balancers. More than one different application on the same server Since Network Load Balancers use IP address to distribute requ...
thanks for sharing..........................!
ReplyDeleteAzure DevOps online training
Azure online training
Chef online training
Data Guard online training
Data Modelling online training
Data Science online training
DevOps online training