Common Platform Basis

From Cibernética Americana Domain Content Mgt. System (DCMS-X) integrates the following packages ¹ for the parenthesized standard dominion purposes:

  • Eucalyptus (compatibility with Amazon/Ubuntu)
  • Drupal
    (our AOP framework and our vetted 3rd party modules)
  • JBoss (Java app server)
  • NixOS (WFL/DCP is a system application
    of this pure functional GNU Linux)
  • SQL-Ledger ( Chart Of Accounts, ERP core )

We support the folllowing RDBMSes

  • MySQL
  • Oracle Express ¹ or non-free Ora server.
  • Postgres
  • SQL Server ¹²

¹ provided on a case by case basis, others are included in base NixOS stdenv.
² requires 3rd party license.

WFL/DCP, our product unifying the above in our framework which also is the basis of our alternative DNS root service with which you can form your own IPV6 namespace and interwork with others that do in a completely peer-controller and autonomous internet scheme.

Our core platform services are made available in bindings for all of the above and our platform service setup will create a fully functional development prototype of a generic vertical for each distinct enterprise domain set or 'dominion' using same. You can see this in action in our 5 regular IPV4 domains (wik-cso.meansofproduction.dom) from the regular net though access to dominion native services will require a WFL/DCP host.

If we have prepared a development prototype for you it will be at <yourTopLevelDomainName>.dom per the offer letter sent you.

Non Applications

Intend to Resell our Service

I.e. without a royalty to me as its author and provider. You may use the software without restriction but you can't compete with me with my own service. Of course this doesn't apply to applications developed using it, only to the resale of the platform itself without a contract to do so.

Narrow Package Focus

Some people undertaking systems development have been observed to focus on one or another of various packages as the basis of their enterprise implementation. This focus is not without consequences but it cannot be helped because shopping for what you think you need instead of what you actually need is a buyer's prerogative.

What you actually want, we think/hope, is a system that achieves your functional goals (assuming these are reasonable and feasible) and appreciate the value of having those goals realized without tying you to particular packages, but rather presented as intellectual work product which can be adapted to different backends. In general what you may have thought is the 'platform' choice or package du Jour generally has little to do with the attainment (except possibly to hinder it) of such goals. Nonetheless, unless such a choice presents a full blown conflict with the attainment of our TQM goals, we attempt to accommodate it by including support for a large selection of such packages in our framework.

Require Local Control

The project provides you a cloud-computing service where you own the cloud as a software service provided by my automation and which you may move to whatever hosting vendor you wish. Migrations are relatively straightforward and can be performed at will, subject to whatever agreements you have with us or 3rd party providers. You can use our software for servers you physically own and privately manage of course but the common service architecture is not oriented for that.

The intent is to not be involved in hosting as soon as possible so from the beginning the service is oriented to your obtaining and managing the deployment of our service yourself. If you require a personal commitment from me beyond the initial development of your domain application other than on a consulting incident basis then that is a contraindication.