Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Memory saver
What do you like best about the product?
I love the small memory of the library I embedded (since I have many issues with the memory of my pc).
It is also very fast and not complex at all and it saved my all my problems in the distributed systems for sure!
It is also very fast and not complex at all and it saved my all my problems in the distributed systems for sure!
What do you dislike about the product?
Nothing to share about this...I would say as a con that it takes a bit more time in order ro coordinate yourself where and what is located
What problems is the product solving and how is that benefiting you?
Solved my problems with my relational databases where I was struggling with the whole backend team in managing correctly our db
- Leave a Comment |
- Mark review as helpful
Hazelcast is the one of the best tools for every day`s life
What do you like best about the product?
Hazelcast first of all is a really great distributed data grid. You can use distributed collections out of the box like Map, Set, Queue for microservices replicas to share data or for caching purposes. Also, it is possible to take distributed locks to prevent doing the same work simultaneously. The Streaming framework Hazelcast Jet has many needful features and is very fast. Can be run separately from services or as a library. Supports automatic rebalancing and replication. Multiple network options to make a cluster such as multicasting or kubernetes support.
What do you dislike about the product?
It`s a little bit tricky to set up cluster in Kubernetes but it`s a matter of reading the documentation carefully. You should write serializers for objects yourself but it`s your payment for the size of the memory footprint of your cache. Poor search options in in-memory data structures.
What problems is the product solving and how is that benefiting you?
Distributed cache, distributed locking for microservices architecture. Stream processing of the big data.
Recommendations to others considering the product:
Great tool for distributed caches and for the stream processing
Clustered in memory cache for your highly scalable application
What do you like best about the product?
We enjoyed using hazel cast cluster for one of the highly scalable SaaS applications serving 2 million transactions every minute
Hazel cast was very stable and we loved it
Hazel cast was very stable and we loved it
What do you dislike about the product?
We used Hazel cast back in 2013-2015 and those days I felt there were multiple opportunities to improve further. Some of those improvements which we had suggested didn't get implemented even after a a couple of years.
What problems is the product solving and how is that benefiting you?
We used it for reducing DB hits for our highly scalable SaaS application
Recommendations to others considering the product:
It used to be one of the well-known java based alternative for Memcached.
Give it a try:)
Give it a try:)
Simple and Powerful Stream Processing Engine
What do you like best about the product?
Performance and how it is easy to start implementation. In-memory processing is great adventage, because of high availability.
What do you dislike about the product?
Documentation is not as good as for Hazelcast IMDG and sometimes I do not know where I can find some information I am looking for.
What problems is the product solving and how is that benefiting you?
We needed Stream processing platform which allow to connect to Kafka and generate some output based on Python scripts provided by business analitycs. Jet allowed us to get messages from Kafka, translate them, enrich with data from software based on another Hazelcast IMDG, execute Python scripts and generate expected output.
Efficient in-memory database, best when used next to a relation database
What do you like best about the product?
I like Hazelcast being configurable to auto back-up features of it. When one of your hazelcast instance is down, remaining instances in the cluster recovers those data from backup and continue working where it left.
What do you dislike about the product?
I can't think of anything I don't like about Hazelcast IMDG, maybe the pricing would be the worst side of it.
What problems is the product solving and how is that benefiting you?
Hazelcast is solving our caching problem and fastens the data access time. It also makes it possible to spend less time on managing instances of cache. The instances can discover each other and communicate as default.
Recommendations to others considering the product:
I used Hazelcast embedded to the services. However, stand-alone usage of Hazelcast might provide a better/more sustainable cluster.
And Excellent Grid-Cache
What do you like best about the product?
Performance, ease-of-use, and JVM friendliness
What do you dislike about the product?
Hazelcast implementation requires application changes. However, solutions like the Heimdall Proxy can manage Hazelcast clusters by providing the caching and invalidation logic for Hazelcast.
What problems is the product solving and how is that benefiting you?
Improved response times and database scale via query caching
Recommendations to others considering the product:
The Heimdall Database Proxy provides the caching and invalidation for Hazelcast. You can create a SQL cache subsystem in minutes without any code changes.
High performance cache
What do you like best about the product?
The ability to have a distributed cache with very high performance numbers
What do you dislike about the product?
Setup on a distributed system can somethings be tricky, but with tools like Kubernetes it's much more simpler than used to be.
What problems is the product solving and how is that benefiting you?
We needed to serve multiple customers. Before, the only way to scale was adding a bigger machine, now, we can just add a new node.
Hazlecast IMDG helped us to reduce service transaction response times by an order of magnitude.
What do you like best about the product?
Hazlecast is great because it's distributed data-structures are extensions of commonly used java interfaces. Due to this our team was able to quickly grasp the framework, and implement our solution.
What do you dislike about the product?
At the time I was using this (2017), there weren't much documentation explaining the internal behavior, so we had to dig in to the source code.
What problems is the product solving and how is that benefiting you?
Hazlecast IMDG helped us to reduce service transaction response times by an order of magnitude, by allowing us to process at the data nodes, in memory. This is a huge cut down in network and disk I/O, when comparing to traditional architectures, where all the data is loaded to the service nodes. It also helped us increasing the number of CPUs available for a single transaction, thanks to it's distributed executor service.
More details - https://medium.com/@tharanga.hewa/distributed-computing-for-not-so-big-data-a7a14600d4b8
More details - https://medium.com/@tharanga.hewa/distributed-computing-for-not-so-big-data-a7a14600d4b8
Recommendations to others considering the product:
May be the stateful architectures that Hazelcast presents are not for every situation, as they are hard to manage (talking about DevOps). Use it when there is a dying need for performance.
Hazelcast review
What do you like best about the product?
We had multiple services running independently. It was helping us to make financial data instantly available to all our services.
What do you dislike about the product?
It's costly and you cannt add huge data in this as it stores data in in-memory.
What problems is the product solving and how is that benefiting you?
Saved multiple back and forth calls between services as if you add data in any service and it will be instantly available to other services.
I have used Hazelcast in production systems with success
What do you like best about the product?
Simple api. Easy to understand. Minimum dependence
What do you dislike about the product?
I wish Hazelcast has better integration with aws like redis
What problems is the product solving and how is that benefiting you?
I was using it as a cache implementation to improve flight search service
showing 1 - 10