This is not an innovative or radical idea in the CMS space Drupal has had a solid database-abstraction layer for more than a decade. To accomplish that, WordPress would need to have a database-abstraction layer. That could be done using an installation guide, or a simple constant in wp-config.php. Ideally, WordPress would allow us to choose the type of database during installation. WordPress requires PHP 5.6.20 or higher and a MySQL/MariaDB server. On lower-end servers, it also decreases performance since the same “box” needs to cater to both a PHP PHP The web scripting language in which WordPress is primarily architected. The requirement of a dedicated MySQL server increases their hosting cost and the complexity of installation. These websites don’t always need the complexities of a MySQL/MariaDB database. These are numerous and consist of all the blogs, company pages, and sites that don’t have thousands of users or thousands of posts, etc. On the lower end of the spectrum, there are small and simple sites. Large sites usually implement custom database stacks depending on their specific needs, so are beyond the scope of this proposal. MySQL is arguably only optimal for some of the scenarios: The “mid-tier” range of site types. A database is a structured collection of data where content, configuration and other options are stored. WordPress requires MySQL MySQL MySQL is a relational database management system. However, one aspect of WordPress has never changed, regardless of the increase in WP’s use cases and popularity: The database. Part of the success of WordPress is because it is extendable, hookable, and can be used and tweaked to accomplish almost any task on the web. These sites are usually rarely updated and are essentially static sites with an administration aspect.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |