Making VLINGO/PLATFORM Possible:
Why members contribute…
My main interest in VLINGO/PLATFORM is to apply the Actor Model on other hardware platforms besides traditional servers, such as mobile. It is interesting to me to validate applying the same principles in mobile development as in backend development. I’m also interested in using DDD on mobile and to experiment in order to find the best way to write Reactive code on mobile devices.
Contributing to VLINGO/PLATFORM means having an opportunity to actually do something about the current state of Java frameworks that try to implement the Actor Model and DDD. I was hooked into the project after a meetup with Vaughn giving an excellent presentation on Reactive programming.
Being a contributor to the VLINGO/PLATFORM has been a wonderful experience for me. I really liked the dynamic nature of the team and eagerness to help each other. I was a big fan of DDD (I still am) and Vaughn is one of my superheroes. I also love contributing to opensource projects. When I got the opportunity to work with Vaughn to implement the actor model and the supporting platform – there was never any second thought about it. As time goes by and the platform matures, I see it shaping up nicely, offering simple APIs to do tasks that are not so simple to implement using traditional approaches. I believe that VLINGO is becoming an awesome tool to help people express their domain logic more easily and cleanly.
For me VLINGO/PLATFORM is the opportunity to make a compelling, easy to use actors framework for Java users. I’ve looked at other systems and they are really uncompelling. On the other hand developers are jumping through hoops to have systems that use a clean, domain-driven design approach. I think VLINGO/PLATFORM begins to fill that gap, allowing developers a practical, type-safe approach that allows them to work very naturally. Software that fundamentally makes programming easier is really compelling to be a part of. And, it’s a great opportunity to work with the talented contributors, and of course with Vaughn.
Contributing to VLINGO/PLATFORM is to support one of the best and most significant open source initiatives in the past years. This platform will widely benefit the software development community by providing a smarter, simpler and easier way to implement distributed, high demand and scalable systems based on the Actor Model, which allows us to experience the power of OOP with no limits.
Contributing means helping to bootstrap a lightweight toolset for Domain-Driven Design that I would be happy to use myself, as the ideas in VLINGO/PLATFORM resonate with my thinking. Now I’m very glad to see the community of contributors growing around the initial core written by Vaughn.
Contributing to VLINGO/PLATFORM is an opportunity to collaborate with a talented team of developers on an incredibly useful and valuable set of tools for building the kinds of reactive, event-driven and microservices architectures that our consulting clients are leveraging for competitive advantage in their businesses.
The future of software development is less about which tool to use and more about which methodology and practice enables developers to collaborate most effectively. With VLINGO/PLATFORM, developers around the world can look forward to working towards creating a culture of learning, with both the tools and the methodology, to effectively bring together the multiple roles involved in all aspects of the software delivery process.
For me, contributing to VLINGO/PLATFORM means to influence the future of software development. The VLINGO/PLATFORM is a toolset that will change how we design software in the long term and how we envision the challenges that will come in the future. IMHO, VLINGO/PLATFORM is the opportunity to set the path to build software that is not only scalable or fast, but to build software that evolves and focuses on solving people problems, not machine problems.
What brought my attention to VLINGO/PLATFORM is a fresh approach to the Actor Model. At the same time, I was also looking for a flexible library to implement Event Sourcing projects on the JVM (Kotlin specifically). Practice quickly taught me that VLINGO would take care of the “boring” implementation details unrelated to the business to let me focus purely on the domain. Since the implementation details are not actually boring, my curiosity led to contributions.
“Everything is an actor.” A statement that resonated with me so deeply that I needed to sit for a day and think about it. After that, I still needed more details and concrete examples. That’s when I found VLINGO and started my contribution! It’s hard but it’s also fun. The team is very talented, hardworking and I learn a lot from them. I am happy and honored to be the part of VLINGO story!
Contributing to VLINGO/PLATFORM for me is an opportunity to learn from an awesome team of developers whose internal conversations are like the continuous editing of a book being written by them. Honestly, because of the way VLINGO/PLATFORM is made it will be one of the main platforms to work with.
When I heard about the VLINGO/PLATFORM for the first time, it drew my interest because it helps to build business-driven solutions using Domain-Driven-Design and the Actor Model. Finally, I can address very complex architectural challenges and still keep it aligned with the business language and requirements! I believe that this is the way we should build complex software.
Being able to help an awesome team shaping VLINGO/PLATFORM and contributing to an important open source effort while learning a ton in the process is an incredible experience. I hope we can provide something that enables developers and enterprises to build more and better reactive systems without getting bogged down by accidental complexity but instead stay focused on their business domains.