# Resource Layer The resource layer mainly consists of two parts: * **Resource Aggregation/Abstraction Layer:** Digital resources nowadays are ubiquitous and mostly underutilized. From edge servers to consumer-level hardware, abundant computational power/storage capacity/bandwidth is waiting for us to tap into. The resource aggregation layer serves as the platform abstraction layer, onboarding those resources to establish a strong network. * **Service Scheduling Layer:** Cloud-native architecture supported by Kubernetes enabled smooth deployment/scaling of microservices at the center, supporting most of the modern applications that we enjoy every day. We believe such a revolution is long-due in the edge space. Our service scheduling layer acts as the intelligent housekeeper between services and the physical resources that are most suited to deploy them, bringing efficiency, utilization optimization, and developer friendliness to the whole edge experience. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.gradient.network/hide/layers/resource-layer.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.