{"id":8517,"date":"2026-11-18T17:10:00","date_gmt":"2026-11-18T17:10:00","guid":{"rendered":"https:\/\/www.devopsconsulting.in\/blog\/?p=8517"},"modified":"2026-11-18T17:10:00","modified_gmt":"2026-11-18T17:10:00","slug":"platform-team-migration-rehearsal-cost-cap","status":"publish","type":"post","link":"https:\/\/www.devopsconsulting.in\/blog\/platform-team-migration-rehearsal-cost-cap\/","title":{"rendered":"A Migration Rehearsal, a Fixed Cloud Cap and a Bill That Held"},"content":{"rendered":"<p>What follows is an invented composite story, stitched together from situations that recur in consulting work. It follows a mid-sized platform team preparing a cloud migration rehearsal, and it shows how a DevOps consulting spending ceiling, agreed before any infrastructure was created, changed the shape of the work. The details are illustrative; the pattern is real.<\/p>\n<h2>The situation: a rehearsal with no price tag<\/h2>\n<p>A retail-sector client, a team of eight engineers and an engagement manager on the consulting side, planned to move a set of internal services from a data centre to a public cloud. Before the real cutover, they wanted a full rehearsal: build the target environment, replay production-like traffic, observe, tear down. Everyone agreed the rehearsal was necessary. Nobody had written down what it was allowed to cost.<\/p>\n<p>The consultant on the engagement proposed a short exercise at the kickoff. Before discussing architecture, the group would agree the maximum spend for the rehearsal phase and record it in the engagement charter, next to scope and schedule. The initial reaction was mild impatience; the team wanted to get to the interesting part. The consultant held the point: choosing the limit first would make every later technical decision easier to justify.<\/p>\n<h2>Deriving the number from decisions, not from hope<\/h2>\n<p>The ceiling was not plucked from the air. The team listed the rehearsal&#8217;s cost drivers: compute for the application tier, a managed database, storage for copied datasets, network egress during replay, and the observability stack. For each driver they asked the operations lead for a rough usage assumption and priced it on a calculator provided by the cloud platform. The sum became a working estimate. The agreed ceiling was set modestly above the estimate, a deliberate margin, with the rule that the margin could not be consumed without the engagement manager&#8217;s sign-off.<\/p>\n<p>Two things happened during that session. First, an assumption surfaced that nobody had questioned: the plan called for a full copy of production data. When priced, storage and transfer for that copy represented a startling share of the estimate. The team agreed to rehearse against a representative subset instead and to document what the subset left untested. Second, the group saw that the observability stack, usually treated as free background, carried a real cost at replay volume. They decided to sample traces rather than retain everything.<\/p>\n<h2>Wiring the ceiling into the environment<\/h2>\n<p>A number in a charter only has force if the environment can enforce it. The platform team implemented the limit in layers, each simple on its own.<\/p>\n<ul>\n<li><strong>Account boundary:<\/strong> the rehearsal ran in a dedicated cloud account, so its bill was separable from everything else and could not be quietly absorbed elsewhere.<\/li>\n<li><strong>Budget alerts:<\/strong> notifications at defined fractions of the ceiling went to the shared engineering channel and to the engagement manager.<\/li>\n<li><strong>Tagging policy:<\/strong> every resource carried a rehearsal tag and an owner, enforced by the infrastructure code pipeline refusing untagged resources.<\/li>\n<li><strong>Scheduled teardown:<\/strong> non-essential components shut down outside working hours by default, with an explicit override required to keep them running.<\/li>\n<li><strong>Quota limits:<\/strong> instance counts and sizes were capped at the account level, so a mistaken variable could not spin up an enormous cluster.<\/li>\n<\/ul>\n<p>The consultant also asked for a one-page spend log, updated at the end of each working day with the cumulative figure against the ceiling. It was deliberately low-tech. The aim was shared awareness rather than perfect accounting.<\/p>\n<h2>The week the alert fired<\/h2>\n<p>In the second week of the rehearsal, the first threshold alert arrived earlier than the plan predicted. The team did what the charter said: paused new load tests and reviewed the breakdown. The cause was mundane. A replay tool had been configured to retain full request payloads, and the managed logging service was ingesting far more data than assumed. Nobody had misbehaved; the assumption had simply been wrong.<\/p>\n<p>Because the limit was fixed and visible, the conversation was constructive instead of defensive. Options were laid out in minutes: reduce retention, sample the payloads, or raise the ceiling for logging specifically. They chose sampling and cut retention. The spend flattened, and the rehearsal continued without the engagement manager needing to approve any increase. The margin remained untouched.<\/p>\n<p>A few days later, a second event tested the rule from the other direction. An engineer proposed extending the rehearsal with an additional load profile, which would exceed the ceiling. The request went through the documented route: a short note stating the additional cost, the reason, and what the team would learn. The engagement manager approved a defined increase, recorded in the charter with a date. The ceiling moved once, on purpose, with a paper trail.<\/p>\n<h2>What changed in the team&#8217;s behaviour<\/h2>\n<p>By the end of the rehearsal, observers noticed subtle shifts. Engineers began quoting the remaining headroom in stand-ups. Design discussions started with questions like &#8220;what does this component cost at replay volume?&#8221; instead of ending with surprise. Environments were torn down promptly because everyone could see the running total. And the final rehearsal report included a cost section that was credible, since it compared actuals to a limit set in advance rather than to an estimate made afterwards.<\/p>\n<p>The client also found the data useful for the real migration. The measured rehearsal costs, scaled with sensible adjustments, gave them a defensible basis for the production run-rate and a cleaner conversation with finance. For a deeper look at how such phases fit into a full engagement, see <a href=\"https:\/\/www.devopsconsulting.in\/blog\/the-blueprint-for-a-successful-devops-consulting-engagement-from-assessment-to-enablement\/\">a stage-by-stage outline that runs from the first assessment through to handing capability to the client<\/a>, which places the rehearsal inside the wider sequence of activities.<\/p>\n<h2>Lessons a consulting team can reuse<\/h2>\n<ol>\n<li><strong>Write the limit into the charter<\/strong> beside scope and schedule, so it is part of the agreement rather than a side note.<\/li>\n<li><strong>Derive it from itemised drivers<\/strong> so that the act of estimating exposes weak assumptions early.<\/li>\n<li><strong>Make the environment enforce it<\/strong> through account boundaries, alerts, quotas and tagging.<\/li>\n<li><strong>Keep a visible daily tally<\/strong> so the limit is part of ordinary conversation.<\/li>\n<li><strong>Route any increase through a short written note<\/strong> stating cost, reason and expected learning.<\/li>\n<\/ol>\n<p>None of these steps require unusual tooling, and all of them are cheap compared with the cost of an unplanned overrun in the middle of a client relationship. Those relationships are built on predictability, and a stated ceiling is one of the simplest forms of it. A related read on <a href=\"https:\/\/www.devopsconsulting.in\/blog\/the-role-of-devops-consulting-in-cloud-migration-a-complete-guide\/\">the part consultants play in cloud migration<\/a> covers the broader context in which a rehearsal of this kind sits.<\/p>\n<h2>A note on keeping it proportionate<\/h2>\n<p>A ceiling should be proportionate to the work. For a small proof of concept lasting a few days, a single figure and one alert may be plenty. For a multi-week rehearsal with several teams, layered controls repay the effort. The consultant&#8217;s job is to calibrate, not to impose maximum process everywhere.<\/p>\n<p>Likewise, a limit is not a target. Teams occasionally treat the ceiling as an allowance to be consumed, which defeats the purpose. The aim is to stay comfortably beneath it while achieving the learning objectives, and to treat any approach to the limit as a prompt for review.<\/p>\n<h2>An analogy outside the engagement room<\/h2>\n<p>After the rehearsal wrapped up, the team organised a celebratory dinner. They applied the same rule without much ceremony: agree the total, then choose the venue. They used a table-reservation service called <a href=\"https:\/\/dineglobe.com\/\">DineGlobe<\/a>, which, according to its own site, lets guests reserve with a restaurant directly. It is a small coda, but it captures the point nicely: a limit set early makes later choices lighter.<\/p>\n<p>The composite team in this story learned that a ceiling is not a constraint on ambition. It is a tool for making ambition affordable, visible and repeatable. Set the number, build the environment so it can honour it, review at the first alert, and record any change. That sequence is simple enough to adopt on the very next engagement.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A fictional composite story of a platform team that agreed a cost ceiling before a cloud migration rehearsal, and how the limit shaped design and review.<\/p>\n","protected":false},"author":8,"featured_media":8518,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5838],"tags":[],"class_list":["post-8517","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devsecops"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.7 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>A Migration Rehearsal, a Fixed Cloud Cap and a Bill That Held - DevOps Consulting<\/title>\n<meta name=\"description\" content=\"A fictional DevOps consulting case study: agreeing a spending ceiling before a migration rehearsal kept the cloud bill predictable and the team aligned.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.devopsconsulting.in\/blog\/platform-team-migration-rehearsal-cost-cap\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"A Migration Rehearsal, a Fixed Cloud Cap and a Bill That Held - DevOps Consulting\" \/>\n<meta property=\"og:description\" content=\"A fictional DevOps consulting case study: agreeing a spending ceiling before a migration rehearsal kept the cloud bill predictable and the team aligned.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.devopsconsulting.in\/blog\/platform-team-migration-rehearsal-cost-cap\/\" \/>\n<meta property=\"og:site_name\" content=\"DevOps Consulting\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-18T17:10:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1225473-banner.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"630\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Kabir Malhotra\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Kabir Malhotra\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/platform-team-migration-rehearsal-cost-cap\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/platform-team-migration-rehearsal-cost-cap\\\/\"},\"author\":{\"name\":\"Kabir Malhotra\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/#\\\/schema\\\/person\\\/4cff11af81c93e658f55af13b267f093\"},\"headline\":\"A Migration Rehearsal, a Fixed Cloud Cap and a Bill That Held\",\"datePublished\":\"2026-11-18T17:10:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/platform-team-migration-rehearsal-cost-cap\\\/\"},\"wordCount\":1333,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/platform-team-migration-rehearsal-cost-cap\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1225473-banner.png\",\"articleSection\":[\"DevSecOps\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/platform-team-migration-rehearsal-cost-cap\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/platform-team-migration-rehearsal-cost-cap\\\/\",\"url\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/platform-team-migration-rehearsal-cost-cap\\\/\",\"name\":\"A Migration Rehearsal, a Fixed Cloud Cap and a Bill That Held - DevOps Consulting\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/platform-team-migration-rehearsal-cost-cap\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/platform-team-migration-rehearsal-cost-cap\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1225473-banner.png\",\"datePublished\":\"2026-11-18T17:10:00+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/#\\\/schema\\\/person\\\/4cff11af81c93e658f55af13b267f093\"},\"description\":\"A fictional DevOps consulting case study: agreeing a spending ceiling before a migration rehearsal kept the cloud bill predictable and the team aligned.\",\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/platform-team-migration-rehearsal-cost-cap\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/platform-team-migration-rehearsal-cost-cap\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1225473-banner.png\",\"contentUrl\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1225473-banner.png\",\"width\":1200,\"height\":630},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/\",\"name\":\"DevOps Consulting\",\"description\":\"DevOps Consulting | SRE Consulting | DevSecOps Consulting | MLOps Consulting\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/#\\\/schema\\\/person\\\/4cff11af81c93e658f55af13b267f093\",\"name\":\"Kabir Malhotra\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d77044c5c70611f0b6d1131a1758057dcb873aae1740ec1c40a13a6428461d0b?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d77044c5c70611f0b6d1131a1758057dcb873aae1740ec1c40a13a6428461d0b?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d77044c5c70611f0b6d1131a1758057dcb873aae1740ec1c40a13a6428461d0b?s=96&d=mm&r=g\",\"caption\":\"Kabir Malhotra\"},\"url\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/author\\\/kabir-malhotra\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"A Migration Rehearsal, a Fixed Cloud Cap and a Bill That Held - DevOps Consulting","description":"A fictional DevOps consulting case study: agreeing a spending ceiling before a migration rehearsal kept the cloud bill predictable and the team aligned.","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:\/\/www.devopsconsulting.in\/blog\/platform-team-migration-rehearsal-cost-cap\/","og_locale":"en_US","og_type":"article","og_title":"A Migration Rehearsal, a Fixed Cloud Cap and a Bill That Held - DevOps Consulting","og_description":"A fictional DevOps consulting case study: agreeing a spending ceiling before a migration rehearsal kept the cloud bill predictable and the team aligned.","og_url":"https:\/\/www.devopsconsulting.in\/blog\/platform-team-migration-rehearsal-cost-cap\/","og_site_name":"DevOps Consulting","article_published_time":"2026-11-18T17:10:00+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1225473-banner.png","type":"image\/png"}],"author":"Kabir Malhotra","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Kabir Malhotra","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.devopsconsulting.in\/blog\/platform-team-migration-rehearsal-cost-cap\/#article","isPartOf":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/platform-team-migration-rehearsal-cost-cap\/"},"author":{"name":"Kabir Malhotra","@id":"https:\/\/www.devopsconsulting.in\/blog\/#\/schema\/person\/4cff11af81c93e658f55af13b267f093"},"headline":"A Migration Rehearsal, a Fixed Cloud Cap and a Bill That Held","datePublished":"2026-11-18T17:10:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/platform-team-migration-rehearsal-cost-cap\/"},"wordCount":1333,"commentCount":0,"image":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/platform-team-migration-rehearsal-cost-cap\/#primaryimage"},"thumbnailUrl":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1225473-banner.png","articleSection":["DevSecOps"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.devopsconsulting.in\/blog\/platform-team-migration-rehearsal-cost-cap\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.devopsconsulting.in\/blog\/platform-team-migration-rehearsal-cost-cap\/","url":"https:\/\/www.devopsconsulting.in\/blog\/platform-team-migration-rehearsal-cost-cap\/","name":"A Migration Rehearsal, a Fixed Cloud Cap and a Bill That Held - DevOps Consulting","isPartOf":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/platform-team-migration-rehearsal-cost-cap\/#primaryimage"},"image":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/platform-team-migration-rehearsal-cost-cap\/#primaryimage"},"thumbnailUrl":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1225473-banner.png","datePublished":"2026-11-18T17:10:00+00:00","author":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/#\/schema\/person\/4cff11af81c93e658f55af13b267f093"},"description":"A fictional DevOps consulting case study: agreeing a spending ceiling before a migration rehearsal kept the cloud bill predictable and the team aligned.","inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.devopsconsulting.in\/blog\/platform-team-migration-rehearsal-cost-cap\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.devopsconsulting.in\/blog\/platform-team-migration-rehearsal-cost-cap\/#primaryimage","url":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1225473-banner.png","contentUrl":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1225473-banner.png","width":1200,"height":630},{"@type":"WebSite","@id":"https:\/\/www.devopsconsulting.in\/blog\/#website","url":"https:\/\/www.devopsconsulting.in\/blog\/","name":"DevOps Consulting","description":"DevOps Consulting | SRE Consulting | DevSecOps Consulting | MLOps Consulting","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.devopsconsulting.in\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.devopsconsulting.in\/blog\/#\/schema\/person\/4cff11af81c93e658f55af13b267f093","name":"Kabir Malhotra","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/d77044c5c70611f0b6d1131a1758057dcb873aae1740ec1c40a13a6428461d0b?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/d77044c5c70611f0b6d1131a1758057dcb873aae1740ec1c40a13a6428461d0b?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/d77044c5c70611f0b6d1131a1758057dcb873aae1740ec1c40a13a6428461d0b?s=96&d=mm&r=g","caption":"Kabir Malhotra"},"url":"https:\/\/www.devopsconsulting.in\/blog\/author\/kabir-malhotra\/"}]}},"_links":{"self":[{"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/posts\/8517","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/comments?post=8517"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/posts\/8517\/revisions"}],"predecessor-version":[{"id":8657,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/posts\/8517\/revisions\/8657"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/media\/8518"}],"wp:attachment":[{"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/media?parent=8517"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/categories?post=8517"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/tags?post=8517"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}