One of the many uses of a microservice is to monitor changes in a filesystem. Files being dropped to an FTP site, text files containing data to be processed, files to archive, the list goes on and on. Most file and directory changes in corporate America will more than likely be those arriving from external vendors to someone in your company, and usually comprise many files coming in and going out on a daily basis. This could be pricing feeds, vendor data uploads, and so on. What if we were to automate what happened when files are received, and the reverse of that, as a result of some action or command, we could also send a file out?

In this chapter, we are going to:

• Build a file monitoring microservice
• Show you how to modify this microservice so that you can mold it into your own based upon the files and directories that you need to monitor