Informix is an embedded relational database offering from IBM.
N/A
PostgreSQL
Score 8.5 out of 10
N/A
PostgreSQL (alternately Postgres) is a free and open source object-relational database system boasting over 30 years of active development, reliability, feature robustness, and performance. It supports SQL and is designed to support various workloads flexibly.
Informix vs. Oracle: although both products are real enterprise-class DBMS, satisfying robustness and scalability criteria, Informix is much more easy and simple to admin. It requires much fewer resources in terms of DBA staffing for an equivalent infrastructure on Oracle. …
As a DB Team Leader I have been looking after other platforms (SQLSvr, MySQL, Oracle and PostgreSQL), supporting application changes, and driving their platforms enhancements through lots of projects over many years. The more I have learnt from other platforms, the more I found …
IBM Informix creates an effective and secure channel for easy and quick data management and transfer across other major Cloud platforms and other data storage systems. The analytical ability is also the best and most effective visual functionalities and the encryption and the data archiving functionalities are great and easy on reporting.
PostgreSQL, unlike other databases, is user-friendly and uses an open-source database. Ideal for relational databases, they can be accessed when speed and efficiency are required. It enables high-availability and disaster recovery replication from instance to instance. PostgreSQL can store data in a JSON format, including hashes, keys, and values. Multi-platform compatibility is also a big selling point. We could, however, use all the DBMS’s cores. While it works well in fast environments, it can be problematic in slower ones or cause multiple master replication.
Excellent Data Warehouse performance from the basic engine. Outstanding Data Warehouse performance from the Informix Warehouse Accelerator module.
Best embedability among major RDBMS systems.
Scalable from the smallest Raspberry PI up to the largest monolithic systems and out to dozens of distributed nodes.
Hybrid data capabilities to merge relational data with time seriesv, geospacial data, JSON data and other non-traditional data types with performance comparable or better than systems dedicated to those data types.
The stability it offers, its speed of response and its resource management is excellent even in complex database environments and with low-resource machines.
The large amount of resources it has in addition to the many own and third-party tools that are compatible that make productivity greatly increase.
The adaptability in various environments, whether distributed or not, [is a] complete set of configuration options which allows to greatly customize the work configuration according to the needs that are required.
The excellent handling of referential and transactional integrity, its internal security scheme, the ease with which we can create backups are some of the strengths that can be mentioned.
It is very difficult to find a missing functionality in Informix, technically is great. I will again criticize the business side and how it has been managed over the past, I hope this could be improved with HCL's help. I know they are working hard, but we need to start letting the world know and revert their concept about its existence and that it is one of the best competitors within the data treatment, in the market. We need to start telling the world about success cases and stories showing this and backing up its strong technology.
The query syntax for JSON fields is unwieldy when you start getting into complex queries with many joins.
I wish there was a distinction (a flag) you could set for automated scripts vs working in the psql CLI, which would provide an 'Are you sure you want to do X?' type prompt if your query is likely to affect more than a certain number of rows. Especially on updates/deletes. Setting the flag in the headless(scripted) flow would disable the prompt.
Better documentation around JSON and Array aggregation, with more examples of how the data is transformed.
Postgresql is the best tool out there for relational data so I have to give it a high rating when it comes to analytics, data availability and consistency, so on and so forth. SQL is also a relatively consistent language so when it comes to building new tables and loading data in from the OLTP database, there are enough tools where we can perform ETL on a scalable basis.
The data queries are relatively quick for a small to medium sized table. With complex joins, and a wide and deep table however, the performance of the query has room for improvement.
There are several companies that you can contract for technical support, like EnterpriseDB or Percona, both first level in expertise and commitment to the software.
But we do not have contracts with them, we have done all the way from googling to forums, and never have a problem that we cannot resolve or pass around. And for dozens of projects and more than 15 years now.
The online training is request based. Had there been recorded videos available online for potential users to benefit from, I could have rated it higher. The online documentation however is very helpful. The online documentation PDF is downloadable and allows users to pace their own learning. With examples and code snippets, the documentation is great starting point.
IBM Informix creates effective solutions for big data extraction and data transportation functionalities across the entire Cloud services and the Automation ability is the best. The security that IBM Informix provides for all our business data and other project information and contacts is effective and the reports are very clean and easy to understand.
Postgres stacks up just [fine] along the other big players in the RDBMS world. It's very popular for a reason. It's very close to MySQL in terms of cost and features - I'd pick either solution and be just as happy. Compared to Oracle it is a MUCH cheaper solution that is just as usable.
Although I do not own nor have visibility on my company's figures:
Informix generates consistent savings on DBA staffing, no need for many DBAs as other DBMS require.
The replication architecture allowed consistent savings in the infrastructure as well as developments and maintenance, the job is already done, no need to develop complex and costly solutions, it's just a matter of configuring it.
The advantages of hybrid development (i.e mixing SQL and NoSQL in the same database) is not just a marketing hype: it allowed us to solve with a brilliant solution, in one afternoon of coding, a functional problem we have been having for more than 10 years!
The biggest drawback is that IBM pricing may be constraining, it has too important gaps between the mid range and highrange in terms of pricing
The user-role system has saved us tons of time and thus money. As I mentioned in the "Use Case" section, Postgres is not only used by engineering but also finance to measure how much to charge customers and customer support to debug customer issues. Sure, it's not easy for non-technical employees to psql in and view raw tables, but it has saved engineering hundreds of man-hours that would have had to be spent on building equivalent tools to serve finance or customer support.
It provides incredibly trustworthy storage for wherever customer data dumped in. In our 6 years of Postgres existence, we have not lost a byte of customer data due to Postgres messing up a transaction or during the multiple times the hard-drives failed (thanks to ACID compliance!).
This is less significant, but Postgres is also quite easy to manage (unless you are going above and beyond to squeeze out every last bit of performance). There's not much to configure, and the out of the box settings are quite sane. That has saved us engineers lots of time that would have gone into Postgres administration.
