MySQL on Ubuntu Reviews

MySQL on Ubuntu serves as our primary database for our application, storing app data such as user accounts and product catalogs. We use MySQL on Ubuntu for transactional applications within our product called Hiretual, which has two sides: enterprise and candidate. We deploy it in both areas.

MySQL on Ubuntu is an open-source relational database management system that stores data in tables and columns. It is free, open-source, and very stable for servers with easy installation for our production application.

MySQL on Ubuntu demonstrates excellent stability and works very effectively with our Node.js backend. It is memory and disk efficient while providing regular security and bug updates.

From an organizational perspective, MySQL on Ubuntu offers significant advantages. The cost is excellent since it is open-source with no licensing fees. The reliability it provides is outstanding with minimal crashes and exceptional stability. The improved application performance is notable with fast query searches and superior indexing properties.

MySQL on Ubuntu saves considerable time and reduces operational costs through decreased database licensing fees as an open-source solution. We achieve a thirty to sixty percent reduction in infrastructure costs. System uptime is excellent in our stable Linux environment, reaching 99.9 percent uptime. Application performance improvements are substantial, delivering twenty-five to forty percent faster API responses when queries are optimized according to our needs.

Performance improvements and security enhancements could be implemented for MySQL on Ubuntu.

From a feature perspective, service management capabilities could be improved. While MySQL on Ubuntu runs as a managed service with auto-start on boot and auto-restart on failure capabilities, performance could be better, particularly in memory and thread handling on Linux. InnoDB buffer pool optimization should be enhanced. Automatic crash recovery should be considered an improvement, and write-ahead logging is another feature that could be advanced.

I have been using MySQL on Ubuntu for two or three years in our product.

MySQL on Ubuntu demonstrates excellent stability because it is Linux-based. Ubuntu provides very long uptime periods. MySQL on Ubuntu uses the InnoDB engine, which has ACID properties integrated, and the process management is very effective.

MySQL on Ubuntu provides excellent reliability for scalability needs. The application can grow into multiple vertical servers through vertical scaling. Read replicas exist, allowing us to separate read and write operations accordingly. Indexing and query optimization with MySQL on Ubuntu are excellent and work quite effectively for our application.

Server scalability with MySQL on Ubuntu is strong. Data security and compliance are important considerations, particularly for sensitive data. When we require predictable performance, MySQL on Ubuntu can be effectively utilized. Cost control with MySQL on Ubuntu is important as it allows us to avoid expensive licensing databases and ensures long-term predictable costs.

MySQL on Ubuntu is deployed in our private cloud. We have purchased MySQL on Ubuntu through the AWS Marketplace. The review rating for this product is ten.

My main use case for MySQL on Ubuntu is integrating it via AWS cloud, and we are working on the Python side as well. All Python apps run on Ubuntu, so for the back end, we set up the database using MySQL. Those databases we integrate with Python.

A quick, specific example of how I use MySQL on Ubuntu in one of my projects is based on an e-commerce platform. We have an e-commerce application that we are working on. Specifically, it was designed in the Python language. We have a simple cart process, checkout process, payment gateway, and all these things integrated. All the database is handled and we are using third-party web services for payment. Basically, all this content and all the data are stored in a MySQL on Ubuntu database. Because it is an e-commerce application, we use third-party web services, and those things we store in MySQL on Ubuntu.

For the main use case, whenever we are using MySQL on Ubuntu, mostly we are using it for the web application for different properties such as user account, login system, profile, comment, and post. We are using the e-commerce application and we use MySQL on Ubuntu to store all types of transactions. We support data consistency. Then we have order processing. If we make the reliable order processing, in that case we are using that as well. It will store the user data, product data, order data, payment data, and most importantly, inventories. These are the main features I can consider.

The best features MySQL on Ubuntu offers mainly include the storage engine, such as the InnoDB storage engine they are providing. Because it is the default engine on Ubuntu, I can say that it is rock solid on Linux and handles crashes very well. Whatever crashes we get, it will handle them very well. The InnoDB storage engine I can say is a base feature. Another thing is strong Linux integration I can see in Ubuntu. They provide features such as system service management, native package support via apt, and easy automation we can do. I consider Ubuntu as a very fast operating system. From the point of view of performance and speed, MySQL on Ubuntu is very fast. Basically, it will optimize for the Linux kernel, efficient memory usage, and excellent indexing. Those features we can elaborate on. It will be used for whatever heavy workload because in an e-commerce application, generally sometimes peak time occurs. Some events are going on, and at that time, sometimes peak loads come on the system. MySQL on Ubuntu combination handles it in a very efficient way. Another thing I can say is that why Ubuntu plus MySQL on Ubuntu is popular is easy maintenance. Easy installation and maintenance they provide. Also, it is scalable, very much scalable. Additionally, providing security is the main feature I can consider, along with user management.

MySQL on Ubuntu has positively impacted my organization because whatever features I mentioned here are the best features we can use in our organization. For that, we get some benefits such as cost reduction. The result is highly reliable and stable because both MySQL on Ubuntu and Ubuntu are both open source. We can save a lot of money in that case. Because there is no licensing fee and no infrastructure build-up cost, we get the benefit. Another thing I already mentioned is that high reliability and stability they provide. They provide long-term support. MySQL on Ubuntu InnoDB crash recovery features we can mainly use in our organization, maturity of the Linux kernel. Those things we are using. Faster time to market I can say, quick installation, easy configuration, and large ecosystem they provided for our business growth because we are dealing with the e-commerce client. There is a large number of chances that their business can get growth. In that case, we can have scalability with MySQL on Ubuntu plus Ubuntu. Then, it provides strong security and compliance because of role-based access, encrypted connections, and Ubuntu security updates. Those help us. Then developer productivity, I can say, excellent performance for the core workload, easy maintenance and operation, and vendor independence. Those kinds of features we can use in our organization and we take the benefits.

MySQL on Ubuntu can be improved in a couple of things in my mind. I can consider performance-wise, scalability-wise, reliability, availability, security, and operational simplicity. Right now it is good enough for ourselves or our organization. But if it is considered from a scalability perspective, currently, MySQL on Ubuntu scales fairly well. Write scaling is hard and manual sharding is required. In that case, what we can improve is native sharding support, better distributed write handling, and easier multi-primary setups.

For performance optimization, I can say currently the limitation is the required expert tuning. The default configuration is conservative. What we need to do in that is auto-tuning based on the hardware, better index recommendations, and smarter query optimization.

Another point is high availability. Currently, what happens is that replication setup is complex. If you make the setup but if you want to replicate it, it will be complex. What we have to do is build in automatic failover, easier cluster setup, and faster recovery time.

The fourth thing is security enhancements. Currently, whatever security is set up is manual. Misconfiguration risk is there. What we can improve in that is secure-by-default configuration and mandatory SSL in production because SSL is very important nowadays. This thing we can improve. Stronger password policy by default. For the security perspective, we can provide a stronger password policy by default.

For recovery and backup simplicity, I can say that currently, we need scripting for the backups and recovery testing is a manual thing. What we can do here is built-in backup scheduler. We can run one scheduler and every day it will take the backups. If we can have it, it will be great. One-click restore and automated recovery validation. Those things we can improve.

Another thing is observability and monitoring. Currently, what happens is limited built-in visibility and external tools required for that. What we can do here is provide native performance dashboard, query heat maps, and bottleneck detection. Those things we can improve.

Another thing I can consider is at the Ubuntu level. Because if you consider, the OS and DB configuration is disconnected and kernel tuning is also manual. What we can improve in that is DB-aware kernel tuning, better file system defaults for the DB workloads, and pre-tuned DB server profiles.

I can say cloud-native enhancements. Right now we are working on a traditional architecture and manual cloud optimization. It would be better to have Kubernetes native auto-scaling and storage-aware tuning. Those can improve my area for that.

Another thing is developer experience. Debugging a query is hard. Currently, if we are running on Ubuntu and code something, there are no other tools we are using. Debugging is very hard. Also, error guidance is limited. We can say that a clearer error message, query rewrite suggestions, and schema change safety checks by default. Those kinds of improvements we can do.

I can say I mostly covered the improvements needed for MySQL on Ubuntu, but one thing I can say is that there is also some limitation on the governance and compliance base. Auditing needs configuration. Some configuration we need to read. Compliance reporting also is manual right now. We can improve that with built-in audit templates, compliance-ready modes we can provide, and easier data masking we can do. Those things we can add also.

I have been using MySQL on Ubuntu for seven-plus years, and mostly we have integrated MySQL on Ubuntu. It basically provides different kinds of features. I can say that for seven-plus years I have totally worked on MySQL on Ubuntu.

MySQL on Ubuntu is stable. Even if it is an open-source tool, it is very stable. In real-world production use, it has been consistently proven across startups, mid-sized companies, and large organizations as well. Because it is on Ubuntu, it is highly stable.

MySQL on Ubuntu is scalable. We are dealing with an e-commerce application. That is why we have a heavy load transaction workload. Sometimes it will increase the demand and we need to scale. I can say that MySQL on Ubuntu can be scaled. I can scale it here without any hesitation.

Sometimes, we need to reach out to customer support for MySQL on Ubuntu because of some setup configuration issues. They provide strong and reliable support because it is an open-source community. We also get some solutions from online, but sometimes we need to reach out to them. I can say that it has got strong support and they are available 24/7.

Positive

Previously, in my first company, I used Oracle Database and Microsoft SQL Server. I tried Oracle Database on Ubuntu. I can say that there are some limitations, such as the extremely high licensing cost Oracle Database provided, costly audits and compliance pressure, and complex administration. Those things are overcome by MySQL on Ubuntu. Ubuntu plus MySQL on Ubuntu removed the licensing fee, first of all. We can do similar transactions with InnoDB, and it has much lower operation overhead. That is the reason I just moved on to this system.

Regarding my experience with pricing, setup cost, and licensing for MySQL on Ubuntu, I can say that it is a free tool. MySQL on Ubuntu pricing is zero licensing cost. Because the community edition is provided for free, I have a great experience with that. We do not have to pay anything for that. But if you are going with the Enterprise edition, there is some paid support provided for that. And if there is also Ubuntu licensing we need, such as if we are increasing the servers. But whatever free installation and all, it will cover everything. I am not going on the premium side, but it is good. The second thing, on the timing base, it will not take much time to configure. On the Ubuntu, I can say the setup cost is also limited because we are using a less amount of resources.

I have seen a return on investment with MySQL on Ubuntu because I can say that everything we can do here is save money and time, and even we are using a small number of team to handle it. Because if we are using a small number of team to handle it, it will definitely save the money. This infrastructure is not very complex, so it always saves the time as well. I can consider every parameter is positive.

I think we can reduce licensing cost saving with MySQL on Ubuntu because there is no cost. In that case, we are also saving time because other providers have additional costs. I can say organization-level saving as well. A small company needs only 5 to 10 servers. A mid-sized company needs only 50 servers. For a large company, we need only 500-plus servers, approximately. In that case, we are saving some money in each case. Then support and maintenance saving because it is a very easy support, free support provided, and maintenance is also very cheaper. Another thing, hardware efficiency saving, I can say that because it runs well on smaller machines with efficient memory usage. Linux has a lower overhead than Windows. This impacts our 20 to 30% of servers needed, fewer servers needed for that. We can save lots of dollars on that. Downtime cost reduction is also there. Cloud cost saving is also there. Cloud means that generally, we are using the cloud, but this is a smaller system, so it will reduce the cost for the AWS cloud also because we are using the AWS. Those are, I can say in the short term, the number of servers we can save, on-prem or cloud, we can save.

Before choosing MySQL on Ubuntu, I evaluated other options such as PostgreSQL, Microsoft SQL Server, Oracle Database, NoSQL database, and cloud-managed database. Those things we considered before that, but I recommend MySQL on Ubuntu, which is profitable to our organization. That is why we are going with it.

If you guys are considering any scalable application such as e-commerce or anything, and if you need the secure configuration with the low cost, I can totally recommend to you to use MySQL on Ubuntu. I would give this solution a rating of 7.5 out of 10.

