Skip to main content

Have you heard of GlusterFS?



GlusterFS is cluster file system that is already tried and tested disk file systems like ext3, ext4, xfs, more to store data. It can easily scale up to petabytes of storage under a single mount point for the user. It is free and open source software available as GNU GPL v3 and some parts as GNU GPL v2.

GlusterFS Servers run glusterfsd daemon to export local file system as volume and glusterfs client process can connect to servers through custom protocol over TCP/IP.  The final volume can be mounted by the client using NFS v3 protocol also.

Why should I use this?
I find it useful typically in cloud environment where I need to scale out. More importantly, when I use AWS cloud, GlusterFS is available as AMI. With standard and premium support subscriptions available from Gluster, the option enables your solution's business continuity by providing disaster recovery capability. Also, Now, I can view file storage service as a commodity. Finally, Gluster is the only highly available storage solution for AWS EC2 AND AWS EBS.

Where do you want to use?
Imagine a scenario where you are designing the solution that involves EC2 and EBS deployment. There is a need for shared file system. The options are plenty, however the simple solution could be to use NFS server. While this is a real solution, You still need to address the problems of production like the following:

1.     What if your storage goes beyond the limit that you envisaged at the time production?
2.     What if your storage infrastructure fails for any reason?

The answer is that the designers will have to provide disaster recovery, high availability and scale out strategies. Alternatively, you can use GlusterFS support on AWS to address all your production needs; In one line, You have outsourced your storage solution support to Gluster support.

However, this comes at cost, and I think, its fair as its Pay as you go model.

Comments

Post a Comment

Thanks for your comments.

Popular posts from this blog

Key to adopt open source product

Friends, I am working on business solution implementation on open source product called Kaltura. Kaltura is a media management solution and has loads of features that compel any business to take a peek into it. More-over this is the only complete end-to-end open source software available to handle digital assets. But it comes with its own head ache. Considering its open source, its understandable. I feel, handling these would ensure you the success in your open source product implementation. 1. In my opinion, before adopting any open source software, build the capability to deal with the inconsistency bundled in the open source software. 2. I would avoid involving external consultants for 2 reasons.      a. I am not sure, they would bring necessary expertise on to table      b. I fear that there would be little ownership, they will not see big picture of my business (neither I am interested to share it all) 3. Alternative to that is to build the tea...
1 comment
Read more

Secure your application on cloud

Handling sensitive data Define sensitive data for your application. Classify as sensitive data and confidential data. Sensitive data is something like password, credit card account number, something that you should not compromise at all. Confidential data could be your customer’s health record, something that requires your permission before its usage. So, you need to define sensitive data in the context of your application. There are many ways to protect the sensitive data in transit; the easiest way is to use SSL. This is nothing different than handling sensitive data in any traditional application.   However, make sure you apply this rule while designing your application for cloud deployment. Alternatively, you can encrypt the sensitive data and transport. Be noted that any kind of protection you design, will have implications on performance. However this is ignorable considering the nature of sensitive data. If you just want to protect your data from being tampered du...
Post a Comment
Read more

Object orientation and Service orientation

Object orientation is all about modeling the real world information mainly through encapsulation, abstraction, polymorphism, containment, inheritance and so on. In simple words, an object contains the data structures and methods to change the content state. A typical OO run-time manages the life cycle of objects. You can create as many objects as required as long as the run-time does not over run its memory. Service orientation requires you to encapsulate a process. The operations of a services are interaction points with the particular process. Data structures are the arguments for these operations. Service run-time shall validate the correctness of the process. Service can have multiple invocation instances, not multiple instances of service itself. Example: TrainTicketBookingService involves a process. - Check the train timings //  interaction point - Check the seat availability // interaction point - Issue ticket // interaction point There could be many ticket...
Post a Comment
Read more