# Encapsulated Modules In addition to setting up boilerplate best-practices, central design principle of NodeBootstrap is to compose applications with re-usable, fully encapsulated set of modules. [TJ Holowaychuk](https://twitter.com/tjholowaychuk) explains this approach in a video screencast: In a more “spaghetti” Node project you may see HTTP route handlers in the main script or application area, tangled together. What TJ argues for and NodeBootstrap implements is: letting each module declare their own handlers, so if you are installing a “user management” or “blog” module, all you need to do is NPM install that module and indicate from the main app where in the URL path the routes get attached. Feel free to check-out more details about module design per NodeBootstrap in the source code of the [sample module](https://github.com/inadarei/nodebootstrap-microservice/tree/master/lib/homedoc). For a more advanced example, see: --- # 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.nodebootstrap.com/coding/encapsulated-modules.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.