What is our primary use case?
My primary use case for HCLTech Informix is multifaceted. I have previously used it as a backend database for Visual Basic, Visual Basic .NET, and C applications, as well as an analytical system to generate key metrics and indicators.
Currently, it serves as our main repository, feeding the foundational (bronze) layer of our data lake with incoming system data while running continuously in the background.
Specifically, we connect directly to HCLTech Informix for raw data ingestion into the bronze layer. We execute SELECT queries across full tables, while using delta loads for larger tables (such as our billing table) to populate the base layer for downstream analysis.
The connection speed is exceptionally fast. Data is ingested daily in batches, and the entire pipeline runs seamlessly. Both application-level writes to the database and data extraction for the data lake operate flawlessly.
What is most valuable?
The standout features of HCLTech Informix are its ease of integration, high data-loading performance—especially for large tables in a short timeframe—and effortless connectivity. The ability to utilize real-time data written by an application, combined with our daily batch loads that flawlessly handle critical data, are the key reasons we continue to rely on it today.
HCLTech Informix has contributed significantly to my organization. When I joined, it had already been implemented for many years, and even today, it has not been fully phased out. I believe it remains highly relevant to the business.
This relevance is reflected in our daily operations, particularly in terms of reliability. This is a crucial factor, as I work at a large enterprise with a high level of responsibility regarding customer data.
What needs improvement?
HCLTech Informix could potentially be improved in the future, but at the moment, I am not in a position to evaluate whether a DBMS can evolve further. For every feature and use case I have required to date, it has met my needs perfectly.
For how long have I used the solution?
I have been using HCLTech Informix for many years, as our software also used HCLTech Informix as its initial database.
What do I think about the stability of the solution?
HCLTech Informix is completely stable in my environment.
What do I think about the scalability of the solution?
Over time, as our data volumes grew significantly, HCLTech Informix scaled seamlessly and consistently met our needs. Whether handling smaller datasets or millions of additional records, it has always operated flawlessly.
Which solution did I use previously and why did I switch?
Prior to HCLTech Informix, some components were migrated to major vendors, but the old core database—which still runs today in our legacy software—remains on HCLTech Informix. Previously, we used nothing else besides it; now, we run other solutions in parallel.
What was our ROI?
I cannot determine whether we have seen a return on investment from using HCLTech Informix because I don't work on the administrative or management side. My role focuses on hands-on software and database usage as a data engineer, so I don't have visibility into financial performance metrics.
Which other solutions did I evaluate?
Before choosing HCLTech Informix, I did not evaluate other options. It was already implemented when I joined, and because it remains in active use today, I believe it fully meets all our requirements for this use case.
What other advice do I have?
A very useful feature we relied on heavily in the past was dirty read isolation, which was crucial for us because it allowed us to monitor the real-time status of information without locking tables.
My advice to anyone considering HCLTech Informix is to adopt it with confidence—it perfectly delivers on everything the platform promises. I would rate this product a ten out of ten.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
