Apex Eos™

RAD for micro-services in a distributed and decentralized world.

...

Apex Eos™ is a RAD framework for building lightweight API servers that is transport, language and paradigm agnostic. Moreover, Apex Eos is designed to support clustering and auto-scaling both on your infrastructure and on your favorite cloud. We use it to build the various technologies that are part of the Apex Unify!™ platform, and to power Apex Functor™ for cloud-neutral distributed scripting; but you can use it to build anything you want.

Apex Eos™ is transport agnostic in that it does not impose a particular protocol. Your services can be HTTP-based (SOAP, REST or GraphQL), or provide custom TCP/IP endpoints. Standard TCP/IP protocols like Web Sockets and telnet are also supported out of the box.

Apex Eos™ is language agnostic in that it allows you to choose from a variety of languages for scripting. Embedding Apex Athena™, you can choose from Pascal, Basic and C# scripting flavors, or embedding Apex Muse™ you can elect flavors of popular dynamic, functional languages like Lua, JavaScript and Clojure.

Apex Eos™ is paradigm agnostic with respect to the nature of the micro-service you are building. It can be in support of n-tier, distributed enterprise stacks (at any layer of traditional architectural stacks) or decentralized, peer-to-peer network applications of the future.

Apex Eos™ even lets you choose your language paradigm. Are you keen on statically typed, imperative languages like Basic, Pascal, or C#? Use Apex Athena™. Do you prefer dynamic, functional languages like JavaScript, Lua or Clojure? Use Apex Muse™ for your scripting engine instead. In a polyglot, multicultural world, Apex Eos™ even provides a way to localize your services and applications without fuss.

Like the Homeric vision of the rosy-fingered sun rising in the East, you can count on Apex Eos™ to power your mission-critical services layer regardless of load, as it supports distributed caching, failover, automatic recovery, and a number of other must-have capabilities to ensure high availability, even under expanding and contracting loads.

Learn More

Features

  • Transport agnosticity means Eos™ can support APIs of any kind, not just HTTP-based APIs. It also means that final API responses can be sent via more than one kind of request.
  • Language agnosticity means your developers are not forced to use a new language they don't know, and any developer is likely to know or be comfortable with at least one of them. You can choose between Apex Athena™ or Apex Muse™ or use both for different aspects of a server instance.
  • Paradigm agnosticity means you aren't pigeon-holed into building a particular kind of service.
  • Apex Eos™ provides excellent support for internationalization and localization.
  • Plug-ins to extend Apex Eos™ can be written in native code or scripted, and extend the server in arbitrarily complex or proprietary ways, to meet your specific needs. Apex Eos™ extensions can be obtained or monetized via Apex Agora™.
  • Apex Eos™ can run in development, test or production mode, and offers numerous tools to assist rapid development and deployment to the cloud of your choice.

Benefits

  • Be Your Own Cloud with "Extensibiliy as a Platform" provided by Apex Eos.
  • Modernize any legacy application incrementally.
  • Gradual migration to micro-services and decentralized platforms can happen at your pace and according to the semantics of your enterprise data.