No Comparison

Our first principles highlight our unique motivations and goals.

Some have asked us to compare the VLINGO XOOM platform and specific components, such as XOOM 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 philosophies and motivations as those frameworks and toolkits. The point is, the design of our platform has unique philosophies and motivations not found in general architecture and programming frameworks. Those generally solve technical problems, but introduce other complexities due to the technology-only mindset on which they are based.

Green Abstract
One of a kind is by definition one of a kind.

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 philosophies and motivations that the others 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, but most don’t. 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 framework 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 XOOM platform, you must start from different first principles.

  1. Simplicity
  2. Model fluency
  3. DOMA-enabler and DDD-friendly
  4. Rapid design and delivery

Other than considering our platform, these combined principles are so extremely rare that we consider our tools quite unique.

The VLINGO XOOM platform was designed for building fluent domain models inside applications and services using a DDD mindset, and in record time. Our platform is built on actors but is not just actors. It is simple to use. Our SDK shields developers from the underlying complexity of modern architectures. 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 XOOM platform or any of the other frameworks 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 DOMA-based 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.

More to explore

Reactive DDD: Modeling Uncertainty

Domain-Driven Design supports reactive architecture and programming. Still, reactive introduces uncertainty. Back in 2003, the way that Domain-Driven Design was used and

Scroll to Top