The solution is useful for storing details of our internal projects.

We are in the process of reorganizing the services that currently exist within the university on our premises. Our plan is to transition everything to the cloud. We initiated this transition using Azure and started implementing AWS for the learning system. Currently, we're in the prototype stage and haven't reached the production phase yet.

My company's clients use Amazon EFS (Elastic File System) for NFS.

I use Amazon EFS to teach about this technology. I create courses and projects about EFS. I'm teaching my students how to work with various AWS services, such as EC2, S3, Glue, and Athena. 

We use the solution for deploying large serverless functions. It helps run Lambda functions with large dependencies like Tensorflow.

I'm a consultant, and I architect solutions for customers by using Amazon EFS in other Amazon products. I am using EFS based on NFS version 4.

I have a customer who is using around 20 Linux servers hosting MySQL databases. Their storage is in Amazon EFS. So, around 20 Linux servers are connecting to Amazon EFS.

The solution is quite stable. There were some bugs at a point but after we patched it, it was stable. 

We need our storage to expand based on demand but storage is a bit costly. So we start with a smaller amount and, as we grow, we use EFS on demand. It manages our costs.

We can predict our storage which comes over a period of time. So it is better that we start small and it automatically helps us grow.