This chapter is from the book
This chapter is from the book
This chapter is from the book
Conclusion
Obviously I'm slightly biased in my feelings about Distribunaut, seeing as how I am the developer of the library. With that said, I feel strongly that Distribunaut makes distributed objects incredibly easy to code, use, and maintain.
The library continues to grow and develop. Its fundamentals were pulled from the mack-distributed gem for the Mack Framework, but the library has grown and evolved much since its origins. Even during the course of writing this chapter, I found several bugs, enhancements, and performance improvements that could be made, so I made changes. The underpinnings of this library have been working hard in several production environments and have proven themselves to be reliable, fast, and easy to use.
Overall I feel that the simple interface, basically just including a module, makes an already easy system for building distributed applications, DRb and Rinda, even easier. Instead of having to write code to look up services, read them, parse them, manage them, and so on, you can use something you are already familiar with—simple Ruby objects.
What does the future hold for Distribunaut? As far as the feature set is concerned, that is hard to say. I try to develop features that will actually be used, not features that I think are cool. What I can tell you for sure is that Distribunaut will continue to be maintained and grown to keep up with the challenges of developing distributed applications.