Apache Archiva vs. MariaDB Platform vs. SAP Adaptive Server Enterprise (ASE)

Well suited for small organizations to medium-sized teams/organizations. Apache Archiva is well suited for:

• It acts as a central repository/proxy of the artifacts generated and used by the teams.
• It provides control on which open source repositories can be utilized by the team.
• Saves network bandwidth by reducing outbound traffic.

Apache Archiva is less appropriate for organizations where immediate support/bug resolutions are required.

Incentivized

• Applications where the users need [to] execute many short queries.
• With new storage engines such as Aria, which allows to replace MyISAM with some improvements, and XtraDB, which evolves InnoDB.
• To fuse the legacy features with the features available in NoSQL databases.
• Connection management, which allows multiplying the number of concurrent accesses.
• New clustering engines, such as Galera, which allow interesting possibilities for Cloud adoption.

Incentivized

We use this for an inbuilt security management system, where it performs well in a scaled setup with a large volume of live data with high availability. Also, the performance is up to the mark for the large statement flow. From a DBA perspective, a lot of parameters need to be fine-tuned for the specific environment needs, which can cause overhead. Expertise is limited, and the learning curve is steep for the SAP ASE.

Incentivized

• It's an open source project and therefore saves cost.
• It allows exchange of artifacts/libraries between different teams.
• It allows managing internal and external repositories with ease.

Incentivized

• Simpler learning curve. MariaDB is a cleaner, simpler system that is (IMO) easier to learn and easier to manage effectively than many other database systems.
• Lower hardware requirements. After migrating to MariaDB from another database software system, we find that our hardware needs have substantially decreased.
• MariaDB support is very responsive. It's like they actually care. On the few occasions we've run into technical issues, support has always come through with what we needed. Once it was showing me a relatively new feature the server supported that I wasn't aware of, that, once I was able to properly make use of it helped me resolve a serious production performance issue.
• Architectural flexibility. As an example, the ready availability of synchronous (Galera) versus asynchronous replication schemes without being locked into one of the other by enormous technical complexity or punitive licensing, allows the customer to find what really works best for their needs.

Incentivized

• High availability and reliability.
• High performance.
• Monitoring of threshold based events.
• Security at multiple levels.
• Query plan optimization.
• Lock management.
• Access to HANA.

Incentivized

• Muti-tenancy was hard to achieve.
• UI can be improved. Its seems bit dated.
• It is a bit tricky to setup.

Incentivized

• Driver Support - Some third party applications use database drivers that cause unexplained slowness with MariaDB. This can be worked around by using the MySQL drivers, but it's not clear what causes the problem in the first place.
• Support - While online communities are helpful in diagnosing problems, there isn't as much professional documentation/support available for MariaDB as some of the other major database options.
• Data Visualization - It would be helpful if there were more built in options for analyzing statistics and generating reports.

Incentivized

• A quick button for devs to switch instances into a dev mode (eliminating logs, and such).
• Licensing is far too complicated. Simplify pricing.

Incentivized

Our licenses are perpetual. It is the support that we will be renewing. We will renew because we continue to use and receive value from the product.

Incentivized

MariaDB is very usable and stable to be used in production settings as an alternative to MySQL. The shortcomings of SQL are present but well understood in the community, and if the decision were to be made again, I would choose MariaDB over MySQL on future projects.

Incentivized

Well-suited in the security domain, high performance, and low latency of the DBMS. In terms of the DBA perspective, a dedicated monitoring tool (Cockpit) helps a lot in terms of managing the database, which helps in identifying bottlenecks during performance issues. Also, it helps us to send custom alerts related to Database activities.

Incentivized

We have launched several inquiries to MariaDB support and they have always responded very quickly and have not been tutoring for the duration of the incident/problem.

Likewise, they want to hold constant meetings with the client to get their opinion as well as how they can help.

I see a very human support and concerned about the customer.

Incentivized

Incredibly responsive, saving us countless hours in troubleshooting.

Incentivized

• Apache Archiva is a great choice for organizations with a limited budget.
• Alternatives are expensive to acquire Archiva comes offers REST API(s) which allows the creation of customized UI.
• With Apache Archiva, it is easy to manage the remote proxy repositories.
• RBAC helps with managing user access to the repository.
• Configuration can be achieved using UI and stored in archiva.xml.
• Backup of configuration is quite simple.

Incentivized

MariaDB stacks up the the competition just fine. Due to is ture open source nature we do not have to worry about licencing and spending money on nothing. Moreover, MariaDB does everything that we need to get done. We can run data that is a million rows or many smaller projects on the same environment with little overhead. One of the best features that MariaDB has is the ability of backup or dump data to standard text sql statements. That was one of the reasons why we choose MariaDb because it makes backups or transferring data a snap

Incentivized

Incentivized

• The impact of Apache Archiva on ROI has been positive. Since it is open source. It is free.
• It has allowed teams to store artifacts centrally, thus leading to a reduced need for multiple servers
• Security audits can be easily performed on the artifacts.

Incentivized

• Low CAPEX if you have a team that use open source software day by day
• Medium OPEX if you have a team that use open source software day by day
• Perfect to use in academic ambient to support researchers and students

Incentivized

• Positive ROI.
• Ease of use with minimal training required to write high performance SQL (assumes a knowledge of SQL already).
• Ease of database administration.
• Sometimes upgrades can be difficult.
• Changing platforms can be difficult (changing say from SPARC to Intel).
• Changing operating systems can be difficult (changing from Solaris to linux).

Incentivized