Serial Number Database Software

Supabase isn’t very stakeholder-friendly. For a POC-level application, it seems fine and generally accepted, but then we’re advised to move to other options like RDS hosting. From what I’ve seen and tested, large and complex queries can be a pain and sometimes perform poorly. Review collected by and hosted on G2.com.

Supabase solves the problem of building and maintaining separate backend services by combining authentication, SQL files, APIs, and real-time features in one platform. This cuts down a huge chunk of backend setup and integration work, so I can move from a prototype to a working application much faster, while still keeping the flexibility of PostgreSQL. Review collected by and hosted on G2.com.

I find the learning curve to be challenging, especially around data modeling, partitioning, and cluster tuning. For new teams, it can be tough to understand data modeling and partitioning best practices and how to design tables around application access patterns. I think more practical examples, guided tutorials, and real-world production scenarios would make this easier. Review collected by and hosted on G2.com.

We use ScyllaDB to handle high-volume data ingestion and low-latency access with horizontal scalability. It's great for real-time events and time-series data, and it manages high throughput while maintaining consistent low latency, efficiently using CPU, memory, and storage. Review collected by and hosted on G2.com.

I find some limitations in support and integration with tools such as Flink. OceanBase introduces several data types and features that are not natively supported by MySQL. As a result, existing CDC tools and pipelines originally built around MySQL can be difficult to migrate and may require significant modifications. Also, the initial setup was somewhat complex. Review collected by and hosted on G2.com.

OceanBase provides better query performance for our large-scale data, handles transactional workloads effectively, and simplifies our architecture with its built-in vector capabilities, eliminating the need for a separate vector database. Review collected by and hosted on G2.com.

Sometimes more sophisticated configurations can take time to figure out especially when one deals with the more complicated database requirements related to performance tuning, security, high availability, and AI workloads. Someone who feels at home with standard PostgreSQL functions may need additional time to get used to the enterprise-level capabilities. Review collected by and hosted on G2.com.

The main benefit of using this software is flexibility. A team will be able to maintain the PostgreSQL environment and at the same time use all the new features of the application. That will make it possible to save some changes in the data environment and build applications with the ability to deal with both structured data and artificial intelligence. Review collected by and hosted on G2.com.

The user interface looks and feels like software from fifteen years ago; it is desperately crying out for a modern redesign. Performance also degrades quickly once the database file size grows, and the lack of native, seamless web or cloud integration is a massive pain point. If you want to share an Access database across a remote team today, you have to jump through hoops with SharePoint or virtual desktops, which feels incredibly outdated. Review collected by and hosted on G2.com.

It bridges the gap for departmental projects that have outgrown Excel but do not justify the massive cost and IT overhead of a full enterprise SQL Server infrastructure. It allows us to track inventories, internal workflows, and relational client data efficiently. Having automated reporting and strict data validation rules built right into the local office desktop saves us dozens of hours of manual cross-referencing every week. Review collected by and hosted on G2.com.

The Enterprise edition, in particular is very expensive per core, and the costs increase quickly as you scale. SQL Server also requires more RAM and CPU, and when parallel jobs are running it can lead to resource constraints. On top of that, the licensing model is complex and difficult to estimate upfront for a real project. Review collected by and hosted on G2.com.

Problem:

Downtime or data loss can severely disrupt business operations.

How SQL Server helps:

It offers Always On Availability Groups, along with backup, disaster recovery options, and failover mechanisms.

Benefit to me:

I can build systems that remain available and resilient, reducing downtime and supporting business continuity. Review collected by and hosted on G2.com.

Kintone gives us enough visual flexibility for internal applications, but it starts showing its limits when the experience needs to feel highly tailored. Fields, groups, tables, and spacing are easy enough to arrange, but precise control over labels, responsive behavior, layouts, or interactive components usually means adding JavaScript, CSS, or a plug-in. We ran into that while building an app for field technicians. The team wanted every piece of information visible on a single screen so they would not have to move through tabs or extra steps, and we tried to accommodate it. The form technically worked, but it became dense, slower to scan, and harder to use on smaller screens. We spent some time trying to improve it with CSS before accepting that the problem was not the styling. The structure itself was overloaded. Simplifying the form and showing only the information technicians needed at each stage produced a much better result than continuing to decorate a layout that had already become too complicated. Review collected by and hosted on G2.com.

