https://developer.app/_app/immutable/nodes/11.CeMD84jX.js

1import{s as v,n as y}from"../chunks/scheduler.Ce_0Mfso.js";import{S as x,i as _,e as u,s as d,c as b,h as w,a as h,d as i,b as m,g as I,f as k,j as f,k as T,l,m as $,t as C,n as E,o as L}from"../chunks/index.BX3iOdbR.js";import{P as q}from"../chunks/Paginator.BxgmZ9oC.js";function P(g){let t,o,n,p=`<h1>III - Infrastructure Abstracted</h1> <h3 class="punchline">Infrastructure is an implementation detail and should not be exposed in raw form</h3> <p>Developer platforms should abstract infrastructure complexities, allowing developers to focus their engineering skills on building high-quality software rather than grappling with infrastructure intricacies.</p> <p>Developers should not be expected to possess deep knowledge of specific infrastructure technologies, such as networking, storage, or clustering. 
2		By empowering developers in this way, they may  concentrate on writing code, designing architectures, solving business problems, and are no longer bogged down by infrastructure management tasks. 
3		This approach enhances developer productivity, reduces the learning curve, and allows teams to leverage their core engineering skills to deliver value more efficiently.</p> <p>Experiences should automatically resolve infrastructure details into the context of the application architecture. 
4		When developers define their application components, dependencies, and desired runtime characteristics, the developer platform should intelligently map those requirements to the appropriate infrastructure and configurations. 
5		This abstraction layer should handle the complex decisions of resource allocation, configuration management, and infrastructure optimization behind the scenes. 
6		By resolving infrastructure details into the application architecture context, the developer platform enables developers to think and operate at a higher level of abstraction, focusing on the logical components and interactions of their application rather than worrying about the underlying infrastructure specifics.</p>`,s,a,c;return a=new q({props:{previousLink:"/expectations/code-neutral/",previousTitle:"Code Neutral",nextLink:"/expectations/local-cloud-parity/",nextTitle:"Local/Cloud Parity"}}),{c(){t=u("meta"),o=d(),n=u("section"),n.innerHTML=p,s=d(),b(a.$$.fragment),this.h()},l(e){const r=w("svelte-8xvpyf",document.head);t=h(r,"META",{name:!0,content:!0}),r.forEach(i),o=m(e),n=h(e,"SECTION",{"data-svelte-h":!0}),I(n)!=="svelte-1qiecwn"&&(n.innerHTML=p),s=m(e),k(a.$$.fragment,e),this.h()},h(){f(t,"name","description"),f(t,"content","Expectation III - Infrastructure Abstracted")},m(e,r){T(document.head,t),l(e,o,r),l(e,n,r),l(e,s,r),$(a,e,r),c=!0},p:y,i(e){c||(C(a.$$.fragment,e),c=!0)},o(e){E(a.$$.fragment,e),c=!1},d(e){e&&(i(o),i(n),i(s)),i(t),L(a,e)}}}class B extends x{constructor(t){super(),_(this,t,null,P,v,{})}}export{B as component};