base on Hazelcast is a unified real-time data platform combining stream processing with a fast data store, allowing customers to act instantly on data-in-motion for real-time insights. # Hazelcast [](https://slack.hazelcast.com/) [](https://javadoc.io/doc/com.hazelcast/hazelcast/latest) [](https://hub.docker.com/r/hazelcast/hazelcast) ---- ## What is Hazelcast The world’s leading companies trust Hazelcast to modernize applications and take instant action on data in motion to create new revenue streams, mitigate risk, and operate more efficiently. Businesses use Hazelcast’s unified **real-time data platform** to process **streaming** data, enrich it with historical context and take instant action with standard or **ML/AI-driven automation** - before it is stored in a database or data lake. Hazelcast is named in the Gartner Market Guide to Event Stream Processing and a leader in the GigaOm Radar Report for Streaming Data Platforms. To join our community of CXOs, architects and developers at brands such as Lowe’s, HSBC, JPMorgan Chase, Volvo, New York Life, and others, visit [hazelcast.com](https://hazelcast.com). ## When to use Hazelcast Hazelcast provides a platform that can handle multiple types of workloads for building real-time applications. * Stateful data processing over streaming data or data at rest * Querying streaming and batch data sources directly using SQL * Ingesting data through a library of connectors and serving it using low-latency SQL queries * Pushing updates to applications on events * Low-latency queue-based or pub-sub messaging * Fast access to contextual and transactional data via caching patterns such as read/write-through and write-behind * Distributed coordination for microservices * Replicating data from one region to another or between data centers in the same region ## Key Features * [Stateful and fault-tolerant data processing and querying over data streams and data](#stateful-data-Processing) at rest using [SQL](https://docs.hazelcast.com/hazelcast/latest/sql/sql-overview) or dataflow API * [A comprehensive library of connectors such as Kafka, Hadoop, S3, RDBMS, JMS and many more](https://docs.hazelcast.com/hazelcast/latest/integrate/connectors) * Distributed messaging using [pub-sub](https://docs.hazelcast.com/hazelcast/latest/data-structures/topic.html) and [queues](https://docs.hazelcast.com/hazelcast/latest/data-structures/queue.html) * [Distributed, partitioned, queryable key-value store with event listeners, which can also be used to store contextual data for enriching event streams with low latency](https://docs.hazelcast.com/hazelcast/latest/data-structures/map) * Tight integration for deploying machine learning models with Python to a data processing pipeline * Cloud-native, run everywhere architecture * Zero-downtime operations with rolling upgrades * At-least-once and exactly-once processing guarantees for stream processing pipelines * Data replication between data centers and geographic regions using WAN * Microsecond performance for key-value point lookups and pub-sub * Unique data processing architecture results in 99.99% latency of under 10ms for streaming queries with millions of events per second. * Client libraries in [Java](https://github.com/hazelcast/hazelcast), [Python](https://github.com/hazelcast/hazelcast-python-client), [Node.js](https://github.com/hazelcast/hazelcast-nodejs-client), [.NET](https://github.com/hazelcast/hazelcast-csharp-client), [C++](https://github.com/hazelcast/hazelcast-cpp-client) and [Go](https://github.com/hazelcast/hazelcast-go-client) ### Stateful Data Processing Hazelcast has a built-in data processing engine called [Jet](https://docs.hazelcast.com/hazelcast/latest/pipelines/overview#what-is-the-jet-engine), which can be used to build both streaming/real-time and batch/static data pipelines that are elastic. A single node of Hazelcast has been proven to [aggregate 10 million events per second](https://foojay.io/today/sub-10-ms-latency-in-java-concurrent-gc-with-green-threads/) with latency under 10 milliseconds. A cluster of Hazelcast nodes can process [billion events per second](https://hazelcast.com/blog/billion-events-per-second-with-millisecond-latency-streaming-analytics-at-giga-scale/). ## Get Started Follow the [Getting Started Guide](https://docs.hazelcast.com/hazelcast/latest/getting-started/install-hazelcast) to install and start using Hazelcast. ## Documentation Read the [documentation](https://docs.hazelcast.com/) for in-depth details about how to install Hazelcast and an overview of the features. ## Get Help You can use [Slack](https://slack.hazelcast.com/) for getting help with Hazelcast. ## How to Contribute Thanks for your interest in contributing! The easiest way is to just send a pull request. ### Building From Source Building Hazelcast requires at minimum JDK 17. Pull the latest source from the repository and use Maven install (or package) to build: ```bash $ git pull origin master $ ./mvnw clean package -DskipTests ``` It is recommended to use the included Maven wrapper script. It is also possible to use local Maven distribution with the same version that is used in the Maven wrapper script. Additionally, there is a `quick` build activated by setting the `-Dquick` system property that skips validation tasks for faster local builds (e.g. tests, checkstyle validation, javadoc, source plugins etc) and does not build `extensions` and `distribution` modules. ### Testing Take into account that the default build executes thousands of tests which may take a considerable amount of time. Hazelcast has 3 testing profiles: * Default: ```bash ./mvnw test ``` to run quick/integration tests (those can be run in parallel without using network by using `-P parallelTest` profile). * Slow Tests: ```bash ./mvnw test -P nightly-build ``` to run tests that are either slow or cannot be run in parallel. * All Tests: ```bash ./mvnw test -P all-tests ``` to run all tests serially using network. Some tests require Docker to run. Set `-Dhazelcast.disable.docker.tests` system property to ignore them. When developing a PR it is sufficient to run your new tests and some related subset of tests locally. Our PR builder will take care of running the full test suite. ## License Source code in this repository is covered by one of two licenses: * [Apache License 2.0](https://docs.hazelcast.com/hazelcast/latest/index.html#licenses-and-support) * [Hazelcast Community License](http://hazelcast.com/hazelcast-community-license) The default license throughout the repository is Apache License 2.0 unless the header specifies another license. ## Acknowledgments We owe (the good parts of) our CLI tool's user experience to [picocli](https://picocli.info/). ## Copyright Copyright (c) 2008-2024, Hazelcast, Inc. All Rights Reserved. Visit [www.hazelcast.com](http://www.hazelcast.com/) for more info. ", Assign "at most 3 tags" to the expected json: {"id":"3757","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"