MySQL on Ubuntu served as the primary storage and management system for structured financial data extracted from documents in our financial mapping system. We stored trial balances, entries, account classifications, and mapping rules that our AI models would query and process. When we extracted financial line items from documents using OCR and LLMs, we would validate them against the database schema, store and clean the data, and use those records to feed into our compliance workflows for chartered accountants.

MySQL on Ubuntu fulfilled three critical roles in our workflow with AI models and compliance. First, it provided reliability by ensuring extracted financial data was persisted correctly and was not lost between processing steps. Second, it provided structure through our compliance workflow for UAE corporate tax and IFRS requirements with static schema validation, so MySQL enforced data integrity on classified accounts and trial balance entries. Third, it enabled queryability by allowing our financial mapping system to rapidly retrieve account classification and historical mapping during processing, which MySQL handled efficiently at scale. Without it, we would have been managing data across files with no guarantee of consistency.

The combination of MySQL on Ubuntu with our structured output parsing from LLMs was crucial to our implementation. We would use n8n workflows to extract financial data via GPT, then translate and store it in MySQL before feeding it downstream to compliance checks. This separation allowed us to audit what the AI extracted, catch parsing errors early, and maintain a clean historical record for chartered accountants to review. MySQL was not just storage; it was our quality gate and audit trail for the entire workflow.

The most valuable features MySQL on Ubuntu offers for our use case are reliability and ACID compliance. We needed transactions to guarantee that financial data remained consistent, particularly when multiple compliance checks were running simultaneously. Performance was another essential feature, as indexed queries on large trial balance data sets had to be fast for real-time processing. Scalability through replication and backup features enabled us to handle growing volumes of financial documents without losing data. Additionally, Ubuntu's stability as an operating system meant our database infrastructure remained predictable and dependable.

MySQL on Ubuntu has positively impacted our organization by enabling our financial mapping system to scale reliably. We transitioned from processing dozens of documents manually to handling hundreds through automated pipelines, all supported by MySQL's structured data storage. For the chartered accountants using our system, this meant faster compliance reporting and fewer manual errors in trial balance classification. We significantly reduced data loss risk through our backup and replication strategy, which gave stakeholders confidence in the system's reliability. On the operational side, MySQL's performance on Ubuntu meant our compliance workflows completed faster, with directly improved turnaround time for financial document processing. Those measurable improvements in speed, accuracy, and reliability validated the system for our stakeholders.

Several pain points regarding MySQL on Ubuntu come to mind. First, its handling of large JSON documents was sometimes cumbersome. We stored structured financial data and occasionally had to denormalize or use workarounds for complex nested JSON queries. Native JSON indexing and better query performance on JSON fields would have helped us avoid some of those compromises. Second, the lack of native full-text search optimization meant we had to layer additional tools on top for searching financial document metadata and account descriptions efficiently. Third, horizontal scaling presented challenges, as MySQL's sharding is not as seamless as some newer databases. As our financial document volume grew, we had to be deliberate about partitioning strategies rather than it scaling automatically. Those are not deal-breakers, but addressing them would make MySQL even stronger for data-heavy AI workflows.

Another consideration pertains to concurrency handling during peak processing windows. When we had multiple n8n workflows running simultaneously and all writing to MySQL, we occasionally encountered lock contention issues. Better built-in handling of high concurrency writes would have resolved that without requiring us to manually tune connection pooling and timeout settings. Additionally, the operational overhead on Ubuntu itself presented challenges. Monitoring and tuning MySQL performance require substantial DevOps knowledge. A more self-tuning approach to index optimization and query execution would reduce that burden, particularly for teams that focus more on application logic than database administration. These represented realistic friction points we managed, but nothing that made us want to abandon MySQL.

The span of my involvement was approximately one and a half years, though the exact timeline was integrated with our broader full-stack development.

MySQL on Ubuntu proved to be very stable for us in production. Our financial document processing pipelines ran continuously, and we did not experience unexpected crashes or data corruption issues. The system reliably handled concurrent workflows from multiple n8n automation jobs without dropping connections or losing data. Uptime was solid, which was critical since chartered accountants depended on our compliance output on schedule.

MySQL on Ubuntu scaled reasonably well for our organization. As we increased the volume of financial documents being processed, moving from dozens to hundreds, MySQL handled the growth in data load without major performance degradation. We implemented indexing strategies on frequently queried fields such as account classification and trial balance entries, which kept query performance strong even as the data set grew. That said, there were limits. Horizontal scaling required careful planning around data partitioning rather than scaling automatically. We had to be intentional about the sharding strategies as volumes increased, which is not as seamless as some new distributed databases. For the scale we operated at, MySQL on Ubuntu met our requirements.

MySQL on Ubuntu's customer support has been mainly through community forums, Stack Overflow, and official MySQL documentation. MySQL itself does not have direct paid support as it is open source. We also relied on Ubuntu's community resources since the operating system side was part of the equation. For specific issues around replication lag or JSON query optimization, the community documentation was usually sufficient to find answers. I did not personally escalate to any formal support channels, but the community sources were accessible, and the issues we encountered were common enough that solutions were already documented. That is both a strength and weakness.

I do not have exact metrics to quote precisely about improvements, but I can speak to what I observed directly. We moved from processing financial documents in hours with manual intervention to doing it in minutes through automation. On the compliance side, our IFRS disclosure flows were processing structured disclosures accurately without data corruption. Without MySQL, this would have previously required multiple manual verification process passes. The audit trail MySQL provided also meant zero untracked data losses in production, whereas before we had occasional synchronization issues across systems. Those were the tangible wins I observed.

My advice for others looking into using MySQL on Ubuntu is to first ensure your use case actually needs a relational database. MySQL's strengths are structure and ACID compliance, so it is a solid choice if you need consistency for financial data or anything that requires it. Second, invest upfront in proper indexing strategy and query optimization. We learned that the hard way with some of our financial queries; poor indexes kill performance fast. Third, plan your scaling strategy early. Do not assume you can shard easily later. Design your schema with growth in mind from the start. Finally, if you are on Ubuntu, you gain a stable, well-supported operating system pairing, which makes operations smoother. Just know you will need some DevOps or database administration capability to keep it tuned as you scale.

