Common Platform Basis: Difference between revisions
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
</ul> | </ul> | ||
</td><td> | </td><td> | ||
While we have used many, the RDBMSes we mainly use these days are MySQL, Postgres, and SQL Server, others as required. Note that some packages we use require MySQL or Postgres and both are standard required components of our base platform service. | While we have used many, the RDBMSes we mainly use these days are MySQL, Postgres, and SQL Server, others as required. Note that some packages we use require MySQL or Postgres and both are standard required components of our base platform service. SQL Server integration is performed on a case by case basis.<br><br> | ||
Development environments contain simple db instances, production ones can use clustering, replication, etc. | |||
</td></tr></table> | </td></tr></table> | ||
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 with our 3 regular IPV4 domains. | 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 with our 3 regular IPV4 domains. | ||
Revision as of 08:50, 7 June 2007
Domain Content Mgt. System (DCMS) integrates the following packages ¹ for the indicated standard purposes and can be for key milestones in the to initialization of your dominion (enterprise domain(s)):
|
While we have used many, the RDBMSes we mainly use these days are MySQL, Postgres, and SQL Server, others as required. Note that some packages we use require MySQL or Postgres and both are standard required components of our base platform service. SQL Server integration is performed on a case by case basis. |
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 with our 3 regular IPV4 domains.
You can see an example of what of an integrated vertical application based on the above is like with the name wik-cso.meansofproduction.biz which is the vertical application supporting the Public Job Shop and our overall enterprise application service.
If we have prepared a development prototype for you it will be at <yourVerticalName>.commoditysoftware.org per the setup offer letter sent you.
Some people focus on one or another of these 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 Total Quality Management goals, we can accomodate it.
¹ Among others.
