{"id":400,"date":"2025-06-24T06:40:55","date_gmt":"2025-06-24T06:40:55","guid":{"rendered":"https:\/\/sreschool.com\/blog\/?p=400"},"modified":"2026-05-05T07:29:44","modified_gmt":"2026-05-05T07:29:44","slug":"blue-green-deployment-in-devsecops","status":"publish","type":"post","link":"https:\/\/sreschool.com\/blog\/blue-green-deployment-in-devsecops\/","title":{"rendered":"Blue-Green Deployment in DevSecOps"},"content":{"rendered":"\n

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

\ud83d\udd39 What is Blue-Green Deployment?<\/h3>\n\n\n\n

Blue-Green Deployment is a software release strategy<\/strong> that reduces downtime and risk by running two identical production environments<\/strong>\u2014Blue<\/strong> and Green<\/strong>. One environment (e.g., Blue) serves live production traffic while the other (Green) hosts the new version. When the new version is ready and tested, traffic is shifted from Blue to Green.<\/p>\n\n\n\n

\ud83d\udd39 History or Background<\/h3>\n\n\n\n
    \n
  • Originated as a zero-downtime deployment strategy<\/strong> in continuous delivery (CD) environments.<\/li>\n\n\n\n
  • Gained popularity with the rise of cloud-native architectures<\/strong>, DevOps<\/strong>, and microservices<\/strong>.<\/li>\n\n\n\n
  • Term popularized by Martin Fowler in his articles on Continuous Delivery.<\/li>\n<\/ul>\n\n\n\n

    \ud83d\udd39 Why is it Relevant in DevSecOps?<\/h3>\n\n\n\n
      \n
    • Minimizes downtime and rollback risk<\/strong>, crucial in secure production environments.<\/li>\n\n\n\n
    • Enables fast testing in production-like environments<\/strong>.<\/li>\n\n\n\n
    • Supports rapid security patching<\/strong> and version rollback.<\/li>\n\n\n\n
    • Integrates cleanly with automated security validations<\/strong> in CI\/CD pipelines.<\/li>\n<\/ul>\n\n\n\n
      \n\n\n\n

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

      \ud83d\udd39 Key Terms and Definitions<\/h3>\n\n\n\n
      Term<\/th>Definition<\/th><\/tr><\/thead>
      Blue Environment<\/strong><\/td>Active\/live environment receiving user traffic.<\/td><\/tr>
      Green Environment<\/strong><\/td>Standby environment hosting new version for testing.<\/td><\/tr>
      Cutover<\/strong><\/td>The switch from Blue to Green for live traffic.<\/td><\/tr>
      Rollback<\/strong><\/td>Reverting to Blue if Green fails post-deployment.<\/td><\/tr>
      Immutable Deployment<\/strong><\/td>Replacing entire environments rather than updating in place.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

      \ud83d\udd39 How it Fits into the DevSecOps Lifecycle<\/h3>\n\n\n\n
      Stage<\/th>Relevance<\/th><\/tr><\/thead>
      Plan<\/strong><\/td>Define release windows, fallback strategies.<\/td><\/tr>
      Develop<\/strong><\/td>Ensure code is deployable in either environment.<\/td><\/tr>
      Build\/Test<\/strong><\/td>Green env used for secure and automated test runs.<\/td><\/tr>
      Release<\/strong><\/td>Smooth transition without downtime or risk.<\/td><\/tr>
      Operate<\/strong><\/td>Real-time monitoring during\/after switchover.<\/td><\/tr>
      Secure<\/strong><\/td>Scan both environments for vulnerabilities before and after release.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      \n\n\n\n

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

      \ud83d\udd39 Components<\/h3>\n\n\n\n
        \n
      • Two Identical Environments<\/strong> (Blue & Green)<\/li>\n\n\n\n
      • Load Balancer or Traffic Router<\/strong> (e.g., AWS ALB, NGINX, Istio)<\/li>\n\n\n\n
      • CI\/CD Pipeline<\/strong> (e.g., Jenkins, GitHub Actions, GitLab CI)<\/li>\n\n\n\n
      • Security Gateways<\/strong> (e.g., Snyk, Trivy for image scans)<\/li>\n\n\n\n
      • Monitoring & Logging Tools<\/strong> (e.g., Prometheus, Grafana, ELK)<\/li>\n<\/ul>\n\n\n\n

        \ud83d\udd39 Internal Workflow<\/h3>\n\n\n\n
        1. Current version runs in BLUE (live).\n2. New version is deployed to GREEN.\n3. Automated testing, security scanning on GREEN.\n4. If GREEN passes, switch traffic via LB to GREEN.\n5. BLUE remains idle for rollback if needed.\n<\/code><\/pre>\n\n\n\n
        \ud83d\udd39 Architecture Diagram (Descriptive)<\/h3>\n\n\n\n
                 +---------------------+\n         |  Load Balancer      |\n         |  (e.g., NGINX\/ALB)  |\n         +----------+----------+\n                    |\n     +--------------+--------------+\n     |                             |\n+----v----+                 +------v-----+\n|  BLUE   |                 |   GREEN    |\n| (v1.0)  |                 |   (v2.0)   |\n+---------+                 +------------+\n   Live                        New Version\n<\/code><\/pre>\n\n\n\n
        \ud83d\udd39 Integration Points with CI\/CD or Cloud Tools<\/h3>\n\n\n\n
          \n
        • Jenkins\/GitLab CI<\/strong>: for pipeline automation.<\/li>\n\n\n\n
        • Terraform\/Ansible<\/strong>: for infra provisioning.<\/li>\n\n\n\n
        • Kubernetes (K8s)<\/strong>: use of namespaces for blue-green routing.<\/li>\n\n\n\n
        • AWS\/Azure\/GCP<\/strong>: Elastic Load Balancing, Auto Scaling groups.<\/li>\n\n\n\n
        • Istio or Linkerd<\/strong>: For advanced traffic routing in service mesh.<\/li>\n<\/ul>\n\n\n\n
          \n\n\n\n
          4. Installation & Getting Started<\/strong><\/h2>\n\n\n\n
          \ud83d\udd39 Basic Setup or Prerequisites<\/h3>\n\n\n\n
            \n
          • Two isolated but identical environments (VMs, containers, K8s namespaces, etc.)<\/li>\n\n\n\n
          • Load balancer with dynamic routing capability.<\/li>\n\n\n\n
          • CI\/CD pipeline setup with approval and rollback steps.<\/li>\n\n\n\n
          • Monitoring and alerting system integrated.<\/li>\n<\/ul>\n\n\n\n
            \ud83d\udd39 Step-by-Step Guide (Example with Kubernetes + NGINX)<\/h3>\n\n\n\n
            Step 1: Prepare Kubernetes Environments<\/strong><\/h4>\n\n\n\n
            kubectl create namespace blue\nkubectl create namespace green\n<\/code><\/pre>\n\n\n\n
            Step 2: Deploy v1 to Blue<\/strong><\/h4>\n\n\n\n
            kubectl apply -f app-v1.yaml -n blue\n<\/code><\/pre>\n\n\n\n
            Step 3: Deploy v2 to Green<\/strong><\/h4>\n\n\n\n
            kubectl apply -f app-v2.yaml -n green\n<\/code><\/pre>\n\n\n\n
            Step 4: Setup Ingress for Traffic Routing<\/strong><\/h4>\n\n\n\n
            # ingress.yaml\napiVersion: networking.k8s.io\/v1\nkind: Ingress\nmetadata:\n  name: app-ingress\nspec:\n  rules:\n  - host: myapp.com\n    http:\n      paths:\n      - path: \/\n        pathType: Prefix\n        backend:\n          service:\n            name: green-service   # change this to blue-service to rollback\n            port:\n              number: 80\n<\/code><\/pre>\n\n\n\n
            Step 5: Monitor and Switch<\/strong><\/h4>\n\n\n\n
              \n
            • Use kubectl edit ingress app-ingress<\/code> to switch between blue\/green.<\/li>\n\n\n\n
            • Monitor logs and health checks using Prometheus\/Grafana.<\/li>\n<\/ul>\n\n\n\n
              \n\n\n\n
              5. Real-World Use Cases<\/strong><\/h2>\n\n\n\n
              \ud83d\udd39 Use Case 1: Healthcare App Deployment (HIPAA)<\/h3>\n\n\n\n
                \n
              • New features tested in Green.<\/li>\n\n\n\n
              • Security scans (e.g., OWASP ZAP) on Green before cutover.<\/li>\n\n\n\n
              • No downtime during patient record updates.<\/li>\n<\/ul>\n\n\n\n
                \ud83d\udd39 Use Case 2: Banking System Upgrade (PCI-DSS)<\/h3>\n\n\n\n
                  \n
                • Upgraded payment gateway tested in Green.<\/li>\n\n\n\n
                • Traffic switched after real-time fraud monitoring integration.<\/li>\n<\/ul>\n\n\n\n
                  \ud83d\udd39 Use Case 3: SaaS Startup Feature Launch<\/h3>\n\n\n\n
                    \n
                  • Feature flags tested in Green with beta users.<\/li>\n\n\n\n
                  • Full cutover after positive feedback and no CVEs reported.<\/li>\n<\/ul>\n\n\n\n
                    \ud83d\udd39 Use Case 4: Government Website Patch<\/h3>\n\n\n\n
                      \n
                    • CVE security patch deployed to Green.<\/li>\n\n\n\n
                    • Scanned with Clair and AquaSec.<\/li>\n\n\n\n
                    • Switch to Green only after confirming no regressions.<\/li>\n<\/ul>\n\n\n\n
                      \n\n\n\n
                      6. Benefits & Limitations<\/strong><\/h2>\n\n\n\n
                      \ud83d\udd39 Benefits<\/h3>\n\n\n\n
                        \n
                      • \u2705 Zero downtime deployments<\/strong><\/li>\n\n\n\n
                      • \u2705 Easy rollback<\/strong><\/li>\n\n\n\n
                      • \u2705 Better security validation before going live<\/strong><\/li>\n\n\n\n
                      • \u2705 Minimal disruption to end-users<\/strong><\/li>\n<\/ul>\n\n\n\n
                        \ud83d\udd39 Limitations<\/h3>\n\n\n\n
                          \n
                        • \u274c Infrastructure cost<\/strong>: Requires duplicated resources<\/li>\n\n\n\n
                        • \u274c Operational complexity<\/strong><\/li>\n\n\n\n
                        • \u274c Data synchronization challenges<\/strong> if database schema changes<\/li>\n\n\n\n
                        • \u274c Manual switchovers may be error-prone<\/strong> without automation<\/li>\n<\/ul>\n\n\n\n
                          \n\n\n\n
                          7. Best Practices & Recommendations<\/strong><\/h2>\n\n\n\n
                          \ud83d\udd39 Security Tips<\/h3>\n\n\n\n
                            \n
                          • Run vulnerability scanners on Green before go-live.<\/li>\n\n\n\n
                          • Apply secrets rotation policies to both environments.<\/li>\n\n\n\n
                          • Use WAF and IAM consistently across both Blue and Green.<\/li>\n<\/ul>\n\n\n\n
                            \ud83d\udd39 Performance & Maintenance<\/h3>\n\n\n\n
                              \n
                            • Monitor latency and error rates in both environments.<\/li>\n\n\n\n
                            • Auto-scale both environments based on usage.<\/li>\n<\/ul>\n\n\n\n
                              \ud83d\udd39 Compliance Alignment<\/h3>\n\n\n\n
                                \n
                              • Keep audit logs of environment switches.<\/li>\n\n\n\n
                              • Document every deployment and approval step for traceability.<\/li>\n<\/ul>\n\n\n\n
                                \ud83d\udd39 Automation Ideas<\/h3>\n\n\n\n
                                  \n
                                • Use GitOps tools (ArgoCD\/Flux) for automated sync and rollback.<\/li>\n\n\n\n
                                • Integrate security scanners in CI pipeline before promoting to Green.<\/li>\n<\/ul>\n\n\n\n
                                  \n\n\n\n
                                  8. Comparison with Alternatives<\/strong><\/h2>\n\n\n\n
                                  Strategy<\/th>Downtime<\/th>Rollback<\/th>Complexity<\/th>Ideal For<\/th><\/tr><\/thead>
                                  Blue-Green<\/strong><\/td>\u274c None<\/td>\u2705 Easy<\/td>\u26a0\ufe0f Medium<\/td>Secure production systems<\/td><\/tr>
                                  Canary Deployments<\/strong><\/td>\u26a0\ufe0f Possible<\/td>\u2705 Gradual<\/td>\u26a0\ufe0f High<\/td>Large-scale feature tests<\/td><\/tr>
                                  Rolling Updates<\/strong><\/td>\u2705 Minimal<\/td>\u274c Hard<\/td>\u2705 Easy<\/td>Stateless microservices<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                                  \ud83d\udd39 When to Choose Blue-Green<\/h3>\n\n\n\n
                                    \n
                                  • Need zero-downtime deployment<\/strong>.<\/li>\n\n\n\n
                                  • High security assurance<\/strong> required before release.<\/li>\n\n\n\n
                                  • Full rollback required immediately upon failure<\/strong>.<\/li>\n<\/ul>\n\n\n\n
                                    \n\n\n\n
                                    9. Conclusion<\/strong><\/h2>\n\n\n\n
                                    Blue-Green Deployment is a powerful and reliable release strategy within DevSecOps, allowing teams to deploy code securely and confidently with minimal risk<\/strong> and maximum uptime<\/strong>. It integrates easily with modern CI\/CD tools and cloud infrastructure while aligning with security best practices.<\/p>\n\n\n\n
                                    \ud83d\udd39 Future Trends<\/h3>\n\n\n\n
                                      \n
                                    • Blue-green with AI-based traffic routing<\/strong><\/li>\n\n\n\n
                                    • Integration with policy-as-code<\/strong> and zero trust networks<\/strong><\/li>\n\n\n\n
                                    • Automation via GitOps<\/strong> and Infrastructure as Code (IaC)<\/strong><\/li>\n<\/ul>\n\n\n\n
                                      \n\n\n\n
                                      <\/p>\n","protected":false},"excerpt":{"rendered":"
                                      1. Introduction & Overview \ud83d\udd39 What is Blue-Green Deployment? Blue-Green Deployment is a software release strategy that reduces downtime and […]<\/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-400","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"yoast_head":"\nBlue-Green Deployment 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\/blue-green-deployment-in-devsecops\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Blue-Green Deployment in DevSecOps - SRE School\" \/>\n<meta property=\"og:description\" content=\"1. Introduction & Overview \ud83d\udd39 What is Blue-Green Deployment? Blue-Green Deployment is a software release strategy that reduces downtime and […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/sreschool.com\/blog\/blue-green-deployment-in-devsecops\/\" \/>\n<meta property=\"og:site_name\" content=\"SRE School\" \/>\n<meta property=\"article:published_time\" content=\"2025-06-24T06:40:55+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\/blue-green-deployment-in-devsecops\/\",\"url\":\"https:\/\/sreschool.com\/blog\/blue-green-deployment-in-devsecops\/\",\"name\":\"Blue-Green Deployment in DevSecOps - SRE School\",\"isPartOf\":{\"@id\":\"https:\/\/sreschool.com\/blog\/#website\"},\"datePublished\":\"2025-06-24T06:40:55+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\/blue-green-deployment-in-devsecops\/#breadcrumb\"},\"inLanguage\":\"en\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/sreschool.com\/blog\/blue-green-deployment-in-devsecops\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/sreschool.com\/blog\/blue-green-deployment-in-devsecops\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/sreschool.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Blue-Green Deployment 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":"Blue-Green Deployment 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\/blue-green-deployment-in-devsecops\/","og_locale":"en_US","og_type":"article","og_title":"Blue-Green Deployment in DevSecOps - SRE School","og_description":"1. Introduction & Overview \ud83d\udd39 What is Blue-Green Deployment? Blue-Green Deployment is a software release strategy that reduces downtime and […]","og_url":"https:\/\/sreschool.com\/blog\/blue-green-deployment-in-devsecops\/","og_site_name":"SRE School","article_published_time":"2025-06-24T06:40:55+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\/blue-green-deployment-in-devsecops\/","url":"https:\/\/sreschool.com\/blog\/blue-green-deployment-in-devsecops\/","name":"Blue-Green Deployment in DevSecOps - SRE School","isPartOf":{"@id":"https:\/\/sreschool.com\/blog\/#website"},"datePublished":"2025-06-24T06:40:55+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\/blue-green-deployment-in-devsecops\/#breadcrumb"},"inLanguage":"en","potentialAction":[{"@type":"ReadAction","target":["https:\/\/sreschool.com\/blog\/blue-green-deployment-in-devsecops\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/sreschool.com\/blog\/blue-green-deployment-in-devsecops\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/sreschool.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Blue-Green Deployment 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\/400","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=400"}],"version-history":[{"count":1,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts\/400\/revisions"}],"predecessor-version":[{"id":401,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts\/400\/revisions\/401"}],"wp:attachment":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/media?parent=400"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/categories?post=400"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/tags?post=400"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}