MySQL on Ubuntu is a pragmatic choice if you are building data-intensive applications such as financial systems or AI pipelines. It is not flashy or cutting-edge, but it is proven, stable, and community support is solid. The combination of MySQL's reliability with Ubuntu's stability provided us confidence in production. My only caveat is not to underestimate the operational side. You need someone who understands database tuning and monitoring. Otherwise, you will hit performance walls later. I would rate my overall experience with MySQL on Ubuntu an eight out of ten.

My main use case for MySQL on Ubuntu is that I have used it most recently for building a WordPress web application in a stack, where MySQL operated as the back-end database for that WordPress.

A specific example of how I used MySQL on Ubuntu in that WordPress web application project is that I was collecting different RSVPs of people coming to an event, and the MySQL on Ubuntu database back end acted as the data store for that, recording the names of the people who were coming to the event and the time in which they RSVP'd, allowing me to figure out how many people were coming and analyze the data for certain age groups.

MySQL on Ubuntu has positively impacted my organization by enabling me to use a database that is very easy to use, quick to set up, and inexpensive; this database provides business value because every web application nowadays needs some type of database, so for those that require SQL databases, MySQL on Ubuntu is a great way to do it.

A specific outcome that shows the positive impact of using MySQL on Ubuntu is the time saved during setup. I have tried to create a Postgres database before, and while that is quite easy to do, MySQL on Ubuntu is quicker, being at least 20% quicker.

The best features MySQL on Ubuntu offers in my experience are that both MySQL and Ubuntu are very well-used products with massive user communities behind them, which is very useful when I am stuck, want to see documentation, or read about tutorials. MySQL on Ubuntu specifically is very simple to use and quick to set up, and I could easily get a database up and running in less than 10 minutes, which is brilliant for proof of concept scenarios.

Its popularity has created a massive ecosystem of different drivers and tools with support available everywhere. The resource usage of the underlying hardware is typically low, making Ubuntu's default MySQL on Ubuntu config very lean and ideal for smaller servers, which also helps with cost management.

The part that has helped me the most about MySQL on Ubuntu is that because it is such a popular setup, there is a lot of documentation out there, making it very easy to use, which is useful nowadays when software engineers, DevOps engineers, and cloud engineers have so many tools that they need to learn.

I would say that MySQL on Ubuntu can be improved particularly in its scaling capabilities. Scaling up is quite easy by simply increasing the RAM or CPU of the underlying machine, especially when running it on AWS or GCP; however, scaling out is much harder to do. Even though a master-slave setup can help maintain a real-time backup or offload queries, achieving true horizontal scaling with numerous nodes at once can be tricky with MySQL on Ubuntu.

Additionally, one limitation is MySQL on Ubuntu's involvement from Oracle, a for-profit organization, which raises some concerns about its future as an open-source project. MariaDB is an alternative that many people use, developed by the original MySQL developers, and it presents a viable option for those wanting MySQL on Ubuntu functionality while ensuring true open-source status.

I have been using MySQL on Ubuntu for around two years.

MySQL on Ubuntu is stable; both the MySQL component and the Ubuntu component are very stable, popular, and actively maintained.

MySQL on Ubuntu's scalability is highly dependent on the underlying infrastructure. When running on EC2 instances, for example, I can scale it from zero to 10,000 machines or even higher.

The customer support I have experienced is excellent. I used AWS support, and they are very quick to respond. I also find support available from sources such as Stack Overflow, Reddit, and the documentation because MySQL on Ubuntu is such a common use case.

Positive

Before using MySQL on Ubuntu, I previously used Postgres on Ubuntu. The switch was due to a business requirement, and while Postgres was good, MySQL on Ubuntu was quicker to get up and running, though I feel Postgres might handle more complex data better.

The initial setup process requires building an EC2 instance and then installing MySQL on Ubuntu on it after choosing the operating system, which I selected as Ubuntu.

I did not purchase MySQL on Ubuntu through the AWS Marketplace. I purchased it by building an EC2 instance and then installing MySQL on Ubuntu on it after choosing the operating system, which I selected as Ubuntu.

I have indeed seen a return on investment, particularly in time saved, as using MySQL on Ubuntu has proven to be 15 to 20% quicker than building a Postgres database.

Regarding pricing, setup cost, and licensing, I do not remember the exact price, but I believe Ubuntu is open source, so I can assume that was free. As for MySQL on Ubuntu, I feel that was free as well or very low cost, but the actual machine running it generates the cost. Since MySQL on Ubuntu is quite lean, it results in low operational costs, making it favorable from a pricing perspective.

Before choosing MySQL on Ubuntu, I did not evaluate other options; it came as a requirement.

My advice to others looking into using MySQL on Ubuntu is to go for it; it is a very common way to utilize databases and operating systems together. I would rate this review a 9 out of 10.

MySQL on Ubuntu is used mainly for backend database management for our web applications. We handle a fair amount of transactional data, so we need something stable and fast. MySQL on Ubuntu fits that perfectly. It is also used for storing and querying large datasets for reporting and analytic work that our team does on a regular basis.

We had a customer management system that we built for one of our clients, where MySQL on Ubuntu played a key role. It was handling thousands of customer records, orders, and transaction histories. We set up MySQL on Ubuntu as the backend, and it managed all the read and write operations smoothly. We had multiple users hitting the database simultaneously, and it held up really well. The performance was consistent, and setting it up on Ubuntu was straightforward compared to other environments I have worked with.

