Please enable JavaScript.

Coggle requires JavaScript to display documents.

Microsoft Cloud Design Patterns - Coggle Diagram

- - - - when read from cache it loads the data into it
      - When write, write it to cache and it update the cache and underlying datastore
    - - Lifetime
      - Evict data when it oversize
      - Priming or prepopulating the cache during startup
      - Consistency
        
        Data in the cache may not be consistence with the data store
      - Local (in-memory) caching
- - - - Resize env basing on usage on dev and prod
    - - Availability
        
        measure when users can access the system
      - Resilency
        
        How fast the system can recover
      - How to implement
        
        Retry pattern
        
        Most Azure service has built in retry pattern
        
        Polly
        
        Circut Breaker pattern
    - - Managed identities via Microsoft Entra ID
      - use central secret store
      - use private endpoints
      - use firewall
  - - - 99.9% for availability
      - 8.7 hours of downtime per year
  - - - to host web apps and RES APIS
    - - for identity, authentication and authorization
    - - for APM (application perforamnce management) and monitring
    - - to cache the data
    - - Load balancer
    - - to store secret keys
    - - Blob storage
    - - To access private services like Azure Cache for Redis or SQL Database