No more typing reviews! Try our Samantha, our new voice AI agent.

IBM Informix vs Microsoft Azure HorizonDB comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

IBM Informix
Ranking in Relational Databases Tools
28th
Average Rating
8.2
Reviews Sentiment
7.5
Number of Reviews
17
Ranking in other categories
Embedded Database (9th)
Microsoft Azure HorizonDB
Ranking in Relational Databases Tools
13th
Average Rating
8.8
Reviews Sentiment
5.5
Number of Reviews
6
Ranking in other categories
Database as a Service (DBaaS) (13th)
 

Featured Reviews

Nasir Niamat - PeerSpot reviewer
DB Consultant at i2c
Has offered a cost-effective option despite frequent technical issues and limited market demand
We find some bugs in IBM Informix. Maybe we are using it more aggressively than others. Every month or every second month, we find some bugs in it, which is not ideal. It should be rare, not this frequent. The good thing is they cover those bugs in the next release within weeks or days on demand. IBM Informix should become hybrid and should include AI features similar to other DBMS systems such as Snowflake, Redshift, and DataBricks. This would help its value rise with the market.
reviewer2898678 - PeerSpot reviewer
Full Stack Software Developer at a financial services firm with 10,001+ employees
Event-driven workflows have delivered global low-latency data access and faster user responses
The standout features of Microsoft Azure HorizonDB are its native multi-model support and global distribution with turnkey scaling, along with rich consistency and change feed capabilities. It natively handles document, key-value, graph, and column family data, allowing me to pick the API that matches the workload such as Core SQL, flexible JSON, or MongoDB for existing drivers. It also automatically partitions data across physical nodes and replicates it to any number of regions I configure, providing sub-millisecond latency for both read and write operations globally. The operational features like point-in-time restore for multi-region write conflict resolution and serverless auto-scaling of request units keep the system highly available and cost predictable. Integration of security via managed identities and role-based access control removes the need for secret management, while Azure monitor metrics let us tune the system before throttling occurs. In practice, I utilize these features to build an event-driven microservice platform where every state change is persisted in Microsoft Azure HorizonDB and instantly propagated via change feed through Azure Functions, along with auditing and analytics cached using Azure Redis for ultra-fast dashboard reads. Overall, the benefits provide a relatable low-latency, globally resilient data backbone, and it can automatically scale while minimizing operational overhead for developers. The feature that has the most impact on my work is the built-in change feed. It allows microservices to write a state change to Microsoft Azure HorizonDB and allows downstream consumers to react automatically without polling or using custom synchronization code. The server-side feed scales with throughput and guarantees in-order, nearly real-time delivery for every message. I pair it with Azure Functions to either write audit records for the ELK pipeline or update materialized views in Azure Synapse. This integration helps decouple our core services from analytical and notification layers, dramatically reducing latency. For example, when a ticket moves through the workflow, the change feed triggers a function that both persists the transaction for reporting and invalidates the Redis cache for the UI, resulting in very low latency and end-to-end visibility. It is simpler than the previous code base, and the overall change feed provides real-time relativity, leading to lower operational overhead and scalability for our event-driven architecture. The feature that has given me the biggest productivity boost is the built-in change feed, which I use for persistent changes. For example, as a ticket moves from open to in progress, downstream consumers react automatically without the need for polling or custom sync code. This pattern provides built-in durability, and we can configure multi-region write conflict resolution, keeping the system highly available during regional outages. In practice, this gives us sub-millisecond end-to-end visibility, which is much simpler than before. From a tooling perspective, Microsoft Azure HorizonDB provides built-in support for Azure OpenAI embeddings, allowing us to generate vectors on the fly in serverless functions and write them back into the same container. Managed indices automatically scale our request units while maintaining the same multi-region replication and consistency guarantees, keeping latency low and the system highly available. In practice, I have used embeddings in our container to power a real-time FAQ bot, where each incoming question receives embeddings and triggers a function that queries the vector index, producing results for users within milliseconds. This setup eliminates the need for a separate search microservice and streamlines our architecture. Overall, the AI extension adds significant value by simplifying our embedding workloads while maintaining Microsoft Azure HorizonDB's reliability. I find the AI output from Microsoft Azure HorizonDB to be both accurate and reliable for most of our use cases. It consistently meets expectations as the service uses OpenAI embeddings with multi-region replication guarantees that we trust for transactional data. The vector index delivers results with millisecond latency, and in practice, we built a FAQ that shows relevance scores comparable to a dedicated search service, enabling users to see the correct answer about 92% of the time. Occasional mismatches typically stem from the underlying language model rather than the storage layer itself. The change feed-driven pipelines ensure that new or updated content is indexed almost instantly, keeping the model fresh with no need for re-indexing. Overall, these extensions have met my expectations for accuracy and reliability, delivering fast and dependable embedding search while keeping the architecture simple and highly available.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"IBM Informix benefits users with high availability and good integration capabilities."
"The initial setup is very simple."
"For IoT business cases, having Informix Enterprise Edition work on edge computers, like Raspberry Pi and using Informix replication, makes complex situations simple to build and maintain."
"The solution's stability, performance, enhanced functionality, and replication are all great features."
"My advice is to take it; you will never regret it."
"It supports multiple applications and business intelligence tools."
"Replication, all levels of replication, query charting, and the MongoDB embedded are the most valuable features of this solution."
"Informix can support huge quantities of data with less memory and less capacity."
"By persisting every state change, such as a ticket moving from open to in progress, into a single Cosmos container using the ticket ID as a partition key, we achieve automatic horizontal scaling with sub-millisecond read/write latencies across different regions."
"Microsoft Azure HorizonDB has been highly scalable for our workloads, allowing us to accommodate increases in application traffic, user activity, and data volumes without manually provisioning and managing additional database infrastructure."
"Microsoft Azure HorizonDB has positively impacted my organization by reducing latency issues, improving performance, and providing a good recovery time."
"Since we are in the proof of concept phase, we have noticed some early improvements and potential benefits that stand out so far in terms of speed, reliability, and ease of management."
"I am impressed by how they have detached the database from the core CPU engine of the compute and pushed out a lot of the code to the storage tier, making backup, recovery, and replication significantly faster than previous releases."
"Using Microsoft Azure HorizonDB provides better scalability and performance in terms of database administration."
 