MySQL on Ubuntu has had a significant impact across several different areas in our organization. From a performance standpoint, since we standardized on MySQL on Ubuntu across our projects, we have seen a noticeable improvement in application response times. Our queries run faster, our application load times have gone down, and overall the end-users are having a smoother experience. This directly translates to better client satisfaction for us. From a cost perspective, it has been a significant benefit. Both MySQL Community Edition and Ubuntu are open source, so we are not paying heavy license fees. That savings gets reinvested into other parts of the infrastructure or development. Operationally, the stability has been outstanding. We have had very minimal unplanned downtime related to the database layer. Ubuntu as an operating system is solid for server workloads, and MySQL on Ubuntu runs reliably. Our team spends less time firefighting database issues and more time actually building and improving our applications. From a team productivity angle, because the setup and administration are reliable and straightforward, even our junior developers can handle basic database tasks without always needing a dedicated DBA to step in. This has really improved our team's overall efficiency.

MySQL on Ubuntu is deeply embedded in how our team operates on a day-to-day basis. We use it for everything from development environments locally to production deployment on cloud servers running Ubuntu. MySQL integrates well with the Ubuntu ecosystem. Whether it is setting up automated backups using cron jobs, managing services through systemctl, or monitoring performance through the MySQL slow query log, everything ties together nicely on Ubuntu. We also do a lot of database migration and schema updates as our application evolves, and tools like mysqldump have been very helpful for taking snapshots before any major changes. It gives the team confidence knowing we can roll back if anything goes wrong. Security-wise, we have been able to configure user permissions and SSL connections without much difficulty, which matters a lot when dealing with client data. Ubuntu's built-in firewall tool UFW also makes it easier to lock down access to the MySQL port. The community support around both MySQL on Ubuntu is massive. Anytime we run into an issue, whether it is a performance bottleneck or a configuration question, there is almost always a solid answer available.

Storage engine flexibility is something that stands out. We primarily use InnoDB, which gives us full ACID compliance and row-level locking, which is critical for our transactional workload. MySQL Workbench is genuinely appreciated. Even though we are on Ubuntu, Workbench runs great and gives us a visual interface for designing schemas, running queries, and managing users. It is really helpful when onboarding new team members who are not fully comfortable with the command line. Partitioning is another feature that we genuinely appreciate. For some of our larger tables with millions of rows, being able to partition data by date or by category has made a huge difference in query performance.

There are several areas where MySQL on Ubuntu can be improved. First, the initial configuration out of the box is not always optimal for production workloads. When MySQL on Ubuntu is first installed, the default settings in the configuration file are conservative. Things such as buffer pool size, connection limits, and query cache settings need manual tuning, and for someone not deeply experienced with database administration, that can be overwhelming. A more intelligent default configuration wizard during installation that asks about workload type and automatically suggests appropriate settings would be beneficial.

Second, the error messages can sometimes be cryptic. There are situations where an error code comes up and one really has to dig through documentation or community forums to understand what is actually going wrong. More descriptive and actionable error messages would save a lot of troubleshooting time.

Third, the built-in monitoring and observability could be better. Currently, we rely on third-party tools such as Percona Monitoring and Management or Grafana with a custom dashboard to get meaningful insight into database performance. Having more robust native monitoring tools directly built into MySQL without setting up a whole separate monitoring stack would be beneficial.

Finally, the documentation, while extensive, can sometimes feel scattered. Consolidating it and making it more beginner-friendly would lower the barrier for new users coming into the MySQL on Ubuntu ecosystem.

On the compatibility side, one thing that has occasionally caused challenges is compatibility between different MySQL versions and certain Linux kernel updates. Sometimes after a system update on the Ubuntu side, minor behavioral changes or deprecated dependencies that require attention are not immediately noticed. This is not a frequent issue, but when it happens, it can be disruptive, especially in production environments. Better version compatibility guarantees and clear communication about potential conflicts between MySQL and Ubuntu updates would be appreciated.

Also, compatibility with certain third-party tools and ORMs can sometimes be more inconsistent. We had situations where a newer version of MySQL introduced slight syntax changes that broke compatibility with our ORM layer, and we had to scramble to patch things. More backward compatibility focus would be beneficial.

On the user interface front, MySQL Workbench is functional, but it feels outdated compared to modern database management tools available today. A more polished and integrated web-based management interface, something built in by default, similar to what phpMyAdmin offers but more modern and secure out of the box, would be a welcome addition for teams managing remote Ubuntu servers.

MySQL on Ubuntu has been used for roughly four years.

Before we standardized on MySQL on Ubuntu, we dealt with approximately two or three unplanned database-related outages per quarter. After optimizing our setup with proper replication, automated backups, and monitoring in place, we brought that down to almost zero. We had maybe one minor incident in the last 12 months, and even that was resolved within the hour.

MySQL on Ubuntu is straightforward once it is set up, but there are a few things that are usually only learned after running into issues. One of the biggest things to know early is that the default installation is very safe but minimal. It works fine for learning or a small project, but for anything substantial, one will want to explicitly configure things such as remote access, user privileges, and password authentication. Many beginners assume MySQL on Ubuntu is ready for production out of the box, but it really is not until hardened.

Another important lesson is to pay attention to the authentication plugin. Newer MySQL versions on Ubuntu often default to auth_socket or stronger password plugins that can confuse people when they try to log in with a password and it fails. Understanding how MySQL authentication works will save a lot of time. Performance-wise, the default configuration is conservative. If running anything beyond a small application, one will eventually want to tune settings such as buffer pool size, query cache depending on the version, and connection limitations. Ubuntu does not auto-optimize MySQL on Ubuntu for hardware. Manual tuning is necessary.

MySQL on Ubuntu is a really powerful and reliable combination that has served us well over the years. The performance, stability, cost-effectiveness, and the strong community support are all genuinely impressive. For most use cases, especially web applications and transactional workloads, it delivers really well. The reason for not giving the highest rating is mainly because of those areas mentioned earlier. The out-of-box configuration needs manual tuning.

Two points have been knocked off because of practical day-to-day frustrations that we have experienced consistently over time. The first point comes off because of the configuration and setup complexity. When MySQL on Ubuntu is deployed fresh, the default settings are not production-ready. One has to invest significant time researching, and it cannot be easily trusted in a live environment. For an experienced DBA, that is manageable, but for a smaller team or someone newer to databases, it is a barrier. The second point comes off because of a tooling and user interface gap. When MySQL Workbench is compared to some of the modern databases available today, it genuinely feels behind. The interface feels very heavy.