A client integration required sandbox credentials, endpoints, technical contacts, API versions, test results, and several approvals before it could move into production. The issue was that all of this information was scattered across emails, support tickets, and a shared spreadsheet that two different people had already organized in completely different ways. We built an integrations app in Kintone and used Process Management to move each record through Discovery, Development, Client Testing, and Production Ready. Lookup pulled client data from our main app, and Related Records surfaced the incidents and deliverables tied to each integration. Our first version was too strict. We made so many fields mandatory that the team started entering placeholder values just to move a record forward. That technically satisfied the workflow, but it made the data less reliable. We adjusted the validation rules by status and added a JavaScript API customization that checked only the information required for each transition. Later, we connected the REST API to our deployment service so the release identifier and deployment result were written back to Kintone automatically. The platform didn’t remove the technical work, and it didn’t prevent us from designing a bad first version. What it changed was where that effort went. Instead of building and maintaining another internal application from scratch, we focused on the process, the validation logic, and the integrations that actually mattered. Engineering, QA, and operations ended up working from the same record, blockers became easier to spot, and we stopped asking the client for information that someone else on the team had already collected. Review collected by and hosted on G2.com.

One thing I dislike about MySQL is that some advanced database operations and complex queries can become difficult to manage as the application grows. Query optimization can also require a good understanding of indexing, execution plans, and database design. Additionally, MySQL Workbench can sometimes feel slow when working with large databases or complex schemas. Overall, these are manageable issues, but they can add some extra effort during development and troubleshooting. Review collected by and hosted on G2.com.

MySQL helps me solve the core challenge of reliably storing, managing, and retrieving application data. As a Java developer working with Spring Boot applications, I use MySQL to manage structured data and perform CRUD operations efficiently through APIs.

It benefits me by providing a reliable relational database that integrates easily with Java, Spring Boot, and JPA/Hibernate. MySQL Workbench also makes it easier to design schemas, inspect data, run queries, and troubleshoot issues. This helps me develop and debug applications faster while keeping the data organized and consistent.

The main problem MySQL solves for me is reliable data storage and management. I like that it integrates very easily with my Spring Boot applications using JPA and Hibernate. Setting up the database connection and performing CRUD operations is straightforward, which helps me develop applications faster and focus more on the business logic. Review collected by and hosted on G2.com.

It's a bit annoying and very time-consuming compared to the previous ERP systems. It's okay, but just very time-consuming. Review collected by and hosted on G2.com.

I use SAP HANA Cloud for supplier management, completing end-to-end transactions more efficiently. It reduces my transaction time from over an hour to just five to ten minutes per transaction. Review collected by and hosted on G2.com.

I find the cost and licensing complex. It's challenging to learn and run, Oracle Database is resource-heavy, and the developer experience feels outdated. The vendor lock-in is a concern as well. I think pricing could be simpler, and I would like to see a better cloud-native story with friendlier defaults. Review collected by and hosted on G2.com.

I use Oracle Database to run critical business apps, manage huge data securely, and ensure stability. It scales to terabytes, has built-in backup and disaster recovery, and supports real application clusters. Review collected by and hosted on G2.com.

Initial setup and configuration—especially when it comes to user roles, privileges, and connection pooling—feels more involved than with simpler databases. In my case, for a pet clinic system I run locally using XAMPP/MariaDB syntax, migrating the schema to PostgreSQL took extra care because of syntax differences (for example, AUTO_INCREMENT vs. SERIAL and how enums are handled).

On top of that, debugging complex multi-join queries—such as joining appointments with animals, owners, doctors, and schedules—can lead to error messages that are difficult to interpret, particularly for developers coming from a MySQL/MariaDB background. Review collected by and hosted on G2.com.

My pet clinic system manages eight interrelated tables—admins, owners, animals, doctors, staff, appointments, medical records, vaccinations, and invoices. PostgreSQL keeps this data consistent through foreign key constraints and transactional integrity, which is especially important when booking appointments or updating medical records.

For instance, when I create an appointment, the record needs to validate several things at once: that the animal exists, the owner matches that animal, the doctor is active, and an appropriate time slot is available. PostgreSQL’s transaction support also means there are no partial writes if any part of that process fails.

As a result, I’ve eliminated data integrity bugs in my application and cut down on the amount of validation logic I have to write in PHP, since the database enforces consistency at the schema level. Overall, it’s made the system more reliable and easier to maintain as I continue adding features. Review collected by and hosted on G2.com.

