Some have asked us to compare the VLINGO/PLATFORM and specific components, such as VLINGO/ACTORS, with frameworks and toolkits offered by various vendors. This is the wrong question because it assumes that our platform is founded on the same motivations as those frameworks and toolkits. The point is, the design of our platform has unique motivations not found in general architecture and programming tools. Our platform starts from completely different first principles. Thus, don't expect us to provide a checklist of feature comparisons, because our checklist would look far different from those that others would produce. Our comparison to the frameworks and toolkits would be unfair to those because we have such unique motivations and they could never align (unless, of course, they would make big changes and copycat).
Most of the other frameworks and toolkits have been created on first-principles of heavy technology solutions, and sometimes those tools include support for actors. Yet, the creators and users of those tools are generally drawn to complexity as if it is a "rite of passage" to deliver deeply complex solutions that require outsmarting the tooling to eventually create working software. Yet, the software rendered from this process is inherently complex at the implementation level. As a result, you would never consider showing it to business people, allowing them to confirm its adherence to the business mental model. This is not to mention that projects routinely fail as a result.
To understand the VLINGO/PLATFORM, you must start from different first principles.
Other than considering our platform, these combined principles are so extremely rare that we consider our tools quite unique.
The VLINGO/PLATFORM was designed for building fluent domain models inside applications and services using a DDD mindset. The VLINGO/PLATFORM is built on actors but is not just actors. It is simple to use. Our tools set shields developers from the underlying complexity. When anyone using our toolset feels uncomfortable with any perceived complexity with our concepts/components, we will give priority attention to simplifying further. Building fluent business-centric domain models is what DDD modeling is all about, and supporting the same fluency in the other components in the architecture of services is an enormous plus. You are not mostly using technical tools, but tools that support readability in a business-technical partnership. Business people should feel completely comfortable reading and reviewing your domain-driven source code with your lead.
The people who will choose to use the VLINGO/PLATFORM or any of the other frameworks/toolkits will be those who gravitate to one or the other set of first principles. That's because the first principles represent two different and likely opposing mindsets. We're committed to the long-term promotion of lightweight architectures with a minimalist mindset. We think that you are reading and will adopt our toolset because you share our values.
To learn more about our support and services, see support, training, consulting, and project development offerings.