From a general security standpoint, MySQL on Ubuntu has a solid foundation. The role-based access control system is mature and granular. One can define very specific permissions at the database, table, and even column level, which is important when dealing with sensitive data. SSL and TLS encryption for data in transit are well supported. However, when it comes to AI-specific governance capabilities, MySQL on Ubuntu is still fairly basic. There is no native built-in framework for things such as data lineage tracking, audit trails specifically designed for AI workloads, or automated sensitive data detection and masking. As organizations start using their MySQL on Ubuntu databases to feed AI modules, those governance features become really critical, and one is largely dependent on third-party tools to fill that gap. Overall, the security foundation is solid, but the AI-specific governance layer definitely needs more development and attention going forward.

MySQL on Ubuntu is primarily a data storage and retrieval system rather than an AI engine. The accuracy and reliability conversation is really about how dependably it stores, manages, and serves data that feeds into AI and machine learning workflows. MySQL on Ubuntu is genuinely reliable from that angle. The data integrity features that come with the InnoDB storage engine, things such as ACID compliance, foreign key constraints, and transaction management, mean that the data going through AI pipelines is consistent and trustworthy. Query results are accurate, consistent, and repeatable. There has never been a situation where the database returned unexpected or corrupted results. As a reliable data backbone for AI systems, MySQL on Ubuntu absolutely holds its own. The AI-native features just need more maturity. This review rates MySQL on Ubuntu with a score of 8 out of 10.

Our main use case for MySQL on Ubuntu is for workforce analytics, where we have US data for Employbridge and Bluecrew, storing the candidate's historical data used for machine learning purposes.

MySQL on Ubuntu works as a data warehouse for us, where we store this historical data that comes in the form of APIs. Then with the help of ETL, we transform it, and SQL acts as a data warehouse for us where we store the finalized data.

That is the only use case that we are currently using MySQL on Ubuntu for.

With MySQL on Ubuntu, we have much more capability of handling it in terms of specifications, and it helps us in reducing costs because MySQL on a cloud platform was costing us much. Using MySQL installation on Ubuntu has helped us save costs, improve our reliability, and maintain data privacy regarding personally identifiable information data.

Since our EC2 instance is deployed in a virtual private network with MySQL on Ubuntu installed, it is protected from unauthorized access and use, and we have also encrypted the data in MySQL. With the functions that MySQL on Ubuntu provides, we have much more capabilities in terms of manipulating the data and producing results that are useful for business purposes.

MySQL on Ubuntu has positively impacted our organization as a trusted data platform for many years across enterprises. We are following the same pattern here, and with the capabilities MySQL on Ubuntu provides and the fine tuning and optimization that the platform offers, along with Ubuntu, we have much more capabilities for fast processing of data. The way it handles MySQL and binary has helped us scale our data platform, achieving high availability and great performance with the analytics we perform.

I am not sure how MySQL on Ubuntu can be improved at the moment because we have not specified any anomalies regarding its integration with Ubuntu. Over the years, MySQL has improved and introduced new functions, so I hope that MySQL on Ubuntu can optimize its internal operations further.

In terms of user experience, MySQL on Ubuntu integrates easily with available IDEs such as JetBrains, Visual Studio Code, and DBeaver, so it works perfectly. The documentation is also good, and there is no issue with integration.

I have been using MySQL on Ubuntu since the last one or two years.

MySQL on Ubuntu is stable.

MySQL on Ubuntu's scalability is pretty good.

The customer support for MySQL on Ubuntu is fairly good, and we have a monthly meeting with them. There have not been any issues.

Positive

Before choosing MySQL on Ubuntu, we evaluated Microsoft SQL Server because of the data this organization had. Previously, the organization was using Microsoft SQL Server before acquiring this company, but because of the integration it required and its older syntax, it did not meet our needs. With new age developers coming in, MySQL on Ubuntu was the most preferred choice.

We originally started with MySQL on Ubuntu. Before developing the application, we created the architecture and looked for multiple options, ultimately choosing MySQL on Ubuntu to go with it.

We have a high-performance EC2 instance, and by installing MySQL on Ubuntu, we achieve high performance in terms of executions. Thanks to the optimization functions and internal functionalities of MySQL on Ubuntu, we maintain constant CPU metrics within the desired range. In terms of analytics speed, we achieve expected results, with significantly reduced downtime due to this scalability and improved processing speed.

We have integrated S3 as a data storage layer with MySQL on Ubuntu, so instead of storing data on a local disk, we use S3, which has fairly reduced our data storage cost. Time is also saved because we are using S3 Express, leading to good performance speeds.

MySQL on Ubuntu is a great platform to deploy your data. It integrates well with services for ETL, analytics, or even machine learning platforms. I would urge everyone to use MySQL on Ubuntu, especially when using AWS, as it provides an additional layer of VPC to achieve high scalability and availability.

I rate MySQL on Ubuntu a nine out of ten because it has been a good tool for us to integrate with our analytic services. The functions it provides, along with integration with our services and cloud services, have worked perfectly for us. We have not encountered a single downtime, and creating a cluster within our VPC has added a layer of data security and effective handling of encryption.

I have used MySQL on Ubuntu over the years, and I am currently working with some Docker products, but most of my experience with Docker is over Windows, not Linux.

Currently, I am not using MySQL on Ubuntu, but in the past, I have worked as a software developer and software architect, typically using it for end-user applications that manage data for the end-users, more in a back-office capacity. I have deployed MySQL on Ubuntu projects using the free version MariaDB, which is basically the same engine for the database.

MySQL on Ubuntu offers very good performance, it is secure, and it is easy to use.

MySQL on Ubuntu helps with data management processes primarily because it is easy to query the data and easy to connect from external or third-party software, such as Excel or Power BI, given some security configurations. It has very good performance, is easy to use, and provides secure methods to handle data.

I believe there could be improvements for MySQL on Ubuntu, particularly with AI integration in scripting tools such as GitHub Copilot, which provides examples and solutions for errors encountered during development.

