Hello, Thanks for your feedback, that’s why these communications are for.
Why only PostgreSQL was announced: - The obvious reason is it is easier to only handle one kind of database than two to focus on it instead of using an ORM. - Also, even if you’re still able to install and tweak sogo as you want, one of our goals is to emphasis the containerization of sogo: Providing an official image, a docker-compose or a helm package for Kubernetes. In that way, redis and postrge are directly embarks with SOGo. - As we chose PostgreSQL only, we are using postgre-only things like JSONB or its full search/indexes methods. But you can achieve the same, in other ways, with MariaDB. However: Ultimately, there is nothing that forbids SOGo 6 to use MariaDB. Besides, we aim to make SOGo code modular. Meaning, even if right now we’re only supporting PostgreSQL, the code is ready to support MariaDB. It “only” needs a MariadbManager that inherits the right class and implements the rights methods. No need to change/break and recode other parts of SOGo. Your feedback is important because we, Alinto, are in the same use case as you Felix. In our product with SOGo, we use MariaDB for SOGo and the other services. And this is not a problem for us to have two databases. But, as maintainers, we don’t want to make a SOGo that only fits us. If the community says that supports for MariaDB is important, we will keep it. That’s also why those updates on SOGo 6 will be more frequent to share with you our vision and get your feedback like this! So? Mariadb support is back on the menu folks Now please nobody tells us they absolutely need Memcached because Redis is not negotiable Cheers, -- Quentin Hivert || Alinto || R&D Lead Developer 19 Quai Perrache 69002 Lyon www.alinto.com <http://www.alinto.com> From: [email protected] <[email protected]> On Behalf Of Felix Bachofner Sent: mardi 30 septembre 2025 00:43 To: [email protected] Subject: Re: [SOGo] [Marketing Mail] Re: Latest updates on SOGo Hello Quentin, et al: While I am thrilled to hear there is strong forward progress on SOGo6, as a company we are very distraught to hear that support for MariaDB/MySQL is being dropped. MariaDB support was one of the key elements that caused us to recently adopt SOGo -- as opposed to competing options which rely exclusively on PostgreSQL. PostgreSQL is a very impressive DBMS, but it is not necessarily a good fit for all enterprises. For one, this decision will now cause enterprises having standardized on MariaDB/MySQL to ADD an element to their technology stack for a single purpose. Adding another DBMS daemon to a host arguably "steals" compute cycles and other resources from other daemons, adds cognitive and perhaps other types of sysadmin and hardware "complexity" and a host of possible other downsides. Given that MariaDB recently seems to have virtually ALL the functionality of PgSQL, could you speak a moment to why this design decision is being made? Especially with regard to technical requirements, for example? After all, working with MariaDB/MySQL on Python seems just as trivial as it is with PostgreSQL. [ But feel free to specifically dispute that if you believe I am wrong. ] ALSO, is there currently any concept that adding "back" MariaDB connectivity would be considered for version 6.x? If not, I fear SOGo will lose quite a lot of adopters. Thanks in advance for your more detailed insights into this decision. Felix On 9/29/25 08:30, qhivert ([email protected] <mailto:[email protected]> ) wrote: Hello, Yes there will be migration scripts from SOGo 5 MAriadb/Postgresql to SOGo 6 Postgresql. -- Quentin Hivert || Alinto || R&D Lead Developer 19 Quai Perrache 69002 Lyon www.alinto.com <http://www.alinto.com>
