I have been working on a application that up until now has been pure Node. However I am concerned about performance and overhead since the application performs a lot of file system operations (Copy directory, file writes, Remove Directory, zip....)

Everything works like a charm, but I am thinking it would be best to move the file system operations to a RESTful Microservice since synchronous operations is not what Node is really about.

I believe my options are:

  • Python Flask (I have some experience with Python)
  • Ruby Sinatra (More experience than Python)
  • Keep it in Node.

Does anyone else have some experiences or metrics that can share or general advice to dispense?

closed as off-topic by gnat, GrandmasterB, Bart van Ingen Schenau, JeffO, Ixrec May 8 '16 at 22:37

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions asking us to find or recommend tools, libraries, programming languages, resources (including books, blogs, tutorials, and examples), or projects to undertake are off-topic here as they attract opinionated answers that won't have lasting value to others. You may be able to get help in The Whiteboard, our chat room." – gnat, GrandmasterB, Bart van Ingen Schenau, JeffO, Ixrec
If this question can be reworded to fit the rules in the help center, please edit the question.

  • Microservices have some pretty expensive costs associated with them. If I were you, I would keep everything in one app until I proved for sure that I had scalability issues. – dsw88 May 6 '16 at 5:22
  • I would prefer to be proactive. I know Node has certain use cases where it works well, but synchronous/blocking IO operations isn't one of them. – Taylor Ackley May 6 '16 at 15:24