Overall, I would give MySQL on Ubuntu a nine out of ten because, despite some issues such as security concerns when changing passwords which compromised the database, it remains a very good database engine.

My experience with MySQL on Ubuntu is around three to four years.

Unfortunately, the backups on Ubuntu have not been particularly beneficial because the system was always up, but once while conducting tests, the backup of the database helped me.

I have not utilized replication and clustering capabilities with MySQL on Ubuntu.

While I have not dealt with support, there is a lot of documentation available for MySQL on Ubuntu, and GitHub Copilot provides substantial information that helps when encountering errors.

Setting up MySQL on Ubuntu was pretty easy, as it involved generating scripts from the tables and creating a backup in plain text.

I have not managed too much with the transactional support features of MySQL on Ubuntu, as I have focused more on design and data management rather than optimizing transactions, since I typically use those databases for small companies that do not require optimizing.

I deal more with design than data management, but I have also done some data management work there.

I have managed backups with MySQL on Ubuntu, but I have not handled recovery; it could be generated as a plain text file or encrypted files for more security.

I have only used basic security resources such as user and password with MySQL on Ubuntu, but I know that there are options to set up certificates for a more secure connection.

I would rate this product nine out of ten overall.

I used MySQL on Ubuntu for temporary storage of financial data utilized for analysis of creditworthiness as the main use case, as I had some streaming services that pulled in data from Equifax.

It helped streamline my data management processes because I needed somewhere to store the data rather than just an array in memory. I needed to have the data to have the record because at some points I have to go back to determine what was the basis of this credit assessment. The data was there and could recreate the calculation once the data was called, and the data was called timestamped, secure, and always available, which is the whole point of MySQL on Ubuntu. Otherwise, if I used an array, it would only be there for the life of the system being up; there would not be a necessity of saving any of the data that was just in a temporary array. By putting it in MySQL on Ubuntu, even if the node went down, the database would come back up.

Integration is always important regarding operating systems and these types of products, so being able to integrate and export or import from JSON structures is very critical. Sometimes that is a little complicated because of the sometimes hierarchical nature of JSON or XML data formats, which do not always match to how you can structure MySQL on Ubuntu as a third normal form. There are those sorts of things that sometimes get inexperienced people; it does not seem to make sense.

For denormalization, if you are trying to analyze it only, there is probably a shortcut that I have seen in some tools that once you define the third normal form type of data, it kind of automatically comes up with a way of analyzing it, turning it into an automated pivot table without you having to design the pivot table. Those things would be good to get the analysis.

Some of the analysis that I had to code from scratch in Python were really simple binomial algorithmic comparisons. Some of that could turn into AI functions. Instead of coding it directly, I could use normal language saying I want to analyze this data based on whether this company has good financial viability to extend a million dollars of credit for buying fuel around the world or whatever the parameter is. That is what I can see coming in the future, that somebody that does not know how to code or does not really want to spend the time coding could actually ask in natural language AI to come up with that. To some extent, I have done that more recently with ChatGPT anyway to come up with a piece of code that at the moment does not work perfectly, but it is still Python and gives me the basic framework to then make it work elegantly.

I dealt with MySQL on Ubuntu for about two years.

I assess the transactional support features of MySQL on Ubuntu as just very simple insert and read because there was only really one stream that inserted data, so there was not any multi-concurrency of entering records to the database. The multi-concurrent users were just accessing and running the algorithm in the nodes to actually get an evaluation. Basically, they called a thing, they said I wanted to give some credit to company A. The node would do a query to Equifax and Experian to get whatever they could get on that and some Dun & Bradstreet information as well, put that in the Ubuntu SQL database, MySQL on Ubuntu database, and then run another algorithm to determine based on a couple of statistical points of view whether to give them this credit or whether they have to prepay for anything.

Regarding MySQL on Ubuntu scalability, I never touched it in terms of scalability because we were not looking at terabytes of data; we were looking at gigabytes of data. I think the database hardly went above one gigabyte when I was there because it is very simple. It just says here is the name of the company and here is anything we have got from three of the main credit or fact information sources globally that might have information on that database. Then a quick search in a virtual web environment to see whether there was any more generic business information on those companies, such as whether director A has just been fired or director B has been in jail for fraud or something, to get a little sentiment analysis of all these other things. The total data was very little.

The initial setup was very straightforward because I have a lot of experience in various database technologies and in Python and creating servers in virtual servers in AWS.

MySQL on Ubuntu is very simple, easy, and quick to use for people with database expertise. For that light use of MySQL on Ubuntu, that was all I needed, so there was nothing that was inadequate, and I could easily access it. The node was fine and the accessibility for people around the world that were actually asking whether they could give credit to this company or whether they have to pay up front was the main thing that was being supported, so everything was fine. There were no limitations there because the data volume was fairly small; globally, they only probably looked at about a thousand different entities per month and so there was only about another thousand records each month added, and the analysis done to give a pretty much real-time determination of whether to extend credit or request prepayment.

AWS was basically my main cloud provider with this. The low cost is what I liked about using MySQL on Ubuntu because basically, I did not have much of a budget for the solution, just my time and a few units of AWS services to work on, because it had to be more than just something on my own PC in the office, so other people could access it, allowing me to actually create a front end as well with it. It is very lightweight regarding the pricing; I never got any issues and was within my department budget for all AWS services for development. We never actually got a production budget for it because things were changing and then COVID hit as well, so it slowed down the demand. I am not quite sure what they did with that solution after that company, but I know they were using it. I still sometimes get an error message that somehow gets into my current AWS account.

I just utilized the standard virtual high availability options on Ubuntu, so I had redundant nodes in two regions. I dealt with MySQL on Ubuntu a little bit, but we never really got the Docker setup completed; I had some experience working with it. I have still maintained some Redshift analysis and some code in Python on some AWS products in the last twelve months. I am not working day-to-day anymore in that area with the Amazon solutions by chance. I deal with a little Amazon Linux and maybe Elastic Disaster Recovery, but not in detail, so I am probably not really the best candidate at the moment. I rate MySQL on Ubuntu a ten out of ten.

