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.
N/A
Progress MarkLogic
Score 9.0 out of 10
N/A
MarkLogic Server is a multi-model database that has both NoSQL and trusted enterprise data management capabilities. The vendor states it is the most secure multi-model database, and it’s deployable in any environment. They state it is an ideal database to power a data hub.
$0.01
per MCU/per hour + 0.10 per GB/per month
Pricing
PostgreSQL
Progress MarkLogic
Editions & Modules
No answers on this topic
Low Priority Fixed
$0.01
per MCU/per hour + 0.10 per GB/per month
Standard Reserved
$0.07
per MCU/per hour + 0.10 per GB/per month
Standard On-Demand
$0.13
per MCU/per hour + 0.10 per GB/per month
Offerings
Pricing Offerings
PostgreSQL
Progress MarkLogic
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
PostgreSQL
Progress MarkLogic
Considered Both Products
PostgreSQL
Verified User
Anonymous
Chose PostgreSQL
My expirence with other solutions is very limited, but what I saw/heard is, that on Azure the managed MS SQL Server is said to be more flexible and you can use it in a serverless-ish fashion. But on the other hand, PostgresSQL is still strong regarding its efficiency. And in my …
Being open source, PostgreSQL offers the highest performance among its peers. It has a strong support community where we can find solutions to most of the queries. It's suited for GIS (Geospatial) based applications, making it unique from its peers. There are fewer databases …
PostgreSQL holds it own against both these options. Some of these DBs are in play for certain needs but the majority are PostgreSQL because of cost and operational performance.
In my experience using all of these products over many years, PostgreSQL is better than any of them in reliability, performance, productivity, cost, scalability and interoperability across operating systems.
MySQL is an Oracle product which has in itself some known issues due to that (support, contract terms). Based on my knowledge, PostgreSQL support everything that MySQL support (syntax wise) and it adds more improvements and syntaxes that make the life of database engineers and …
First It's open source and it's cost-effective compared to other databases.PostgreSQL can be easily integrated with numerous platforms. It is well known and appreciated so relying on it as our system database can be easily accepted by our customers. And if your developing a …
For our use cases, PostgreSQL is just as feature rich as other options, costs less, and is simple to get up and running. There is also a plethora of documentation to support it which makes it a great option for a small scale startup without needing high levels of expertise to …
In this case, Postgres is preferred because it handles large data sets and requires fewer hardware resources than its competitor, MySQL. Compared to PostgreSQL, Microsoft products are excellent, but the installation process for MS SQL is lengthy. PostgreSQL has an advantage …
I've been using different databases for the past 20 years, solutions like MS SQL Server, MySQL, MariaDB, Interbase, Firebird, DB2, etc., and by using them I wasn't able to be neither close to the performance PostgreSQL deliver. Also, it is one of the most popular databases on …
Although the competition between the different databases is increasingly aggressive in the sense that they provide many improvements, new functionalities, compatibility with complementary components or environments, in some cases it requires that it be followed within the same …
We evaluated both PostgreSQL and MySQL, two popular open source relational databases. While they are very similar in most areas, PostgreSQL's reliability and performance won us over, plus it has much better support from cloud vendors we also work with.
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 …
A free corporate professional product. Who does not want to have such a thing, we hesitated because we did not know the product before and frankly we did not want it at first. But when we give it a chance, it has been running smoothly for years.
When we were originally evaluating Redshift we ran into some issue with dates. Either way, Postgres is a better choice than Redshift because it avoids vendor lockin. We ended up choosing Postgres over MySQL because it was easier at the time to get a hosted Postgres cluster up …
As I have been telling all along, PostgreSQL is much cheaper compared to the other RDBMS solutions. It has got better performance with some of the application services that we are using and is easy to maintain. Overall, we are satisfied migrating to PostgreSQL database clusters.
Much more mature and stable when compared to MySQL with features such as MVCC, complex subquery plans, ORDBMS, and NoSQL support. With Oracle retaining rights to MySQL its future as an open database is less secure and is no longer in the hands of the community. PostgreSQL also …
Its main characteristic is the integrity of the data. In addition, being free software, it has no costs associated with its license, which allows the number of installations to be scaled without problems.
The technical staff quickly learns about its installation, configuration …
Both Oracle and MS-SQL database option fell when we evaluated the effect on our overall solution cost to our customers. customer examine the overall cost of the solution they buy, selecting Oracle or MS-SQL would leave less money in our pockets. We are Linux based solutions and …
PostgrPostgreSQL as a transaction db engine against oracle and sql server works well. TPM wise compared to MySQL and MariaDB, on an evan scale. SQL function supports, far outweighs compared to MySQL and MariaDB. PG Extensions allow for flexibiltity and scalability. Allows …
We selected PostgreSQL due to the number of employees who have used it in the past. The data consistency guarantees. The multiple transaction isolation levels support.
PostgreSQL outperforms every other option. It is faster, more flexible, more reliable, easier to maintain, and more consistent in behaviour than any of the other offerings.
The main reason for select PostgreSQL against MS SQL Server Express edition is the necessity to use open-source platform, without any issues for licensing, client licensing, etc. etc, which is usually follows developers and project managers when they start to use products and …
In comparison to both Mongo and HBase, MarkLogic wins in terms of integration to other systems, while loosing in terms of pricing. In terms of documentation all will be in same range putting MarkLogic a bit forward.
MarkLogic is good at what it does: storing and searching XML with a REST interface. The amount of support out there for the other NoSQL products is what gives them the best advantage. Many plugins exist for those, none exist for MarkLogic. Even the proprietary ones like …
There's no other single product that directly compares to all the features that are packed into MarkLogic. Generally speaking, you're looking at a combination of many products to build a stack that competes feature-for-feature. Even if you're leveraging only a limited set of …
I have used most of the common RDBMS databases (SQL Server, Oracle, MySQL, etc.). MarkLogic is more dependable, faster, and flexible. I would not willingly go back to RDBMS. As far as open source competition to MarkLogic such as MongoDB, I haven't used it myself so I don't have …
Senior Director, IT Architecture and Publishing Solutions
Chose Progress MarkLogic
We had Fast in place when Microsoft had bought it up and was going to change / deprecate it. One of the biggest advantages of MarkLogic for search actually had to do with the rest of the content pipeline - it allowed us to have it all in one technology. On the NoSQL side, we …
Based on my experience, PostgreSQL is exactly what I imagine when thinking of a relational database: it is fast for querying and intuitive (if the underlying relations have been well written) and its writes are also efficient. Of course you need to know that a relational database is what you need, for example I would not recommend it if you have a lot of unstructured data that have no way to create a relation from and if you need to run heavy aggregations over your data, as it is not where PostgreSQL would shine.
In an area where it will be built once and maintained, it shines. If you aim to use CI, temporary environments, or anything else, it is not very effective. Licensing is almost impossible on boxes that are to be created on the fly.
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.
Indexing is a major strength of MarkLogic. The out-of-the-box configuration is set up to handle a combination of text and fielded data. The indexing is also highly configurable. Those configuration options are at the heart of a lot of our high-volume, high-performance applications.
The industrial strength transactions and security are also a strength, particularly when we are dealing with user-created intellectual property.
The engineering support is a strength. They are big enough to have a really strong support and engineering staff, but small enough so that a medium-sized customer has access to it. They are very responsive to questions and problem reports.
The ability to move easily among XML and JSON is a strength.
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.
How to do complete data profiling on documents loaded in Marklogic database?
Customers need a tools which can be customized to suit their data profiling needs but currently the tools which MarkLogic provides fall short on this requirement.
Unit testing framework which is using only XQuery as the language is lacking some features.
Our firm has consultants for a number of technologies/disciplines. While I am capable and experienced in other areas, my preference is always to work on engagements with MarkLogic. As an architect and developer, I get far more flexibility and performance from one product instead of cobbling together a stack of several products to provide a capability that MarkLogic has rolled into one great product.
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.
Very little about it can be done better or with greater ease. Even things that seem difficult aren't really that bad. There's multiple ways to accomplish any admin task. MarkLogic requires a fraction of administrative effort that you see with enterprise RDBMS like Oracle. MarkLogic is continually improving the tools to simplify cluster configuration and maintenance.
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.
There's always room for improvement. Some problems get solved faster than others, of course. MarkLogic's direct support is very responsive and professional. If they can't help immediately, they always have good feedback and are eager to receive information and details to work to replicate the problem. They are quick to escalate major support issues and production show-stopping problems. In addition to MarkLogic's direct support, there are several employees who are very active among the community and many questions and common issues get quick attention from helpful responses to email and StackOverflow questions.
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.
In my experience using all of these products over many years, PostgreSQL is better than any of them in reliability, performance, productivity, cost, scalability and interoperability across operating systems.
In comparison to both Mongo and HBase, MarkLogic wins in terms of integration to other systems, while loosing in terms of pricing. In terms of documentation all will be in same range putting MarkLogic a bit forward.
It took longer than expected to develop our application and get the level of consistent performance necessary. As a result, profit was flat for a couple of years but the benefits are really starting to kick in.