Cons

"The solution doesn't include functionality like data anonymization."
"I really would love to have a QT plugin."
"There should be more intelligence surrounding discovering data to be able to automatically create indexes."
"The product needs a lot more marketing involvement from IBM."
"I would like to see backups from secondary servers."
"The support team could include local engineers to establish efficient communication. It will help us speed up the escalation process."
"Continue extending the SQL language for compatibility with the competition's language, including Stored Procedure Language."
"The pricing is a bit expensive."
"The only reason I do not rate it a perfect 10 is that I would prefer to see richer server-side query features and more granular cost forecasting in the portal, which would streamline development and debugging tasks."
"While the performance of Microsoft Azure HorizonDB is generally good, we have noticed that it can be more challenging during periods of higher application traffic and larger data volumes, with the impact being more noticeable when workloads generate a high number of concurrent read and write operations or when queries involve larger data sets, as poorly optimized or partitioned usage can result in higher resource consumption and require additional tuning."
"So far, I have not seen any return on investment from Microsoft Azure HorizonDB in terms of cost."
"Regarding needed improvements, I feel that we need more documentation on Microsoft Azure HorizonDB."
"I want to say that the costing of Microsoft Azure HorizonDB is too high and should be less."
 

Pricing and Cost Advice

"For me, it's always too expensive."
"The free edition can be enough to handle moderate-size implementations, but you may want a pay for edition to benefit from more functionality, such as replication."
"I am not aware of the licensing costs or terms."
"The product has reasonable pricing. We purchase its yearly license."
Information not available
report
Use our free recommendation engine to learn which Relational Databases Tools solutions are best for your needs.
921,523 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Comms Service Provider
12%
Construction Company
10%
Outsourcing Company
9%
Financial Services Firm
8%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise2
Large Enterprise8
By reviewers
Company SizeCount
Small Business4
Large Enterprise7
 

Questions from the Community

What is your experience regarding pricing and costs for IBM Informix?
There is a cost reason to move from IBM Informix. It is relatively cheaper than Oracle. The second reason is that moving the whole application to a new database would require significant cost. The ...
What needs improvement with IBM Informix?
We find some bugs in IBM Informix. Maybe we are using it more aggressively than others. Every month or every second month, we find some bugs in it, which is not ideal. It should be rare, not this f...
What is your primary use case for IBM Informix?
We are using IBM Informix for OLTP systems. We are using IBM Informix although it is a technology that is not very popular compared to others. We are using it because our application was initially ...
What is your experience regarding pricing and costs for Microsoft Azure HorizonDB?
Our experience with Microsoft Azure HorizonDB's pricing, setup cost, and licensing has been generally positive, as there was no major upfront hardware or infrastructure investment due to it bei...
What needs improvement with Microsoft Azure HorizonDB?
While the performance of Microsoft Azure HorizonDB is generally good, we have noticed that it can be more challenging during periods of higher application traffic and larger data volumes, with the ...
What is your primary use case for Microsoft Azure HorizonDB?
Microsoft Azure HorizonDB serves as our main use case to support production applications that handle large volumes of semi-structured and frequently changing data, and we use it as a scalable NoSQL...
 

Comparisons

No data available
 

Also Known As

Informix
No data available
 

Overview

 

Sample Customers

Shaspa, Hildebrand, Kaifa, Ranhill Powertron, Federaci‹ Farmacutica (FedeFarma), Camden Council, The German Aerospace Center (DLR), Myers, Votorantim Group, Doosan Infracore, GreenIvory
Information Not Available
Find out what your peers are saying about IBM Informix vs. Microsoft Azure HorizonDB and other solutions. Updated: November 2026.
921,523 professionals have used our research since 2012.