One area that could be improved is the pricing, especially as storage and resources scale. Some database configuration and monitoring options can also be a bit complex for new users. More cost optimization recommendations and a simpler management interface would make Google Cloud SQL even easier to use. Review collected by and hosted on G2.com.

I use Google Cloud SQL to manage data with ease, offering reliable performance, automated backups, and high availability. It simplifies administration by handling infrastructure, letting us focus on development. Scaling is seamless, saving us time and effort. Review collected by and hosted on G2.com.

Manual backups are locked to a higher tier. If you want that feature, you’ll need the plan that’s €22 + VAT per license/month (billed annually) instead of the starter at €11 + VAT per license/month (billed annually). It’s not a dealbreaker for me, but it’s worth knowing up front. Review collected by and hosted on G2.com.

Ninox is a time saver. After implementing my new management and accounting system, I am saving 2-3 hours each day on tasks that I used to run manually and are now automated thanks to databases created in Ninox. Review collected by and hosted on G2.com.

I find the initial setup difficult because MySQL Workbench is external and requires a public setup, which isn't easy for beginners. AWS should update their UI and UX for permissions and network management. Also, its costing is too high. Review collected by and hosted on G2.com.

I use Amazon RDS to store user data, integrating well with other AWS services. It allows access outside AWS, and I can manage it using MySQL Workbench. Initial setup is difficult and costs are high. Review collected by and hosted on G2.com.

The biggest downside of Redis Cloud is the cost as you scale up. The managed service is convenient, but pricing can rise quickly as memory usage increases. I’d also like to see more flexible configuration options, along with stronger monitoring capabilities. Review collected by and hosted on G2.com.

Redis Cloud helps address performance bottlenecks in applications that need fast access to frequently requested data. By caching responses and session data in Redis, we can reduce database calls and improve response times, making the application faster and more scalable overall. Review collected by and hosted on G2.com.

Schema and partition key design require careful planning. Query flexibility is limited compared to relational databases. Review collected by and hosted on G2.com.

Amazon DynamoDB handles high traffic efficiently, offering scalable high-performance data storage for real-time apps, without database management. It features automatic scaling, high availability, low latency, minimal operational overhead, and seamless AWS integration, providing fast performance for distributed and event-driven applications. Review collected by and hosted on G2.com.

The observability story still feels incomplete out of the box. Getting meaningful metrics without plugging in external tools like Prometheus takes more effort than it should. Also, the error messages during misconfigured cluster setups can be cryptic - a bit more guidance there would save a lot of debugging time. Documentation has improved, but advanced topics like PITR and xCluster replication still feel like they assume too much prior knowledge. Review collected by and hosted on G2.com.

YugabyteDB is solving the problem of needing a database that can handle large amounts of data and many users without slowing down. It gives the power of traditional SQL databases with the scalability of NoSQL systems. For me, as someone new to the software field, it helped me understand how modern applications manage data across different regions and servers while staying fast and reliable. It’s also helping me learn how real-world systems are built — like how companies make sure their apps don’t go down even if one part of the system fails. It’s been a great learning tool and has given me confidence to explore more advanced database concepts. Review collected by and hosted on G2.com.

Proper cache invalidation and eviction strategies require careful planning. Applications also need to be designed to gracefully handle cache misses or node failovers. Review collected by and hosted on G2.com.

ElastiCache reduced database bottlenecks by serving frequently accessed data directly from memory.

Example: Product catalog data, user sessions, authentication tokens, and API responses were cached in Redis, reducing database queries by more than half while lowering application response times from several hundred milliseconds to well under 100 milliseconds during peak traffic. Review collected by and hosted on G2.com.

Costs can increase significantly for high scale production workloads. It is quite expensive for high scale production workloads, especially with replicas and storage growth. Troubleshooting performance bottlenecks in complex environments can also require deeper AWS expertise. Review collected by and hosted on G2.com.

Amazon Aurora solves the challenge of running high-level and scalable relational databases without manually managing backups, failover, and infrastructure maintenance. Review collected by and hosted on G2.com.

It can get expensive if we don't monitor usage closely. Review collected by and hosted on G2.com.

I use Azure SQL Database to store and query application data without infrastructure worries. It saves me time by handling backups, servers, and patching automatically, allowing easy scaling and integration with Microsoft tools. Review collected by and hosted on G2.com.