{"id":459,"date":"2025-06-24T09:35:36","date_gmt":"2025-06-24T09:35:36","guid":{"rendered":"https:\/\/sreschool.com\/blog\/?p=459"},"modified":"2026-05-05T07:29:42","modified_gmt":"2026-05-05T07:29:42","slug":"service-ownership-in-devsecops-a-complete-tutorial","status":"publish","type":"post","link":"https:\/\/sreschool.com\/blog\/service-ownership-in-devsecops-a-complete-tutorial\/","title":{"rendered":"Service Ownership in DevSecOps \u2014 A Complete Tutorial"},"content":{"rendered":"\n

\ud83d\udccc 1. Introduction & Overview<\/h1>\n\n\n\n

What is Service Ownership<\/strong>?<\/h3>\n\n\n\n

Service Ownership<\/strong> is the practice of assigning a single team (often cross-functional) full responsibility for the development<\/strong>, deployment<\/strong>, monitoring<\/strong>, security<\/strong>, and maintenance<\/strong> of a software service throughout its lifecycle.<\/p>\n\n\n\n

It is foundational to modern DevSecOps<\/strong> practices where developers, security, and operations collaborate seamlessly.<\/p>\n\n\n\n

History or Background<\/h3>\n\n\n\n
    \n
  • Emerged from Site Reliability Engineering (SRE)<\/strong> and DevOps<\/strong> cultures.<\/li>\n\n\n\n
  • Popularized by companies like Google, Netflix, and Amazon<\/strong>.<\/li>\n\n\n\n
  • Addressed challenges of “throw-it-over-the-wall” model between dev and ops teams.<\/li>\n<\/ul>\n\n\n\n

    Why is it Relevant in DevSecOps?<\/h3>\n\n\n\n
      \n
    • Ensures end-to-end accountability<\/strong>, including security from day one.<\/li>\n\n\n\n
    • Encourages secure coding<\/strong>, vulnerability patching<\/strong>, and compliance checks<\/strong> to be built into ownership.<\/li>\n\n\n\n
    • Minimizes security blind spots<\/strong> caused by team silos.<\/li>\n\n\n\n
    • Aligns with Shift Left<\/strong> principles (security earlier in development).<\/li>\n<\/ul>\n\n\n\n
      \n\n\n\n

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

      Key Terms and Definitions<\/h3>\n\n\n\n
      Term<\/th>Description<\/th><\/tr><\/thead>
      Service Owner<\/strong><\/td>A team (or individual) accountable for all aspects of a service.<\/td><\/tr>
      SLOs\/SLIs<\/strong><\/td>Service Level Objectives\/Indicators used to measure reliability.<\/td><\/tr>
      On-call Rotation<\/strong><\/td>A team schedule for handling service outages or security alerts.<\/td><\/tr>
      Toil<\/strong><\/td>Manual, repetitive tasks owners aim to automate.<\/td><\/tr>
      Shift Left<\/strong><\/td>Integrating testing\/security early in the development lifecycle.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

      How It Fits into the DevSecOps Lifecycle<\/h3>\n\n\n\n
         Plan \u2192 Code \u2192 Build \u2192 Test \u2192 Release \u2192 Deploy \u2192 Operate \u2192 Monitor\n             \u2191                                   \u2193\n         Service Ownership Enforces Dev+Sec Responsibility End-to-End\n<\/code><\/pre>\n\n\n\n
      Service Ownership ensures:<\/p>\n\n\n\n
        \n
      • Secure Code Reviews<\/strong> during Code & Build stages<\/li>\n\n\n\n
      • Vulnerability scanning<\/strong> during Test<\/li>\n\n\n\n
      • Patch management<\/strong> during Operate<\/li>\n\n\n\n
      • Monitoring + Incident Response<\/strong> during Monitor<\/li>\n<\/ul>\n\n\n\n
        \n\n\n\n
        \ud83c\udfd7\ufe0f 3. Architecture & How It Works<\/h2>\n\n\n\n
        Components of Service Ownership<\/h3>\n\n\n\n
        Component<\/th>Role<\/th><\/tr><\/thead>
        DevSecOps Team<\/td>Acts as the service owner, includes developers, testers, security<\/td><\/tr>
        CI\/CD Pipelines<\/td>Automate deployments, testing, security scanning<\/td><\/tr>
        Monitoring\/Observability Tools<\/td>Provide real-time metrics, alerts, and logs<\/td><\/tr>
        Security Integrations<\/td>Include tools like Snyk, Trivy, or Checkov in CI\/CD<\/td><\/tr>
        Cloud Infrastructure<\/td>Often managed via Terraform\/IaC with ownership tied to the service<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
        Internal Workflow<\/h3>\n\n\n\n
        [Developer Pushes Code]\n        \u2193\n[CI\/CD Triggered \u2192 Security Tests \u2192 Code Quality Check]\n        \u2193\n[Automated Deploy to Staging \u2192 Smoke Tests \u2192 Manual Approvals (if needed)]\n        \u2193\n[Production Deploy + Alert Setup + On-call Setup]\n        \u2193\n[Real-time Monitoring + Incident Response + Continuous Patching]\n<\/code><\/pre>\n\n\n\n
        Architecture Diagram (Described)<\/h3>\n\n\n\n
        Logical Diagram (Textual)<\/strong>:<\/p>\n\n\n\n
        +------------------+       +----------------+        +------------------+\n| Code Repository  |  -->  | CI\/CD Pipeline |  -->   | Kubernetes\/Cloud |\n+------------------+       +----------------+        +------------------+\n         |                          |                          |\n         v                          v                          v\n[Code Scan, SAST]       [Secrets Detection, IaC Scan]   [Logging, APM, Security Agents]\n<\/code><\/pre>\n\n\n\n
        Integration Points<\/h3>\n\n\n\n
        Tool Type<\/th>Examples<\/th>Purpose<\/th><\/tr><\/thead>
        CI\/CD<\/td>GitHub Actions, GitLab CI<\/td>Automate deployment & tests<\/td><\/tr>
        Monitoring<\/td>Prometheus, Grafana, Datadog<\/td>Metrics & observability<\/td><\/tr>
        Security<\/td>Trivy, Aqua, SonarQube, Snyk<\/td>Vulnerability scanning<\/td><\/tr>
        Cloud IaC<\/td>Terraform, Pulumi<\/td>Declarative infra with ownership<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
        \n\n\n\n
        \ud83d\ude80 4. Installation & Getting Started<\/h2>\n\n\n\n
        Basic Setup or Prerequisites<\/h3>\n\n\n\n
          \n
        • A microservice-based app (Node.js, Python, Go, etc.)<\/li>\n\n\n\n
        • CI\/CD platform (e.g., GitHub Actions)<\/li>\n\n\n\n
        • Monitoring tool (e.g., Prometheus)<\/li>\n\n\n\n
        • Security scanner (e.g., Trivy)<\/li>\n<\/ul>\n\n\n\n
          Step-by-Step: Set Up Basic Service Ownership<\/h3>\n\n\n\n
          \u2705 1. Create Service Repository<\/h4>\n\n\n\n
          mkdir inventory-service && cd inventory-service\ngit init\n<\/code><\/pre>\n\n\n\n
          \u2705 2. Add CI\/CD Pipeline<\/h4>\n\n\n\n
          Example: .github\/workflows\/ci.yml<\/code><\/strong><\/p>\n\n\n\n
          name: CI Pipeline\n\non: [push]\n\njobs:\n  build:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\/checkout@v3\n      - name: Run Tests\n        run: npm test\n      - name: Security Scan\n        uses: aquasecurity\/trivy-action@master\n        with:\n          scan-type: fs\n          scan-ref: .\n<\/code><\/pre>\n\n\n\n
          \u2705 3. Set Up Monitoring<\/h4>\n\n\n\n
            \n
          • Export Prometheus metrics using your framework (e.g., express-prometheus-middleware<\/code> for Node.js).<\/li>\n\n\n\n
          • Create Grafana dashboard with alert rules.<\/li>\n<\/ul>\n\n\n\n
            \u2705 4. Define Ownership in README.md<\/code><\/h4>\n\n\n\n
            ### Service Owner: Inventory Team\n- On-call Contact: oncall-inventory@example.com\n- Escalation: security@example.com\n<\/code><\/pre>\n\n\n\n
            \n\n\n\n
            \ud83e\uddea 5. Real-World Use Cases<\/h2>\n\n\n\n
            \ud83c\udfe5 Healthcare App Example<\/h3>\n\n\n\n
              \n
            • Ownership of patient-data-service<\/code> ensures PHI is encrypted and monitored.<\/li>\n\n\n\n
            • Daily Trivy scans check for vulnerabilities in container images.<\/li>\n<\/ul>\n\n\n\n
              \ud83d\uded2 E-commerce Scenario<\/h3>\n\n\n\n
                \n
              • payment-gateway<\/code> team owns security compliance with PCI-DSS.<\/li>\n\n\n\n
              • Ownership enforces real-time fraud monitoring and patching.<\/li>\n<\/ul>\n\n\n\n
                \ud83c\udfe6 Fintech Startup<\/h3>\n\n\n\n
                  \n
                • loan-service<\/code> is monitored for anomalous transaction patterns.<\/li>\n\n\n\n
                • Ownership includes SLA tracking and audit logging for regulators.<\/li>\n<\/ul>\n\n\n\n
                  \ud83c\udf93 EdTech Platform<\/h3>\n\n\n\n
                    \n
                  • quiz-service<\/code> is owned by the same dev team for faster feature delivery.<\/li>\n\n\n\n
                  • Security included from start via SonarQube and GitHub Advanced Security.<\/li>\n<\/ul>\n\n\n\n
                    \n\n\n\n
                    \u2705 6. Benefits & Limitations<\/h2>\n\n\n\n
                    \u2705 Key Benefits<\/h3>\n\n\n\n
                      \n
                    • Faster Incident Response<\/strong><\/li>\n\n\n\n
                    • Built-in Security<\/strong><\/li>\n\n\n\n
                    • Team Autonomy<\/strong><\/li>\n\n\n\n
                    • Higher Uptime & Reliability<\/strong><\/li>\n<\/ul>\n\n\n\n
                      \u26a0\ufe0f Common Challenges<\/h3>\n\n\n\n
                        \n
                      • Burnout from 24\/7 on-call<\/strong> pressure.<\/li>\n\n\n\n
                      • Teams need cross-skilling<\/strong> in DevOps & Security.<\/li>\n\n\n\n
                      • Requires strong tooling and culture<\/strong> support.<\/li>\n<\/ul>\n\n\n\n
                        \n\n\n\n
                        \ud83d\udccb 7. Best Practices & Recommendations<\/h2>\n\n\n\n
                        \ud83d\udd10 Security Tips<\/h3>\n\n\n\n
                          \n
                        • Use Secrets Management<\/strong> tools (Vault, SOPS).<\/li>\n\n\n\n
                        • Run static + dynamic + dependency<\/strong> scans in CI\/CD.<\/li>\n\n\n\n
                        • Use policy-as-code<\/strong> tools like OPA or Sentinel.<\/li>\n<\/ul>\n\n\n\n
                          \u2699\ufe0f Performance & Maintenance<\/h3>\n\n\n\n
                            \n
                          • Define error budgets<\/strong> and SLOs.<\/li>\n\n\n\n
                          • Automate toil-heavy tasks (e.g., log rotation, patching).<\/li>\n<\/ul>\n\n\n\n
                            \ud83e\uddfe Compliance Alignment<\/h3>\n\n\n\n
                              \n
                            • Integrate compliance checks (e.g., SOC2, HIPAA) into pipelines.<\/li>\n\n\n\n
                            • Use IaC to track ownership<\/strong> and infrastructure drift<\/strong>.<\/li>\n<\/ul>\n\n\n\n
                              \ud83d\udd04 Automation Ideas<\/h3>\n\n\n\n
                                \n
                              • Auto-assign incidents based on ownership label.<\/li>\n\n\n\n
                              • Auto-rotate on-call based on calendar.<\/li>\n<\/ul>\n\n\n\n
                                \n\n\n\n
                                \ud83d\udd01 8. Comparison with Alternatives<\/h2>\n\n\n\n
                                Model<\/th>Description<\/th>Best For<\/th><\/tr><\/thead>
                                Service Ownership<\/strong><\/td>Full responsibility by a single team<\/td>DevSecOps, security-heavy orgs<\/td><\/tr>
                                SRE Shared Model<\/td>SRE team owns reliability across services<\/td>Large orgs with central ops teams<\/td><\/tr>
                                Platform Teams<\/td>Central teams own infra, devs own logic<\/td>Medium\/large orgs with shared infra<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                                \n\n\n\n
                                \ud83c\udfaf 9. Conclusion<\/h2>\n\n\n\n
                                Final Thoughts<\/h3>\n\n\n\n
                                Service Ownership<\/strong> is a critical pillar for secure, scalable, and reliable software in a DevSecOps<\/strong> world. It builds a culture of accountability, integrates security from day one, and enables faster innovation.<\/p>\n\n\n\n
                                \ud83d\udccc Future Trends<\/h3>\n\n\n\n
                                  \n
                                • AI-driven ownership suggestion tools.<\/li>\n\n\n\n
                                • Automated compliance reporting per service.<\/li>\n\n\n\n
                                • More decentralized policy enforcement (e.g., Rego, Kyverno).<\/li>\n<\/ul>\n\n\n\n
                                  \n","protected":false},"excerpt":{"rendered":"
                                  \ud83d\udccc 1. Introduction & Overview What is Service Ownership? Service Ownership is the practice of assigning a single team (often […]<\/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-459","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"yoast_head":"\nService Ownership in DevSecOps \u2014 A Complete Tutorial - 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\/service-ownership-in-devsecops-a-complete-tutorial\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Service Ownership in DevSecOps \u2014 A Complete Tutorial - SRE School\" \/>\n<meta property=\"og:description\" content=\"\ud83d\udccc 1. Introduction & Overview What is Service Ownership? Service Ownership is the practice of assigning a single team (often […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/sreschool.com\/blog\/service-ownership-in-devsecops-a-complete-tutorial\/\" \/>\n<meta property=\"og:site_name\" content=\"SRE School\" \/>\n<meta property=\"article:published_time\" content=\"2025-06-24T09:35:36+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-05-05T07:29:42+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\/service-ownership-in-devsecops-a-complete-tutorial\/\",\"url\":\"https:\/\/sreschool.com\/blog\/service-ownership-in-devsecops-a-complete-tutorial\/\",\"name\":\"Service Ownership in DevSecOps \u2014 A Complete Tutorial - SRE School\",\"isPartOf\":{\"@id\":\"https:\/\/sreschool.com\/blog\/#website\"},\"datePublished\":\"2025-06-24T09:35:36+00:00\",\"dateModified\":\"2026-05-05T07:29:42+00:00\",\"author\":{\"@id\":\"https:\/\/sreschool.com\/blog\/#\/schema\/person\/6a53e3870889dd6a65b2e04b7bc3d7db\"},\"breadcrumb\":{\"@id\":\"https:\/\/sreschool.com\/blog\/service-ownership-in-devsecops-a-complete-tutorial\/#breadcrumb\"},\"inLanguage\":\"en\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/sreschool.com\/blog\/service-ownership-in-devsecops-a-complete-tutorial\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/sreschool.com\/blog\/service-ownership-in-devsecops-a-complete-tutorial\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/sreschool.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Service Ownership in DevSecOps \u2014 A Complete Tutorial\"}]},{\"@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":"Service Ownership in DevSecOps \u2014 A Complete Tutorial - 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\/service-ownership-in-devsecops-a-complete-tutorial\/","og_locale":"en_US","og_type":"article","og_title":"Service Ownership in DevSecOps \u2014 A Complete Tutorial - SRE School","og_description":"\ud83d\udccc 1. Introduction & Overview What is Service Ownership? Service Ownership is the practice of assigning a single team (often […]","og_url":"https:\/\/sreschool.com\/blog\/service-ownership-in-devsecops-a-complete-tutorial\/","og_site_name":"SRE School","article_published_time":"2025-06-24T09:35:36+00:00","article_modified_time":"2026-05-05T07:29:42+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\/service-ownership-in-devsecops-a-complete-tutorial\/","url":"https:\/\/sreschool.com\/blog\/service-ownership-in-devsecops-a-complete-tutorial\/","name":"Service Ownership in DevSecOps \u2014 A Complete Tutorial - SRE School","isPartOf":{"@id":"https:\/\/sreschool.com\/blog\/#website"},"datePublished":"2025-06-24T09:35:36+00:00","dateModified":"2026-05-05T07:29:42+00:00","author":{"@id":"https:\/\/sreschool.com\/blog\/#\/schema\/person\/6a53e3870889dd6a65b2e04b7bc3d7db"},"breadcrumb":{"@id":"https:\/\/sreschool.com\/blog\/service-ownership-in-devsecops-a-complete-tutorial\/#breadcrumb"},"inLanguage":"en","potentialAction":[{"@type":"ReadAction","target":["https:\/\/sreschool.com\/blog\/service-ownership-in-devsecops-a-complete-tutorial\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/sreschool.com\/blog\/service-ownership-in-devsecops-a-complete-tutorial\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/sreschool.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Service Ownership in DevSecOps \u2014 A Complete Tutorial"}]},{"@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\/459","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=459"}],"version-history":[{"count":1,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts\/459\/revisions"}],"predecessor-version":[{"id":460,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts\/459\/revisions\/460"}],"wp:attachment":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/media?parent=459"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/categories?post=459"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/tags?post=459"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}