We are using MySQL on Ubuntu to store our transactions, which, because we are a trading firm, are usually the buy and sell trades that we make. We use this more as a relational database.

The primary aspect of MySQL on Ubuntu that I appreciate is that it is extremely reliable among the RDBMS that I have used. Another important quality is that it extends with volume very well. Most RDBMS don't scale very well, but this one scales very well and has been very reliable and highly available. The performance of MySQL is supposed to be very good, which is another aspect I really appreciate.

MySQL on Ubuntu supports what is known as the ACID properties, which are atomicity, consistency, isolation, and durability. This supports my use cases very well because without having all of them together, it's tough to ensure the reliability and integrity of the system. Transaction management ensures that we can figure out the best way to leverage the database.

The security of AWS is set at a very high standard, and we do a good job of ensuring that we leverage the base security that comes with the cloud platform. It is a joint responsibility between the cloud platform provider and the tenant, which is us. We harden our platform very well and, on top of that, MySQL on Ubuntu provides clear permissioning and separation of concerns, allowing us to provide permissions only to the right set of people. There is very clear segregation of duties, and only the people who need access are given access. It supports encryption, enhancing our security posture. Security is one of the big concerns that MySQL on Ubuntu has lived up to for our use cases.

I have not seen too much of a response in terms of issues. Sometimes, if the indexing is not done very well, I have noticed slowness, but largely, it has performed pretty well. The only area where I would say I have seen potential for improvement is occasional slowness, but I cannot really attribute it to the product; it could also be the design of the database and the queries. I have not encountered any other significant challenges.

The slowness that occurs at times has not yet been established whether it is due to the design of the database, the queries, or the underlying software itself. I cannot comment on that right now.

We have been using MySQL on Ubuntu for about a year and a half now.

We have not used too much replication, but clustering is useful because that helps with high availability and scalability. Clustering definitely helps.

MySQL on Ubuntu stands out among its competitors because, after evaluating some of them, I figured out that this is the one I would be interested in using for our solutions. While we have used MS SQL in the past, AWS supports MySQL on Ubuntu very well, which has worked excellently for us.

Backup and recovery are absolutely essential; without that, it would be very tough to rely on the software, as the software will not perform if suddenly there is some kind of an outage. We definitely require the recovery mechanism and backup mechanism to be able to go back to the data. That gives us the confidence that we can run our critical applications. Mission-critical applications can be run on these platforms because they provide both backup solutions and recovery solutions.

The pricing of MySQL on Ubuntu is fairly plausible for what I am getting, especially when I compare it with everything else that I see. It becomes attractive if I can use some of the free tiers of AWS.

The deployment and management have improved significantly; previously, it would have been tough because many configurations needed to be taken care of. However, now, with just a few lines of code, we can deploy and manage it much more easily. Overall, I rate this review an eight out of ten.

We are using MySQL on Ubuntu for the best use case for a CMS content management system which we use for motor data, e-commerce transactions, and getting data from the field for video footage as well as events on MySQL on Ubuntu server.

We are using MySQL on Ubuntu to manage all this data for our e-commerce transactions and video events through the integrated command and control system handling. We are using MySQL version 7 with Ubuntu 22.07. We get the data from the field in the form of videos, images, and photos. This data is bifurcated through Kafka and routed into MySQL on Ubuntu database server for the challan purpose and for the event footage for the police user use cases.

We are using MySQL on Ubuntu for the server which utilizes the motor data server that is used for NMS network management services for getting all events like CPU, LPU, and CPUs, and monitoring all the data to get the data on one single platform, which is the ICCC data center, and to display all the records on the dashboard.

If you are talking about MySQL on Ubuntu's best features at the application level, they are high-speed read-write performance, strictly integrated data, and a scalable structure. For the CMS, including web content management and social media handling and online transaction, these are the use cases which we are seeing.

For web content management using MySQL on Ubuntu, this is the backend for the world's most popular platforms like WordPress, Joomla, and Drupal. We use this for user profiles and configuration settings. For e-commerce, we are using the GPT service for the government side where different types of vendors are nominated to sell their products to government norms.

There are many useful cases for MySQL on Ubuntu. If you are talking about MySQL on Ubuntu security, when we take an example like MySQL installation, we use a bit script for which we set a strong root password and a hardened OS. If we are using Ubuntu, we harden the operating system on different platforms at the OS level, SSH level, kernel level, as well as the SELinux level. We can remove the history file and manage access. These are some specific cases for security and reliability for the user.

MySQL on Ubuntu has a definite impact on our organization. It improves the scalability level to 70% and the accessibility is very fast to achieve the data on the dashboard. We provide different types of reports to end users on the different side using Power BI. This improved the efficiency of our organization.

The workbench, GUI-based application for MySQL on Ubuntu, needs improvement.

I have been using MySQL on Ubuntu for the last three years for the DBMS, LPUs, and for the analytics service.

MySQL on Ubuntu is stable.

I provide a seven out of 10 for MySQL on Ubuntu for the scalability and better speed to access.

We provide a seven out of 10 because we are using different areas in MySQL on Ubuntu. This is open-source, so there is no need to purchase it, and we can use it effectively with different operators.

The customer support for MySQL on Ubuntu is very good. We are providing an eight out of 10 for the customer support of MySQL on Ubuntu.

Previously we were using MS SQL Server. We found that it had a low rate of scalability and a low rate of accessibility. We now switched to MySQL on Ubuntu.

Taking a real-world example of how MySQL on Ubuntu has improved our team's workflow and productivity, we are using the local processing unit on the field side where we get the data from the local cameras which are installed on the field side. This data is stored on MySQL on Ubuntu in the local LPUs for different storage. Then this data is sent to the ICCC data center through the MPLS link, and after that, this data is used for the police team for evidence and to catch thefts and different types of unwanted activities which are occurring in the cities to stop these types of criminal work.

MySQL on Ubuntu is more relational, scalable, and free to use, and the security is very enhanced. The large products we are using are for microservices, web development, and AI, and for Power BI. We can use it in different fields of areas, and it is open-source and free to use. Overall, I provide this product with a review rating of 7 out of 10.