Elasticsearch is an enterprise search tool from Elastic in Mountain View, California.
$16
per month
Redis Software
Score 9.1 out of 10
N/A
Redis is an open source in-memory data structure server and NoSQL database.
N/A
SAP Commerce Cloud
Score 8.2 out of 10
N/A
SAP Commerce Cloud (formerly Hybris) is designed to help businesses sell more goods, services, and digital content through every touchpoint, channel, and device through their multichannel ecommerce and order management solution, available as a SaaS or on-premise.
Elasticsearch has a steep learning curve, but it is the best in terms of customization and use cases it can cover most of the business needs. The other tools might be easier to integrate with and start seeing results, but you will end up having issues when you need customized …
All database systems have things they are good at, and things they aren't as good at. Riak/SOLR is great as a K/V store, but SOLR cannot handle requests as fast as ElasticSearch. In fact, SOLR is the reason we had to migrate to ElasticSearch. Redis is great at SET operations …
ES does not compete with the above packages but compliments them. By automating and mining logs, you are able to get a sense of the business process, marketing data or whatever else you need to capture and mine. The potential energy stored within Elasticsearch makes it a great …
Verified User
Manager
Chose Elasticsearch
We found Elasticsearch to be the fastest in querying text based data, allowing us to significantly speed up our APIs.
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 …
Redis is great at set operations and is very fast. Riak is a fast long-term data store, but it is expensive to run. MongoDB is good for small, quick projects. Elasticsearch is great at indexing and searching. Choose the right tool for the job, and don't be afraid to …
We chose Redis over Memcached and Couchbase for its performance, cost, support, and ease of use. Couchbase probably would have worked as well, but it seemed a bit overkill for our use cases.
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.
Redis has been a great investment for our organization as we needed a solution for high speed data caching. The ramp up and integration was quite easy. Redis handles automatic failover internally, so no crashes provides high availability. On the fly scaling scale to more/less cores and memory as and when needed.
SAP Commerce Cloud is well-suited for large enterprises requiring robust personalization, seamless multi-channel integration, and the ability to handle high-volume transactions, especially during peak periods like Black Friday. Its scalability and advanced features make it ideal for businesses needing to manage complex product catalogs and global operations.Enough development capacities are needed to have a best in class shop
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.
Easy for developers to understand. Unlike Riak, which I've used in the past, it's fast without having to worry about eventual consistency.
Reliable. With a proper multi-node configuration, it can handle failover instantly.
Configurable. We primarily still use Memcache for caching but one of the teams uses Redis for both long-term storage and temporary expiry keys without taking on another external dependency.
Fast. We process tens of thousands of RPS and it doesn't skip a beat.
Centralized Data Management: SAP Commerce Cloud excels in centralizing data from various operational sectors, which is pivotal in the chemicals industry. This feature allows for better oversight and management of complex supply chains, regulatory compliance, and customer interactions. Having a single source of truth for crucial business data minimizes discrepancies and promotes informed decision-making.
Real-Time Data Processing: The real-time data processing capability of SAP Commerce Cloud is invaluable. It aids in timely adherence to regulatory changes and helps in meeting customer demands promptly. In a sector where regulations and market conditions are ever-evolving, real-time data processing is fundamental for maintaining compliance and ensuring customer satisfaction.
We had some difficulty scaling Redis without it becoming prohibitively expensive.
Redis has very simple search capabilities, which means its not suitable for all use cases.
Redis doesn't have good native support for storing data in object form and many libraries built over it return data as a string, meaning you need build your own serialization layer over it.
It's a little pricey; further cost reductions will expand product selection; also, trained operators are required.
HAC occasionally functions extremely slowly and does not provide any problem messages; it simply gets stuck. Logging into the Backoffice for testing purposes causes a lot of trouble; it does not enable us to log in in one attempt, and the page refreshes every time we enter in the credentials.
We will definitely continue using Redis because: 1. It is free and open source. 2. We already use it in so many applications, it will be hard for us to let go. 3. There isn't another competitive product that we know of that gives a better performance. 4. We never had any major issues with Redis, so no point turning our backs.
SAP Commerce and Spartacus together becomes one of the omnichannel powerhouse of commerce application. It also comes with edge advantage with out of the box integrations with many SAP applications and also non-SAP applciations which gives it edge advantage over other tools. The main reason being the integration becomes easier as SAP shares the common data schema and model across all its product line and new feature releases are compatible with all the SAP product line.
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.
It is quite simple to set up for the purpose of managing user sessions in the backend. It can be easily integrated with other products or technologies, such as Spring in Java. If you need to actually display the data stored in Redis in your application this is a bit difficult to understand initially but is possible.
More true headless and a more rationale pricing. Since moving from the Hzbris Monolyth towards SAP Commerce Cloud a lot of progress has been made, but dissecting the monolyth into composable components where you just pay for what you use is still a longer journey and here pricing should be more realistic. Things become so expensive once they have the SAP stamp on them (example the SAP CIAM)
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.
The support team has always been excellent in handling our mostly questions, rarely problems. They are responsive, find the solution and get us moving forward again. I have never had to escalate a case with them. They have always solved our problems in a very timely manner. I highly commend the support team.
We have the right to open a ticket or submit request to SAP support teams for all the problems we have experienced. They also provide solutions for critical issues within 48 hours. In addition, the product has support documents such as a user guide and admin guide. In addition, there is a strong community of users. In this way, we can access solution of some specific problems that we have fallen on from there.
Scalability of the product was good Seamless integrations were helped in reducing the implementation for the development team to integrate with the SAP ERP Product framework helped customer to customize and adapt the new features which were developed basis business processes and ease of customer experience. Deployment and creation of the build becomes very easy with the CCv2 setup.
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.
We are big users of MySQL and PostgreSQL. We were looking at replacing our aging web page caching technology and found that we could do it in SQL, but there was a NoSQL movement happening at the time. We dabbled a bit in the NoSQL scene just to get an idea of what it was about and whether it was for us. We tried a bunch, but I can only seem to remember Mongo and Couch. Mongo had big issues early on that drove us to Redis and we couldn't quite figure out how to deploy couch.
SAP Cloud is much better than GoDaddy. it was a smooth transition and every aspect of the program is easier. My scalability increased greatly from GoDaddy to SAp Commerce Cloud and sales are now tracked easier and inventory is at the touch of a button, making sales much easier than previous software.
The business users/admins were able to quickly segment products by brand, allowing for unique branding and header-less page design. As new products are added to the SAP backend, all characteristics and pricing automatically migrate to Commerce Cloud. We also segment our user sign-on (domains) by brand and allow targeting displays.
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.
Redis has helped us increase our throughput and server data to a growing amount of traffic while keeping our app fast. We couldn't have grown without the ability to easily cache data that Redis provides.
Redis has helped us decrease the load on our database. By being able to scale up and cache important data, we reduce the load on our database reducing costs and infra issues.
Running a Redis node on something like AWS can be costly, but it is often a requirement for scaling a company. If you need data quickly and your business is already a positive ROI, Redis is worth the investment.
It has a positive impact on my client's business and ROI is higher than expected. As orders count is increasing due to smooth and better experience.
My current client's customers have given very positive experience about new website built on SAP Commerce Cloud.
Due to SAP Commerce Cloud website rollout is very easy and due to it, my current client has introduced around 25 websites. As SAP Commerce Cloud logic needs to develop once and can be reused for multiple websites easily with minimal effort.
Branding is also very easy as promotions, events can be implemented on the website easily and with minimum time.
SAP Commerce has helped our client to integrate the Recommendation tool ISS which is easy to configure after this tool product sale is increased. The best thing was that integration was very easy and quick.
One option of Blue/Green deployment helping us to check the production release in advance on production environment. Prev we don't have this option and many times face P1 issue in prod which had ruined client reputation. But now this feature is helping lot
