Hi @Ankita-0970 , thanks for your patience. Please refer to below reply for your query from product group.
If front door meets your needs (only caches for GET requests, one of the query string behaviors fits your needs, then you don’t need extra control over expiration, etc. Caching with Azure Front Door) then it is probably a better fit for use case and provides some benefits that would take extra work to replicate with Azure Cache for Redis such as being a ‘global’ resource, caching at the edge, and reducing the number of requests made to their servers.
If you need to cache for other types of requests, want to be able to scale out servers, or have an application running on servers that would benefit from being able to cache arbitrary data inside of a region or set of regions with extra control over the data then Redis would be a good fit.
Also they aren’t mutually exclusive, AFD could be used to cache GET requests and reduce overall requests to the backend while Redis improves the performance of requests that do get forwarded as long as we can understand how both are working at the same time (eg a response expiring in Redis doesn’t mean that it expires in AFD)
Please let us know if this helps.
If answer helps, you can mark it 'Accept Answer'