{"id":1185,"date":"2026-04-17T10:00:00","date_gmt":"2026-04-17T09:00:00","guid":{"rendered":"https:\/\/wade.one\/blog\/?p=1185"},"modified":"2026-04-13T15:07:46","modified_gmt":"2026-04-13T15:07:46","slug":"the-case-for-smaller-deployments","status":"publish","type":"post","link":"https:\/\/wade.one\/blog\/2026\/04\/17\/the-case-for-smaller-deployments\/","title":{"rendered":"The Case for Smaller Deployments"},"content":{"rendered":"<p><img decoding=\"async\" src=\"https:\/\/wade.one\/blog\/wp-content\/uploads\/2026\/04\/01-stack-shipping-containers-forming-colorful.webp\" alt=\"Stacked shipping containers\" style=\"float:right;width:280px;max-width:40%;height:auto;margin:0 0 1rem 1rem\" loading=\"lazy\" \/><\/p>\n<p>I trust smaller deployments more than bigger ones.<\/p>\n<p>That is not because I think change is bad. It is because I think large releases hide too much. When one deployment carries half a dozen unrelated changes, it becomes harder to tell what actually broke, harder to roll back cleanly, and harder to tell whether the release was good or just lucky.<\/p>\n<h2>Smaller releases are easier to reason about<\/h2>\n<p>The main benefit of a smaller deployment is not aesthetic. It is visibility.<\/p>\n<p>If you ship one thing, you can usually tell whether that thing worked. If you ship ten things, you have to start guessing. A smaller release gives you a tighter boundary around the change, which means faster debugging and less confusion when production behaves badly.<\/p>\n<p>That matters because most deployment pain is not really about the code itself. It is about the time spent answering simple questions:<\/p>\n<ul>\n<li>what changed<\/li>\n<li>what started failing<\/li>\n<li>what can we safely undo<\/li>\n<li>who owns the next step<\/li>\n<\/ul>\n<p>The fewer unrelated changes in a release, the easier those questions are to answer.<\/p>\n<h2>Rollback is only useful when the blast radius is small<\/h2>\n<p>People like to talk about rollback like it is a magic safety net. It is not.<\/p>\n<p>A rollback only helps when the deployment is narrow enough that undoing it does not create more damage than the original problem. If you bundle too much work together, rollback gets messy fast. You may not want to revert everything. You may not be able to revert only one part. You may end up in the worst possible place: trying to untangle several changes in production while everybody is already stressed.<\/p>\n<p>That is why smaller deployments are so useful. They keep rollback simple enough to be real.<\/p>\n<h2>Bigger releases slow teams down<\/h2>\n<p>People sometimes argue for larger releases because they feel more efficient. Fewer deploys, fewer overheads, fewer interrupts.<\/p>\n<p>In practice, I usually see the opposite.<\/p>\n<p>Large releases create more review friction, more QA pressure, more coordination, and more fear. When a team expects every deployment to carry a lot of risk, they start treating releases like events instead of routine work. That slows everything down.<\/p>\n<p>Smaller deployments lower the emotional cost of shipping. They make it easier to move forward without turning every release into a mini crisis.<\/p>\n<h2>The real win is faster feedback<\/h2>\n<p>The best reason to prefer smaller deployments is feedback.<\/p>\n<p>When you ship less at once, you get signal sooner. If something is wrong, you find out sooner. If something is fine, you know that sooner too. That is the part people overlook. Small releases are not just safer. They are also better for learning.<\/p>\n<p>For me, that is the whole point. Good deployment practice is not about making shipping feel ceremonial. It is about making change predictable enough that the team can keep moving.<\/p>\n<p>If a deployment is too big to understand, it is too big.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Smaller deployments are usually easier to trust, easier to roll back, and easier to debug. Once a release starts carrying too much change, the team spends more time managing risk than shipping value.<\/p>\n","protected":false},"author":0,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[13,25],"tags":[54,61,104,82,103],"class_list":["post-1185","post","type-post","status-publish","format-standard","hentry","category-programming","category-software-engineer","tag-debugging","tag-deployments","tag-operations","tag-release-process","tag-rollback"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.4 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>The Case for Smaller Deployments - wade.one<\/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:\/\/wade.one\/blog\/2026\/04\/17\/the-case-for-smaller-deployments\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"The Case for Smaller Deployments - wade.one\" \/>\n<meta property=\"og:description\" content=\"Smaller deployments are usually easier to trust, easier to roll back, and easier to debug. Once a release starts carrying too much change, the team spends more time managing risk than shipping value.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/wade.one\/blog\/2026\/04\/17\/the-case-for-smaller-deployments\/\" \/>\n<meta property=\"og:site_name\" content=\"wade.one\" \/>\n<meta property=\"article:published_time\" content=\"2026-04-17T09:00:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/wade.one\/blog\/wp-content\/uploads\/2026\/04\/01-stack-shipping-containers-forming-colorful.webp\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@wadewomersley\" \/>\n<meta name=\"twitter:site\" content=\"@wadewomersley\" \/>\n<meta name=\"twitter:label1\" content=\"Estimated reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"2 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/wade.one\\\/blog\\\/2026\\\/04\\\/17\\\/the-case-for-smaller-deployments\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/wade.one\\\/blog\\\/2026\\\/04\\\/17\\\/the-case-for-smaller-deployments\\\/\"},\"author\":{\"name\":\"\",\"@id\":\"\"},\"headline\":\"The Case for Smaller Deployments\",\"datePublished\":\"2026-04-17T09:00:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/wade.one\\\/blog\\\/2026\\\/04\\\/17\\\/the-case-for-smaller-deployments\\\/\"},\"wordCount\":489,\"publisher\":{\"@id\":\"https:\\\/\\\/wade.one\\\/blog\\\/#\\\/schema\\\/person\\\/8b4739f8f8bb2cff5d792d4b8779fcc3\"},\"image\":{\"@id\":\"https:\\\/\\\/wade.one\\\/blog\\\/2026\\\/04\\\/17\\\/the-case-for-smaller-deployments\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/wade.one\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/01-stack-shipping-containers-forming-colorful.webp\",\"keywords\":[\"debugging\",\"deployments\",\"operations\",\"release-process\",\"rollback\"],\"articleSection\":[\"Programming\",\"Software Engineer\"],\"inLanguage\":\"en-GB\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/wade.one\\\/blog\\\/2026\\\/04\\\/17\\\/the-case-for-smaller-deployments\\\/\",\"url\":\"https:\\\/\\\/wade.one\\\/blog\\\/2026\\\/04\\\/17\\\/the-case-for-smaller-deployments\\\/\",\"name\":\"The Case for Smaller Deployments - wade.one\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/wade.one\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/wade.one\\\/blog\\\/2026\\\/04\\\/17\\\/the-case-for-smaller-deployments\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/wade.one\\\/blog\\\/2026\\\/04\\\/17\\\/the-case-for-smaller-deployments\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/wade.one\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/01-stack-shipping-containers-forming-colorful.webp\",\"datePublished\":\"2026-04-17T09:00:00+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/wade.one\\\/blog\\\/2026\\\/04\\\/17\\\/the-case-for-smaller-deployments\\\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/wade.one\\\/blog\\\/2026\\\/04\\\/17\\\/the-case-for-smaller-deployments\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\\\/\\\/wade.one\\\/blog\\\/2026\\\/04\\\/17\\\/the-case-for-smaller-deployments\\\/#primaryimage\",\"url\":\"https:\\\/\\\/wade.one\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/01-stack-shipping-containers-forming-colorful.webp\",\"contentUrl\":\"https:\\\/\\\/wade.one\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/01-stack-shipping-containers-forming-colorful.webp\",\"width\":1024,\"height\":741,\"caption\":\"Stacked shipping containers\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/wade.one\\\/blog\\\/2026\\\/04\\\/17\\\/the-case-for-smaller-deployments\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/wade.one\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"The Case for Smaller Deployments\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/wade.one\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/wade.one\\\/blog\\\/\",\"name\":\"wade.one\",\"description\":\"wade womersley - york based software engineer\",\"publisher\":{\"@id\":\"https:\\\/\\\/wade.one\\\/blog\\\/#\\\/schema\\\/person\\\/8b4739f8f8bb2cff5d792d4b8779fcc3\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/wade.one\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-GB\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\\\/\\\/wade.one\\\/blog\\\/#\\\/schema\\\/person\\\/8b4739f8f8bb2cff5d792d4b8779fcc3\",\"name\":\"Wade Womersley\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\\\/\\\/wade.one\\\/blog\\\/wp-content\\\/uploads\\\/2015\\\/02\\\/200px.png\",\"url\":\"https:\\\/\\\/wade.one\\\/blog\\\/wp-content\\\/uploads\\\/2015\\\/02\\\/200px.png\",\"contentUrl\":\"https:\\\/\\\/wade.one\\\/blog\\\/wp-content\\\/uploads\\\/2015\\\/02\\\/200px.png\",\"width\":202,\"height\":200,\"caption\":\"Wade Womersley\"},\"logo\":{\"@id\":\"https:\\\/\\\/wade.one\\\/blog\\\/wp-content\\\/uploads\\\/2015\\\/02\\\/200px.png\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"The Case for Smaller Deployments - wade.one","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:\/\/wade.one\/blog\/2026\/04\/17\/the-case-for-smaller-deployments\/","og_locale":"en_GB","og_type":"article","og_title":"The Case for Smaller Deployments - wade.one","og_description":"Smaller deployments are usually easier to trust, easier to roll back, and easier to debug. Once a release starts carrying too much change, the team spends more time managing risk than shipping value.","og_url":"https:\/\/wade.one\/blog\/2026\/04\/17\/the-case-for-smaller-deployments\/","og_site_name":"wade.one","article_published_time":"2026-04-17T09:00:00+00:00","og_image":[{"url":"https:\/\/wade.one\/blog\/wp-content\/uploads\/2026\/04\/01-stack-shipping-containers-forming-colorful.webp","type":"","width":"","height":""}],"twitter_card":"summary_large_image","twitter_creator":"@wadewomersley","twitter_site":"@wadewomersley","twitter_misc":{"Estimated reading time":"2 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/wade.one\/blog\/2026\/04\/17\/the-case-for-smaller-deployments\/#article","isPartOf":{"@id":"https:\/\/wade.one\/blog\/2026\/04\/17\/the-case-for-smaller-deployments\/"},"author":{"name":"","@id":""},"headline":"The Case for Smaller Deployments","datePublished":"2026-04-17T09:00:00+00:00","mainEntityOfPage":{"@id":"https:\/\/wade.one\/blog\/2026\/04\/17\/the-case-for-smaller-deployments\/"},"wordCount":489,"publisher":{"@id":"https:\/\/wade.one\/blog\/#\/schema\/person\/8b4739f8f8bb2cff5d792d4b8779fcc3"},"image":{"@id":"https:\/\/wade.one\/blog\/2026\/04\/17\/the-case-for-smaller-deployments\/#primaryimage"},"thumbnailUrl":"https:\/\/wade.one\/blog\/wp-content\/uploads\/2026\/04\/01-stack-shipping-containers-forming-colorful.webp","keywords":["debugging","deployments","operations","release-process","rollback"],"articleSection":["Programming","Software Engineer"],"inLanguage":"en-GB"},{"@type":"WebPage","@id":"https:\/\/wade.one\/blog\/2026\/04\/17\/the-case-for-smaller-deployments\/","url":"https:\/\/wade.one\/blog\/2026\/04\/17\/the-case-for-smaller-deployments\/","name":"The Case for Smaller Deployments - wade.one","isPartOf":{"@id":"https:\/\/wade.one\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/wade.one\/blog\/2026\/04\/17\/the-case-for-smaller-deployments\/#primaryimage"},"image":{"@id":"https:\/\/wade.one\/blog\/2026\/04\/17\/the-case-for-smaller-deployments\/#primaryimage"},"thumbnailUrl":"https:\/\/wade.one\/blog\/wp-content\/uploads\/2026\/04\/01-stack-shipping-containers-forming-colorful.webp","datePublished":"2026-04-17T09:00:00+00:00","breadcrumb":{"@id":"https:\/\/wade.one\/blog\/2026\/04\/17\/the-case-for-smaller-deployments\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/wade.one\/blog\/2026\/04\/17\/the-case-for-smaller-deployments\/"]}]},{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/wade.one\/blog\/2026\/04\/17\/the-case-for-smaller-deployments\/#primaryimage","url":"https:\/\/wade.one\/blog\/wp-content\/uploads\/2026\/04\/01-stack-shipping-containers-forming-colorful.webp","contentUrl":"https:\/\/wade.one\/blog\/wp-content\/uploads\/2026\/04\/01-stack-shipping-containers-forming-colorful.webp","width":1024,"height":741,"caption":"Stacked shipping containers"},{"@type":"BreadcrumbList","@id":"https:\/\/wade.one\/blog\/2026\/04\/17\/the-case-for-smaller-deployments\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/wade.one\/blog\/"},{"@type":"ListItem","position":2,"name":"The Case for Smaller Deployments"}]},{"@type":"WebSite","@id":"https:\/\/wade.one\/blog\/#website","url":"https:\/\/wade.one\/blog\/","name":"wade.one","description":"wade womersley - york based software engineer","publisher":{"@id":"https:\/\/wade.one\/blog\/#\/schema\/person\/8b4739f8f8bb2cff5d792d4b8779fcc3"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/wade.one\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-GB"},{"@type":["Person","Organization"],"@id":"https:\/\/wade.one\/blog\/#\/schema\/person\/8b4739f8f8bb2cff5d792d4b8779fcc3","name":"Wade Womersley","image":{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/wade.one\/blog\/wp-content\/uploads\/2015\/02\/200px.png","url":"https:\/\/wade.one\/blog\/wp-content\/uploads\/2015\/02\/200px.png","contentUrl":"https:\/\/wade.one\/blog\/wp-content\/uploads\/2015\/02\/200px.png","width":202,"height":200,"caption":"Wade Womersley"},"logo":{"@id":"https:\/\/wade.one\/blog\/wp-content\/uploads\/2015\/02\/200px.png"}}]}},"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":1183,"url":"https:\/\/wade.one\/blog\/2026\/04\/15\/the-real-cost-of-fancy-cloud-abstractions\/","url_meta":{"origin":1185,"position":0},"title":"The Real Cost of Fancy Cloud Abstractions","author":"","date":"April 15, 2026","format":false,"excerpt":"Fancy cloud abstractions often look like they remove complexity, but a lot of the time they just move it somewhere harder to see. That matters when something breaks and you need to debug it or hand it over to someone else.","rel":"","context":"In &quot;Programming&quot;","block_context":{"text":"Programming","link":"https:\/\/wade.one\/blog\/category\/programming\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1169,"url":"https:\/\/wade.one\/blog\/2026\/04\/02\/the-problem-with-simple-aws-architectures\/","url_meta":{"origin":1185,"position":1},"title":"The Problem With &#8220;Simple&#8221; AWS Architectures","author":"","date":"April 2, 2026","format":false,"excerpt":"AWS diagrams love to look simple. The problem is that the operational reality behind them is usually doing a lot more work than the picture admits.","rel":"","context":"In &quot;Programming&quot;","block_context":{"text":"Programming","link":"https:\/\/wade.one\/blog\/category\/programming\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1176,"url":"https:\/\/wade.one\/blog\/2026\/04\/08\/why-build-pipelines-become-part-of-the-product\/","url_meta":{"origin":1185,"position":2},"title":"Why Build Pipelines Become Part of the Product","author":"","date":"April 8, 2026","format":false,"excerpt":"Build pipelines stop being \"just internal tooling\" the moment they start deciding how fast you can ship, how often you break things, and how painful releases feel.","rel":"","context":"In &quot;Software Engineer&quot;","block_context":{"text":"Software Engineer","link":"https:\/\/wade.one\/blog\/category\/software-engineer\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1170,"url":"https:\/\/wade.one\/blog\/2026\/04\/03\/why-environment-management-gets-messy-faster-than-people-expect\/","url_meta":{"origin":1185,"position":3},"title":"Why Environment Management Gets Messy Faster Than People Expect","author":"","date":"April 3, 2026","format":false,"excerpt":"Environment management usually looks simple at first. Then defaults drift, secrets spread out, local setups stop matching production, and the whole thing becomes a source of avoidable mistakes.","rel":"","context":"In &quot;Programming&quot;","block_context":{"text":"Programming","link":"https:\/\/wade.one\/blog\/category\/programming\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1168,"url":"https:\/\/wade.one\/blog\/2026\/04\/01\/why-i-still-like-serverless-for-small-teams\/","url_meta":{"origin":1185,"position":4},"title":"Why I Still Like Serverless for Small Teams","author":"","date":"April 1, 2026","format":false,"excerpt":"Serverless has real tradeoffs, but for small teams I still think it usually wins. The operational overhead stays low, the first version ships faster, and the mistakes are easier to afford early on.","rel":"","context":"In &quot;Programming&quot;","block_context":{"text":"Programming","link":"https:\/\/wade.one\/blog\/category\/programming\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1171,"url":"https:\/\/wade.one\/blog\/2026\/04\/04\/i-trust-boring-infrastructure-more-than-clever-infrastructure\/","url_meta":{"origin":1185,"position":5},"title":"I Trust Boring Infrastructure More Than Clever Infrastructure","author":"","date":"April 4, 2026","format":false,"excerpt":"Clever infrastructure looks impressive in diagrams. Boring infrastructure is usually easier to operate, easier to debug, and much easier to keep alive once real users depend on it.","rel":"","context":"In &quot;Programming&quot;","block_context":{"text":"Programming","link":"https:\/\/wade.one\/blog\/category\/programming\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/wade.one\/blog\/wp-json\/wp\/v2\/posts\/1185","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wade.one\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wade.one\/blog\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/wade.one\/blog\/wp-json\/wp\/v2\/comments?post=1185"}],"version-history":[{"count":4,"href":"https:\/\/wade.one\/blog\/wp-json\/wp\/v2\/posts\/1185\/revisions"}],"predecessor-version":[{"id":1223,"href":"https:\/\/wade.one\/blog\/wp-json\/wp\/v2\/posts\/1185\/revisions\/1223"}],"wp:attachment":[{"href":"https:\/\/wade.one\/blog\/wp-json\/wp\/v2\/media?parent=1185"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wade.one\/blog\/wp-json\/wp\/v2\/categories?post=1185"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wade.one\/blog\/wp-json\/wp\/v2\/tags?post=1185"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}