# Sticking to Nestjs > It is not my intention to abandon `Nestjs`, but to use it as a base and focus on resource engineering. Obviously NestJS has many essential features already available, but in some cases Niro uses a particular approach. For example: Within Nest.js you have an approach for uploading files, but the approach is on-resource and still needs to be implemented in your architecture. The same example using Niro you already have routes to host files for different providers like MongoDB(GridFS), File System and S3, i.e. you don't need to program how to host your files, but to configure the module (Files). --- # 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://guilhermesantos.gitbook.io/niro-health/the-mission/sticking-to-nestjs.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.