Elasticsearch is an enterprise search tool from Elastic in Mountain View, California.
$16
per month
PostgreSQL
Score 8.7 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.
N/A
Microsoft SQL Server
Score 8.7 out of 10
N/A
Microsoft SQL Server is a relational database.
$1,418
Per License
Pricing
Elasticsearch
PostgreSQL
Microsoft SQL Server
Editions & Modules
Standard
$16.00
per month
Gold
$19.00
per month
Platinum
$22.00
per month
Enterprise
Contact Sales
No answers on this topic
Subscription
$1,418.00
Per License
Enterprise
$13,748.00
Per License
Offerings
Pricing Offerings
Elasticsearch
PostgreSQL
Microsoft SQL Server
Free Trial
No
No
No
Free/Freemium Version
No
No
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
Elasticsearch
PostgreSQL
Microsoft SQL Server
Considered Multiple Products
Elasticsearch
Verified User
Vice-President
Chose Elasticsearch
We first started out experimenting with PostgreSQL's fulltext searching capabilities for our project. As our dataset grew, PostgreSQL began to slow down too much for our purposes. The simple fact that Elasticsearch has built-in clustering and replication was enough for us to …
Previously, we used Microsoft SQL Server's full-text search. Elasticsearch is faster and that includes searching and indexing and re-indexing the catalog of products.
Elasticsearch and Solr are both based on Lucene, but the user community for Elasticsearch is much stronger, and setting up a cluster is easier. Splunk is very well suited for Log indexing and searching but is not nearly as flexible as Elasticsearch. Couchbase is a great NoSQL …
When we first evaluated Elasticsearch, we compared it with alternatives like traditional RDBMS products (Postgres, MySQL) as well as other noSQL solutions like Cassandra & MongoDB. For our use case, Elasticsearch delivered on two fronts. First, we got a world-class search …
Even though Lucene is very powerful it is not easy to implement Lucene as a search provider. Lucene is the core of Elasticsearch and they made implementation very easy.
Ability to support JSON queries, Percolator, ease to set up and custom routing were some of the reasons why we decided to use Elasticsearch instead of Solr.
I have used MS SQL and MySQL. Microsoft SQL Server is a good option for small applications in the commercial space. PostgreSQL can be more compared with Oracle in the feature set.
They each have their pros and cons. MySQL is probably the other popular "free" alternative in this space, but it's not as popular or have as much community support as PostgreSQL. Microsoft SQL Server is amazing in the microsoft tech stack, but it's pretty useless and provides …
PostgreSQL has more features than MySQL, and it has better documentation. Microsoft SQL Server is more complicated to set up and administer, and its syntax is not as easy to write as PLPGSQL. Moreover, the built-in functions in PostgreSQL are better than what's on offer from MS …
MySQL: As I mentioned before, MySQL has superior write performance. However, Postgres has super read performance and safer ACID transactions, i.e. less potential data loss. Elasticsearch: we use Elasticsearch to store free-form customer data, but that's a different use-case. …
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 …
We had to use PostgreSQL as that is the DB preferred by our SaaS Provider.
Verified User
Manager
Chose PostgreSQL
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.
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 …
Verified User
Engineer
Chose PostgreSQL
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 …
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 …
PostgreSQL is rich in features and free to use which is perfect for our organization. PostgreSQL is our goto RDBMS if we want to create an application or services backend with the database if there's no specific requirement. For example for the most important and largest …
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.
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.
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.
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 …
SQL Server is an excellent product from Microsoft, it is a derivative from Sybase which originally developed the SQL Server form Unix and Linux, and Microsoft purchased it to migrate the DBMS to Windows Server. But the cycle comes full circle, and now Microsoft recommends its …
It's a viable alternative, with a rich feature set and a reliable system. PostgreSQL is one of the best RDBMS's currently on the market in 2020, it serves just as well as a starter, PoC DB for any software idea as a final, highly valuable database solution for big systems.
PostgreSQL beats every other RDBMS offering for being truly Open Source. Since it does not belong to a specific company it is poised to remain as such for a long time to come. PostgreSQL has a huge user base and active community. The releases are coming out often with …
PostgreSQL is very similar to both MySQL and Microsoft's SQL Server. With no licensing costs, it's clearly a win against SQL Server, plus it can be run on either Linux or Windows. MySQL and PostgreSQL also have many similarities, however, PostgreSQL offers many more options for …
I have been a SQL Server focused professional for over 20 years, so SQL Server is my first choice. I have experience and comfort, and the ability to get up to speed quickly. Oracle has been too expensive, though I think it has performed similar to SQL Server in the applications …
When talking about structured storage, the big three currently are SQL Server, MySQL and Oracle. You can also toss in PostgreSQL into the mix. From a straight forward relational storage stand point, any of these tools will work, and work well. However, SQL Server is superior in …
Microsoft SQL Server is more secure and offers more robustness for our data. SQL Server is also great because of its integration with Microsoft Visual Studio. It's also great because developers can build reports and stuff like that from scratch. It's faster compared to PostgreSQ…
Elasticsearch is a very good alternative to using SQL Server full-text search. It is not a relational database like SQL Server but is open-source so cost is lower. MySQL is another open-source option to look into depending on the requirements of your projects.
Microsoft SQL Server is cheaper than Oracle, so it is the best choice for us. But our data is growing, we are searching for other technologies. Maybe Oracle, DB2, or PostgreSQL.
UI of the Microsoft SQL Server makes it easy to use and learn. The better technical support and documentation give it an extra edge over other databases. The Microsoft ecosystem provides additional advantages, as we can seamlessly use other Microsoft products, such as Power …
Microsoft SQL Server is faster and more compatible, but it does cost more, so you're paying for those features. I use the others in many other places where critical transaction processing time and compatibility aren't of great concern.
Microsoft SQL Server providers a more user friendly experience when it comes to Microsoft SQL Server components management via its unique SQL Server management Studio. It is also a production ready, resilient, highly available and tested database management system (DBMS). The …
MS SQL Server is easier to use compared to other RDBMS which really speeds up development time and relatively easier to find a problem when it happens as well. It's also pretty quick to run a query, especially in a large table make it pretty convenient if we need to monitor the …
Native to Windows and being required for other MS apps puts it above others in terms of usage. If we were not heavily dependent on Microsoft applications or OS, we might have considered other database solutions. It's an expensive solutions but it is a solid reliable solution. …
For a single vendor solution, SQL Server is the best choice in my opinion. Most of the other solutions do not offer the full range of products in a single package. Also, for a largely Microsoft shop, there are additional integrations which increase the value proposition. …
Microsoft SQL Server is a DBMS that can be used in any situation, from small projects to big ones, and the latest versions now can be used in several OS platforms. It is a great product with many features over its competitors. It's a mature and robust product. It's easy and …
Compared to free versions, SQL Server just blows away the free/open-source software. Things just run faster, and better, and at less overhead. This is truer and truer with the later versions. Microsoft just invests so much into research and development into their product. And …
SQL Server is a full feature robust platform with relatively mature coding standards. Interactivity with other Microsoft products enhances my workflow with minimal installation headaches.
In contrast, easier licensing for MySQL and SQLite gives them a definite advantage, …
I started working with databases many years ago with Access, which allows you to create relational database and provide an old-fashioned desktop interface. I had a look at Oracle but I never had the opportunity to get to the bottom (also because of the budget that had the …
Elasticsearch is a really scalable solution that can fit a lot of needs, but the bigger and/or those needs become, the more understanding & infrastructure you will need for your instance to be running correctly. Elasticsearch is not problem-free - you can get yourself in a lot of trouble if you are not following good practices and/or if are not managing the cluster correctly. Licensing is a big decision point here as Elasticsearch is a middleware component - be sure to read the licensing agreement of the version you want to try before you commit to it. Same goes for long-term support - be sure to keep yourself in the know for this aspect you may end up stuck with an unpatched version for years.
PostgreSQL is best used for structured data, and best when following relational database design principles. I would not use PostgreSQL for large unstructured data such as video, images, sound files, xml documents, web-pages, especially if these files have their own highly variable, internal structure.
Microsoft SQL is ubiquitous, while MySQL runs under the hood all over the place. Microsoft SQL is the platform taught in colleges and certification courses and is the one most likely to be used by businesses because it is backed by Microsoft. Its interface is friendly (well, as pleasant as SQL can be) and has been used by so many for so long that resources are freely available if you encounter any issues.
As I mentioned before, Elasticsearch's flexible data model is unparalleled. You can nest fields as deeply as you want, have as many fields as you want, but whatever you want in those fields (as long as it stays the same type), and all of it will be searchable and you don't need to even declare a schema beforehand!
Elastic, the company behind Elasticsearch, is super strong financially and they have a great team of devs and product managers working on Elasticsearch. When I first started using ES 3 years ago, I was 90% impressed and knew it would be a good fit. 3 years later, I am 200% impressed and blown away by how far it has come and gotten even better. If there are features that are missing or you don't think it's fast enough right now, I bet it'll be suitable next year because the team behind it is so dang fast!
Elasticsearch is really, really stable. It takes a lot to bring down a cluster. It's self-balancing algorithms, leader-election system, self-healing properties are state of the art. We've never seen network failures or hard-drive corruption or CPU bugs bring down an ES cluster.
Microsoft SQL Server Enterprise edition has a high cost but is the only edition which supports SQL Always On Availability Groups. It would be nice to include this feature in the Standard version.
Licensing of Microsoft SQL Server is a quite complex matter, it would be good to simplify licensing in the future. For example, per core vs per user CAL licensing, as well as complex licensing scenarios in the Cloud and on Edge locations.
It would be good to include native tools for converting Oracle, DB2, Postgresql and MySQL/MariaDB databases (schema and data) for import into Microsoft SQL Server.
We understand that the Microsoft SQL Server will continue to advance, offering the same robust and reliable platform while adding new features that enable us, as a software center, to create a superior product. That provides excellent performance while reducing the hardware requirements and the total cost of ownership of our solution.
To get started with Elasticsearch, you don't have to get very involved in configuring what really is an incredibly complex system under the hood. You simply install the package, run the service, and you're immediately able to begin using it. You don't need to learn any sort of query language to add data to Elasticsearch or perform some basic searching. If you're used to any sort of RESTful API, getting started with Elasticsearch is a breeze. If you've never interacted with a RESTful API directly, the journey may be a little more bumpy. Overall, though, it's incredibly simple to use for what it's doing under the covers.
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.
SQL Server mostly 'just works' or generates error messages to help you sort out the trouble. You can usually count on the product to get the job done and keep an eye on your potential mistakes. Interaction with other Microsoft products makes operating as a Windows user pretty straight forward. Digging through the multitude of dialogs and wizards can be a pain, but the answer is usually there somewhere.
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.
We've only used it as an opensource tooling. We did not purchase any additional support to roll out the elasticsearch software. When rolling out the application on our platform we've used the documentation which was available online. During our test phases we did not experience any bugs or issues so we did not rely on support at all.
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.
We managed to handle most of our problems by looking into Microsoft's official documentation that has everything explained and almost every function has an example that illustrates in detail how a particular functionality works. Just like PowerShell has the ability to show you an example of how some cmdlet works, that is the case also here, and in my opinion, it is a very good practice and I like it.
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.
Other than SQL taking quite a bit of time to actually install there are no problems with installation. Even on hardware that has good performance SQL can still take close to an hour to install a typical server with management and reporting services.
As far as we are concerned, Elasticsearch is the gold standard and we have barely evaluated any alternatives. You could consider it an alternative to a relational or NoSQL database, so in cases where those suffice, you don't need Elasticsearch. But if you want powerful text-based search capabilities across large data sets, Elasticsearch is the way to go.
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 family of applications that performs the company that develops it and that is not all bad, but being able to adapt or configure different programs, applications or other environments developed by third parties apart is what gives PostgreSQL a certain advantage and this diversification in the components that can be joined with it, is the reason why it is a great option to choose.
[Microsoft] SQL Server has a much better community and professional support and is overall just a more reliable system with Microsoft behind it. I've used MySQL in the past and SQL Server has just become more comfortable for me and is my go to RDBMS.
We have had great luck with implementing Elasticsearch for our search and analytics use cases.
While the operational burden is not minimal, operating a cluster of servers, using a custom query language, writing Elasticsearch-specific bulk insert code, the performance and the relative operational ease of Elasticsearch are unparalleled.
We've easily saved hundreds of thousands of dollars implementing Elasticsearch vs. RDBMS vs. other no-SQL solutions for our specific set of problems.
Easy to administer so our DevOps team has only ever used minimal time to setup, tune, and maintain.
Easy to interface with so our Engineering team has only ever used minimal time to query or modify the database. Getting the data is straightforward, what we do with it is the bigger concern.
Increased accuracy - We went from multiple users having different versions of an Excel spreadsheet to a single source of truth for our reporting.
Increased Efficiency - We can now generate reports at any time from a single source rather than multiple users spending their time collating data and generating reports.
Improved Security - Enterprise level security on a dedicated server rather than financial files on multiple laptop hard drives.