---
title: "Comment by Stefan Müller on \"10 things you shouldn't do while running Node.js in production\" | Hashnode"
description: "I would like to add the following topics as what you shouldn't do in production: Serve static assets not minified and gzip'ed (see grunt) Disallow local"
url: "https://hashnode.com/posts/10-things-you-shouldnt-do-while-running-nodejs-in-production/57bee46e93309a25047c619a/comment/59706a2f107fab2733afe15c"
---

[Discussion](https://hashnode.com/posts/10-things-you-shouldnt-do-while-running-nodejs-in-production/57bee46e93309a25047c619a)

Comment [10 things you shouldn't do while running Node.js in production](https://hashnode.com/posts/10-things-you-shouldnt-do-while-running-nodejs-in-production/57bee46e93309a25047c619a)

[Stefan Müller](https://hashnode.com/@SM)

[Jul 20, 2017](https://hashnode.com/posts/10-things-you-shouldnt-do-while-running-nodejs-in-production/57bee46e93309a25047c619a/comment/59706a2f107fab2733afe15c)

I would like to add the following topics as what you shouldn't do in production:

-   Serve static assets not minified and gzip'ed (see grunt)
-   Disallow local caching for those static assets
-   Keep access logging enabled
-   Store uploaded files on disk folders instead of a virtual file system like GridFS

[Abhishek Sharma](https://hashnode.com/@0xabhishek)

[Jan 30, 2018](https://hashnode.com/posts/10-things-you-shouldnt-do-while-running-nodejs-in-production/57bee46e93309a25047c619a/comment/59706a2f107fab2733afe15c#reply-5a70bc4fd3e3e6ca6266612a)

Why use gridfFS if the file is not meant to be streamed back to the client and only used for processing? Just curious. We at our startup take in a video and generate meta data off it with AI. Summary, questions, chapters etc. (Everything patented) We need to only process the video and not serve it back. Even if we do need to stream it, I'm sure grid FS won't do any justice. Or would it?