Common Platform Basis: Difference between revisions
No edit summary |
No edit summary |
||
| Line 34: | Line 34: | ||
What you actually want, we think/hope, is a system that achieves your functional goals (assuming these are reasonable and feasible) and has the properties highlighted in the Value Prop(osition). 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 there properties. Nonetheless, unless such a choice presents a full blown conflict with the attainment of our [[:en:Total Quality Management|TQM]] goals, we can accomodate it. | What you actually want, we think/hope, is a system that achieves your functional goals (assuming these are reasonable and feasible) and has the properties highlighted in the Value Prop(osition). 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 there properties. Nonetheless, unless such a choice presents a full blown conflict with the attainment of our [[:en:Total Quality Management|TQM]] goals, we can accomodate it. | ||
<hr> | <hr> | ||
Revision as of 16:36, 8 May 2010
ai-integration.biz Domain Content Mgt. System (DCMS-X) integrates the following packages ¹ for the parenthesized standard dominion purposes:
- Eucalyptus (Open Souce Cloud Framework)
- Drupal (the current stable core, our AOP framework service and our maintained (third pary) module set)
- JBoss (for all Java services)
- NixOS (WFL/DCP is distributed as a derivative of this pure function Linux distro)
- SQL-Ledger ( used for Chart Of Accounts )
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.
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 illustrated in our space over our 5 regular IPV4 domains.
You can see an example of what of an integrated vertical application based on the above is like in the domain name space wik-cso.meansofproduction.biz which is the vertical application supporting the Public Job Shop and our overall enterprise application platform and development support service.
If we have prepared a development prototype for you it will be at <yourVerticalName>.commoditysoftware.org per the setup offer letter sent you.
A caution for non-IT professionals
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 has the properties highlighted in the Value Prop(osition). 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 there properties. Nonetheless, unless such a choice presents a full blown conflict with the attainment of our TQM goals, we can accomodate it.
