Extension Delivery Survey Please enable JavaScript in your browser to complete this form.Please enable JavaScript in your browser to complete this form.Installation 1. How do you install your database server in production? *Distribution packages/repository (apt, dnf, zypper, etc.)Vendor official repository + native package managerInternal/company/third-party package repositoryOfficial or custom container image (Docker/Podman)Kubernetes/OpenShift (Helm, Operator, etc.)Binary tarballBuilt from sourceManaged database serviceDownloading and installing it manually (Windows)Using brew (MacOSX)Other1.1. For Other – Please tell us your answer.2. Are you using the same install method for testing/development? *YesNo2.1. Which install method are you using for testing/development?Distribution packages/repository (apt, dnf, zypper, etc.)Vendor official repository + native package managerInternal/company/third-party package repositoryOfficial or custom container image (Docker/Podman)Kubernetes/OpenShift (Helm, Operator, etc.)Binary tarballBuilt from sourceManaged database serviceDownloading and installing it manually (Windows)Using brew (MacOSX)Other2.2. For Other – please tell us your answer.Upgrades 3. How do you usually upgrade your database in production? *apt / dnf / yum / distro package managerVendor repository + package managerReplace/update the container imageConfiguration management / automation — Ansible, Puppet, etc.Build and deploy a new version from sourceReplace the server/VM and migrate or fail overManaged service handles it for usOther3.1. For Other – please tell us your answer.4. When upgrading your database, what is your preferred strategy? *In-place upgradeReplica first, then switchoverBlue/green deploymentNew cluster + migrationWhatever the package/service provider supportsWe don’t upgradePlugins & Extensions 5. How do you currently install/manage plugins or extensions? *Included with the official packagesInstall an additional OS package (apt, dnf, etc.)Download a .so / binary manuallyBuild the plugin from sourceIncluded in our container imageManaged through configuration-management/deployment toolingWe don’t use external pluginsOther5.1. For Other – please tell us your answer. in same using 6. How do you discover plugins/extensions today? *Vendor documentationGitHub / GitLabSearch engineLinux distro packagesBlog posts / social mediaRecommendations from colleaguesI don’t really know where to look7. What would be your preferred ways to install MariaDB plugins/extensions? *apt install mariadb-plugin-xyz / dnf install …mariadb-plugin install xyz (a command line tool)Download and install directly from a MariaDB SQL sessionInclude plugins in the official MariaDB container imageDownload a binary manuallyBuild from sourceOther7.1. For Other – please tell us your answer.8. If MariaDB had a plugin manager, what should it do? *Search/discover pluginsDownload/install pluginsHandle dependenciesUpgrade pluginsCheck compatibility with my MariaDB versionEnable/disable plugins9. Where would you trust downloading a plugin from? *Official repositoryCommunity plugin registryLinux distro repositoryGitHub/GitLab releasePlugin author’s website/repositoryCommercial vendor repository10. What is your biggest concern when installing a third-party plugin? *Is it compatible with my database version?Is it maintained?Is it secure/trustworthy?How do I install it?How do I upgrade it?Will it survive a database upgrade?Documentation/supportSubmit
