6e218adc1d
The SERVER_REF and DCB members of the Backend class are now private. Access to the stored SERVER_REF is provided with the backend() function. No accompanying setter function is provided as the backend server should not change during the lifetime of the session. The creation of the internal DCB is hidden behind the connect() function. It simplifies the process of connecting to a server by removing the need to manually do the bookkeeping of the server reference connection counts. Access to the DCB is provided by the dcb() function. The closing of the backend is done with the close() function which contains the code that was previously in closeSession. If the backend isn't closed when the destructor is called, it will be done automatically. This should prevent connection leakage. The pending command queues and the methods used to write them are now also internal to the backends. They are simple wrappers around dcb->func.write and the interfaces provided by the Buffer class. The mapping command queue is still public. It needs to be combined with the generic command queue.
MaxScale by MariaDB Corporation
The MariaDB Corporation MaxScale is an intelligent proxy that allows forwarding of database statements to one or more database servers using complex rules, a semantic understanding of the database statements and the roles of the various servers within the backend cluster of databases.
MaxScale is designed to provide load balancing and high availability functionality transparently to the applications. In addition it provides a highly scalable and flexible architecture, with plugin components to support different protocols and routing decisions.
MaxScale is implemented in C and makes extensive use of the asynchronous I/O capabilities of the Linux operating system. The epoll system is used to provide the event driven framework for the input and output via sockets.
The protocols are implemented as external shared object modules which can be loaded at runtime. These modules support a fixed interface, communicating the entries points via a structure consisting of a set of function pointers. This structure is called the "module object".
The code that routes the queries to the database servers is also loaded as external shared objects and are referred to as routing modules.
An Google Group exists for MaxScale that can be used to discuss ideas, issues and communicate with the MaxScale community.
We're also on the #maria and #maxscale channels on FreeNode.
Please report all feature requests, improvements and bugs in the MariaDB Jira.
Documentation
For information about installing and using MaxScale, please refer to the documentation. The official documentation can be found on the MariaDB Knowledge Base.
The module and configuration documentation can be found in the Documentation directory of the source tree.
Contributing Code
Read the Contributing page on the wiki for more information on how to do pull request and where to do them.