{"id":398,"date":"2025-06-24T06:38:52","date_gmt":"2025-06-24T06:38:52","guid":{"rendered":"https:\/\/sreschool.com\/blog\/?p=398"},"modified":"2026-05-05T07:29:44","modified_gmt":"2026-05-05T07:29:44","slug":"dns-failover-in-devsecops","status":"publish","type":"post","link":"https:\/\/sreschool.com\/blog\/dns-failover-in-devsecops\/","title":{"rendered":"DNS Failover in DevSecOps"},"content":{"rendered":"\n

Introduction & Overview<\/strong><\/h1>\n\n\n\n

What is DNS Failover?<\/h3>\n\n\n\n

DNS Failover<\/strong> is a high-availability mechanism that automatically redirects traffic to a standby server or resource if the primary resource becomes unavailable. It leverages Domain Name System (DNS)<\/strong> records with health checks to dynamically shift traffic from unhealthy endpoints to healthy backups.<\/p>\n\n\n\n

History & Background<\/h3>\n\n\n\n
    \n
  • The Domain Name System (DNS)<\/strong>, developed in 1983, was originally designed as a decentralized naming system for devices.<\/li>\n\n\n\n
  • With the growth of internet traffic, availability and resilience became critical. DNS Failover emerged as a strategy to ensure services remained reachable despite outages.<\/li>\n\n\n\n
  • Cloud platforms like AWS Route 53<\/strong>, Azure Traffic Manager<\/strong>, and Cloudflare Load Balancer<\/strong> now provide managed DNS Failover as part of their offerings.<\/li>\n<\/ul>\n\n\n\n

    Why is it Relevant in DevSecOps?<\/h3>\n\n\n\n
      \n
    • DevSecOps<\/strong> integrates security, development, and operations seamlessly.<\/li>\n\n\n\n
    • DNS Failover contributes to resiliency<\/strong>, availability<\/strong>, and incident response<\/strong>\u2014critical pillars of DevSecOps.<\/li>\n\n\n\n
    • It enables secure failover<\/strong> strategies with monitoring, observability, and automation built in.<\/li>\n<\/ul>\n\n\n\n
      \n\n\n\n

      Core Concepts & Terminology<\/strong><\/h2>\n\n\n\n

      Key Terms & Definitions<\/h3>\n\n\n\n
      Term<\/th>Description<\/th><\/tr><\/thead>
      DNS Record<\/strong><\/td>A mapping of a domain to IP addresses or services (A, AAAA, CNAME, etc.).<\/td><\/tr>
      Health Check<\/strong><\/td>A mechanism to monitor the status of a server or service.<\/td><\/tr>
      TTL (Time to Live)<\/strong><\/td>Duration a DNS response is cached before rechecking.<\/td><\/tr>
      Failover Pool<\/strong><\/td>A group of endpoints (primary and backup) for failover.<\/td><\/tr>
      Latency Routing<\/strong><\/td>Directs users to the lowest-latency region\/server.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

      Fit in the DevSecOps Lifecycle<\/h3>\n\n\n\n
      DevSecOps Phase<\/th>DNS Failover Role<\/th><\/tr><\/thead>
      Plan<\/strong><\/td>Define availability and recovery SLAs.<\/td><\/tr>
      Develop<\/strong><\/td>Integrate failover logic in code-based infrastructure.<\/td><\/tr>
      Build\/Test<\/strong><\/td>Automate testing of DNS changes and failover behavior.<\/td><\/tr>
      Release<\/strong><\/td>DNS routing integrated into release pipelines.<\/td><\/tr>
      Operate<\/strong><\/td>Continuous monitoring and failover for HA.<\/td><\/tr>
      Monitor<\/strong><\/td>Alerting on service failure and DNS state.<\/td><\/tr>
      Secure<\/strong><\/td>Ensure DNS failover cannot be hijacked or spoofed.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      \n\n\n\n

      Architecture & How It Works<\/strong><\/h2>\n\n\n\n

      Components<\/h3>\n\n\n\n
        \n
      • Primary DNS Endpoint<\/strong>: Main application server or API endpoint.<\/li>\n\n\n\n
      • Secondary (Failover) Endpoint<\/strong>: Backup server or region to handle traffic in failures.<\/li>\n\n\n\n
      • Health Checker<\/strong>: Monitors the status of endpoints (HTTP, TCP, etc.).<\/li>\n\n\n\n
      • Failover Controller<\/strong>: Logic that updates DNS records upon failures.<\/li>\n\n\n\n
      • DNS Resolver<\/strong>: Handles DNS queries and caches results.<\/li>\n<\/ul>\n\n\n\n

        Internal Workflow<\/h3>\n\n\n\n
          \n
        1. DNS Record with Health Checks<\/strong> is created pointing to the primary IP.<\/li>\n\n\n\n
        2. Health Checker<\/strong> pings the service at regular intervals.<\/li>\n\n\n\n
        3. If the primary endpoint fails, the Failover Controller<\/strong> updates the DNS record.<\/li>\n\n\n\n
        4. DNS queries are now resolved to the secondary endpoint<\/strong>.<\/li>\n\n\n\n
        5. When the primary is restored, the record is updated again.<\/li>\n<\/ol>\n\n\n\n

          Architecture Diagram (Textual)<\/h3>\n\n\n\n
                          \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510\n                \u2502   DNS Provider     \u2502\n                \u2502 (e.g. Route 53)    \u2502\n                \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u252c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518\n                         \u2502\n              \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u25bc\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510\n              \u2502   Health Checker   \u2502\n              \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u252c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518\n                         \u2502\n        \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u25bc\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510\n        \u2502 Failover Controller (API\/CDN)\u2502\n        \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u252c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u252c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518\n                   \u2502          \u2502\n         \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u25bc\u2500\u2500\u2510    \u250c\u2500\u2500\u25bc\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510\n         \u2502 Primary App\u2502    \u2502 Secondary App\u2502\n         \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518    \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518\n<\/code><\/pre>\n\n\n\n
          Integration Points<\/h3>\n\n\n\n
            \n
          • CI\/CD Pipelines<\/strong>:\n
              \n
            • Terraform\/Ansible to automate DNS configurations.<\/li>\n\n\n\n
            • Validate failover configurations using test environments.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
            • Cloud Providers<\/strong>:\n
                \n
              • AWS Route 53<\/strong>, Azure Traffic Manager<\/strong>, Google Cloud DNS<\/strong> support native failover.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
              • Monitoring Tools<\/strong>:\n
                  \n
                • Prometheus, Datadog, or ELK Stack for health monitoring and DNS alerts.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
                  \n\n\n\n
                  Installation & Getting Started<\/strong><\/h2>\n\n\n\n
                  Prerequisites<\/h3>\n\n\n\n
                    \n
                  • Registered domain name.<\/li>\n\n\n\n
                  • DNS service that supports health checks and failover (e.g., AWS Route 53).<\/li>\n\n\n\n
                  • At least two endpoints: primary and backup.<\/li>\n\n\n\n
                  • Basic CLI or API knowledge (e.g., AWS CLI).<\/li>\n<\/ul>\n\n\n\n
                    Step-by-Step Guide with AWS Route 53<\/h3>\n\n\n\n
                    1. Create Hosted Zone<\/h4>\n\n\n\n
                    aws route53 create-hosted-zone --name example.com --caller-reference 12345\n<\/code><\/pre>\n\n\n\n
                    2. Set Up Health Check<\/h4>\n\n\n\n
                    aws route53 create-health-check --caller-reference \"check123\" \\\n  --health-check-config '{\n    \"IPAddress\": \"1.2.3.4\",\n    \"Port\": 80,\n    \"Type\": \"HTTP\",\n    \"ResourcePath\": \"\/health\",\n    \"RequestInterval\": 30,\n    \"FailureThreshold\": 3\n  }'\n<\/code><\/pre>\n\n\n\n
                    3. Create DNS Failover Record<\/h4>\n\n\n\n
                    aws route53 change-resource-record-sets --hosted-zone-id ZONE_ID --change-batch '{\n  \"Changes\": [{\n    \"Action\": \"CREATE\",\n    \"ResourceRecordSet\": {\n      \"Name\": \"app.example.com\",\n      \"Type\": \"A\",\n      \"SetIdentifier\": \"Primary\",\n      \"Failover\": \"PRIMARY\",\n      \"TTL\": 60,\n      \"ResourceRecords\": [{\"Value\": \"1.2.3.4\"}],\n      \"HealthCheckId\": \"your-health-check-id\"\n    }\n  }]\n}'\n<\/code><\/pre>\n\n\n\n
                    4. Add Secondary Record (Failover)<\/h4>\n\n\n\n
                    # Change \"Failover\" to \"SECONDARY\" and update IP address.\n<\/code><\/pre>\n\n\n\n
                    \n\n\n\n
                    Real-World Use Cases<\/strong><\/h2>\n\n\n\n
                    1. E-commerce Platform Uptime<\/strong><\/h3>\n\n\n\n
                    A major online retailer configures DNS Failover across AWS (primary) and Azure (secondary) to ensure checkout availability during outages.<\/p>\n\n\n\n
                    2. Healthcare App Compliance<\/strong><\/h3>\n\n\n\n
                    Hospitals hosting patient portals use DNS Failover to ensure HIPAA-compliant failover to DR sites during emergencies.<\/p>\n\n\n\n
                    3. SaaS Incident Management<\/strong><\/h3>\n\n\n\n
                    A B2B SaaS provider uses DNS Failover integrated with PagerDuty to redirect users during regional downtimes.<\/p>\n\n\n\n
                    4. Banking & Fintech<\/strong><\/h3>\n\n\n\n
                    Banks configure DNS Failover to instantly redirect users to alternative infrastructure without downtime during peak hours or attacks.<\/p>\n\n\n\n
                    \n\n\n\n
                    Benefits & Limitations<\/strong><\/h2>\n\n\n\n
                    Key Advantages<\/h3>\n\n\n\n
                      \n
                    • High Availability<\/strong>: Redirect traffic seamlessly during failure.<\/li>\n\n\n\n
                    • Low Operational Cost<\/strong>: Minimal infrastructure overhead.<\/li>\n\n\n\n
                    • Cloud Agnostic<\/strong>: Works across multi-cloud deployments.<\/li>\n\n\n\n
                    • Security Add-on<\/strong>: Deflect DDoS or targeted failures automatically.<\/li>\n<\/ul>\n\n\n\n
                      Common Limitations<\/h3>\n\n\n\n
                      Limitation<\/th>Description<\/th><\/tr><\/thead>
                      DNS Caching<\/strong><\/td>Failover delay depends on DNS TTL.<\/td><\/tr>
                      False Positives<\/strong><\/td>Unstable health checks may trigger failover incorrectly.<\/td><\/tr>
                      No Session Awareness<\/strong><\/td>User sessions may break on redirection.<\/td><\/tr>
                      Limited Real-Time Response<\/strong><\/td>Not suitable for sub-second failover like load balancers.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                      \n\n\n\n
                      Best Practices & Recommendations<\/strong><\/h2>\n\n\n\n
                      Security Tips<\/h3>\n\n\n\n
                        \n
                      • Use DNSSEC<\/strong> to prevent spoofing.<\/li>\n\n\n\n
                      • Harden health check endpoints (e.g., auth, rate-limiting).<\/li>\n\n\n\n
                      • Monitor for failover abuse or configuration drift.<\/li>\n<\/ul>\n\n\n\n
                        Performance & Maintenance<\/h3>\n\n\n\n
                          \n
                        • Set appropriate TTL values<\/strong> (e.g., 60s) to balance failover speed and caching.<\/li>\n\n\n\n
                        • Regularly test failover manually or through CI.<\/li>\n\n\n\n
                        • Use observability tools<\/strong> to track DNS behavior.<\/li>\n<\/ul>\n\n\n\n
                          Compliance & Automation<\/h3>\n\n\n\n
                            \n
                          • Integrate with security scanners and policy engines (e.g., Open Policy Agent).<\/li>\n\n\n\n
                          • Automate DNS configuration with Terraform\/CDK\/Ansible.<\/li>\n<\/ul>\n\n\n\n
                            \n\n\n\n
                            Comparison with Alternatives<\/strong><\/h2>\n\n\n\n
                            Feature<\/th>DNS Failover<\/th>Load Balancer<\/th>Anycast<\/th><\/tr><\/thead>
                            Cost<\/strong><\/td>Low<\/td>Medium\/High<\/td>High<\/td><\/tr>
                            Setup Complexity<\/strong><\/td>Easy<\/td>Moderate<\/td>Complex<\/td><\/tr>
                            Failover Time<\/strong><\/td>Seconds\u2013minutes<\/td>Instant<\/td>Instant<\/td><\/tr>
                            Session Stickiness<\/strong><\/td>No<\/td>Yes<\/td>No<\/td><\/tr>
                            Cloud Native<\/strong><\/td>Yes<\/td>Yes<\/td>No<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                            When to Use DNS Failover<\/h3>\n\n\n\n
                              \n
                            • Budget-conscious HA strategies.<\/li>\n\n\n\n
                            • Multi-cloud or hybrid deployments.<\/li>\n\n\n\n
                            • DR planning and fallback options.<\/li>\n<\/ul>\n\n\n\n
                              \n\n\n\n
                              Conclusion<\/strong><\/h2>\n\n\n\n
                              DNS Failover is a lightweight yet powerful high-availability mechanism<\/strong> that plays a critical role in DevSecOps practices. When combined with CI\/CD automation, observability, and secure DNS practices, it enables robust and resilient applications with minimal overhead.<\/p>\n\n\n\n
                              As cloud-native technologies evolve, DNS Failover will integrate more deeply with service meshes, global load balancers, and edge networks.<\/p>\n\n\n\n
                              \n","protected":false},"excerpt":{"rendered":"
                              Introduction & Overview What is DNS Failover? DNS Failover is a high-availability mechanism that automatically redirects traffic to a standby […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-398","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"yoast_head":"\nDNS Failover in DevSecOps - SRE School<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/sreschool.com\/blog\/dns-failover-in-devsecops\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"DNS Failover in DevSecOps - SRE School\" \/>\n<meta property=\"og:description\" content=\"Introduction & Overview What is DNS Failover? DNS Failover is a high-availability mechanism that automatically redirects traffic to a standby […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/sreschool.com\/blog\/dns-failover-in-devsecops\/\" \/>\n<meta property=\"og:site_name\" content=\"SRE School\" \/>\n<meta property=\"article:published_time\" content=\"2025-06-24T06:38:52+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-05-05T07:29:44+00:00\" \/>\n<meta name=\"author\" content=\"priteshgeek\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"priteshgeek\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/sreschool.com\/blog\/dns-failover-in-devsecops\/\",\"url\":\"https:\/\/sreschool.com\/blog\/dns-failover-in-devsecops\/\",\"name\":\"DNS Failover in DevSecOps - SRE School\",\"isPartOf\":{\"@id\":\"https:\/\/sreschool.com\/blog\/#website\"},\"datePublished\":\"2025-06-24T06:38:52+00:00\",\"dateModified\":\"2026-05-05T07:29:44+00:00\",\"author\":{\"@id\":\"https:\/\/sreschool.com\/blog\/#\/schema\/person\/6a53e3870889dd6a65b2e04b7bc3d7db\"},\"breadcrumb\":{\"@id\":\"https:\/\/sreschool.com\/blog\/dns-failover-in-devsecops\/#breadcrumb\"},\"inLanguage\":\"en\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/sreschool.com\/blog\/dns-failover-in-devsecops\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/sreschool.com\/blog\/dns-failover-in-devsecops\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/sreschool.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"DNS Failover in DevSecOps\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/sreschool.com\/blog\/#website\",\"url\":\"https:\/\/sreschool.com\/blog\/\",\"name\":\"SRESchool\",\"description\":\"Master SRE. Build Resilient Systems. Lead the Future of Reliability\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/sreschool.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/sreschool.com\/blog\/#\/schema\/person\/6a53e3870889dd6a65b2e04b7bc3d7db\",\"name\":\"priteshgeek\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en\",\"@id\":\"https:\/\/sreschool.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/231a0e8b7a02636f2fbacf8dcf4494cb1cc0d49ecc9a8165fbaeaeeaf102641a?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/231a0e8b7a02636f2fbacf8dcf4494cb1cc0d49ecc9a8165fbaeaeeaf102641a?s=96&d=mm&r=g\",\"caption\":\"priteshgeek\"},\"url\":\"https:\/\/sreschool.com\/blog\/author\/priteshgeek\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"DNS Failover in DevSecOps - SRE School","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/sreschool.com\/blog\/dns-failover-in-devsecops\/","og_locale":"en_US","og_type":"article","og_title":"DNS Failover in DevSecOps - SRE School","og_description":"Introduction & Overview What is DNS Failover? DNS Failover is a high-availability mechanism that automatically redirects traffic to a standby […]","og_url":"https:\/\/sreschool.com\/blog\/dns-failover-in-devsecops\/","og_site_name":"SRE School","article_published_time":"2025-06-24T06:38:52+00:00","article_modified_time":"2026-05-05T07:29:44+00:00","author":"priteshgeek","twitter_card":"summary_large_image","twitter_misc":{"Written by":"priteshgeek","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/sreschool.com\/blog\/dns-failover-in-devsecops\/","url":"https:\/\/sreschool.com\/blog\/dns-failover-in-devsecops\/","name":"DNS Failover in DevSecOps - SRE School","isPartOf":{"@id":"https:\/\/sreschool.com\/blog\/#website"},"datePublished":"2025-06-24T06:38:52+00:00","dateModified":"2026-05-05T07:29:44+00:00","author":{"@id":"https:\/\/sreschool.com\/blog\/#\/schema\/person\/6a53e3870889dd6a65b2e04b7bc3d7db"},"breadcrumb":{"@id":"https:\/\/sreschool.com\/blog\/dns-failover-in-devsecops\/#breadcrumb"},"inLanguage":"en","potentialAction":[{"@type":"ReadAction","target":["https:\/\/sreschool.com\/blog\/dns-failover-in-devsecops\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/sreschool.com\/blog\/dns-failover-in-devsecops\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/sreschool.com\/blog\/"},{"@type":"ListItem","position":2,"name":"DNS Failover in DevSecOps"}]},{"@type":"WebSite","@id":"https:\/\/sreschool.com\/blog\/#website","url":"https:\/\/sreschool.com\/blog\/","name":"SRESchool","description":"Master SRE. Build Resilient Systems. Lead the Future of Reliability","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/sreschool.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en"},{"@type":"Person","@id":"https:\/\/sreschool.com\/blog\/#\/schema\/person\/6a53e3870889dd6a65b2e04b7bc3d7db","name":"priteshgeek","image":{"@type":"ImageObject","inLanguage":"en","@id":"https:\/\/sreschool.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/231a0e8b7a02636f2fbacf8dcf4494cb1cc0d49ecc9a8165fbaeaeeaf102641a?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/231a0e8b7a02636f2fbacf8dcf4494cb1cc0d49ecc9a8165fbaeaeeaf102641a?s=96&d=mm&r=g","caption":"priteshgeek"},"url":"https:\/\/sreschool.com\/blog\/author\/priteshgeek\/"}]}},"_links":{"self":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts\/398","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/comments?post=398"}],"version-history":[{"count":1,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts\/398\/revisions"}],"predecessor-version":[{"id":399,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts\/398\/revisions\/399"}],"wp:attachment":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/media?parent=398"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/categories?post=398"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/tags?post=398"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}