Best practice for Open Source DBs
For a successful adoption of Open Source, a number of Best Practices have been developed on the basis of
real-life software projects. This includes the different treatment of challenges in Software Engineering,
operations / DevOps, and continuous improvement of the database application services.
Architecture & High Availability
-
Open Source databases offer very high levels of High Availability, allowing for enterprise-ready compliance and failure-safety
-
Possible High Availability architectures offer e.g. full data synchronicity, semi-synchronous replication setups, as well as various master failover mechanisms and modalities
-
See also our High Availability page
Software engineering
-
Open Source empowers a significantly agile culture of improving, experimenting and competing by solution quality, not by price
-
Several limitations of legacy commercial DBMS often do not exist in Open Source, e.g. CPU-based licenses
-
Modern architectures allow for quick automation ofexisting or migrated DB topologies
-
Consolidation of instances helps to reduce costs
Performance tuning
-
Relational Open-Source DBMS like MariaDB, MySQL, PostgreSQL offer full range of indexing, sharding, partitioning as well as very extensive server tuning capabilities
-
In general, proper indexing allows for optimizing your application by vast orders of magnitude , e.g. from 5...10 secs to 30..40 milliseconds per request
-
See also our performance page
DevOps & operations
-
As in any other software product, training of your team members for operating Open Source databases is essential
-
We can assist you with enhancing the skills of your existing DBA team in order to deal with the new database infrastructure based on Open Source
-
We carefully help your team to prepare for switchover from old to new database