Hazelcast Community Newsletter Archive

Welcome to the Hazelcast community newsletter archives! Discover latest blog articles, learning materials, industry news and meetups/events to stay informed about all things Hazelcast!

2024

  • January 2024 — In-depth Recap of the 12 Days of DevRel

    Explore real-time streaming solutions like payment systems on Hazelcast. Learn about preventing duplicate payments with fault-tolerant pipelines. Also, discover highlights from Hazelcast's 12 Days of DevRel event, featuring sessions on software architecture, development, support, customer success, and training.

2023

  • December 2023 — Technical Evolution of Stream Processing

    Explore the evolution of stream processing from 1980s dataflow programming. Discover the future of stream processing with the Unified Real-Time Data Platform. In part two of our discussion on data consistency, delve into ACID attributes and their relevance to databases.

  • November 2023 — Technical Evolution of Data Caching

    Explore the evolution of data caching and the performance benefits of Fast Data Store in-memory data grids over traditional databases. Learn about Data Consistency Dimensions, including Strong vs. Eventual consistency in Distributed Systems, and ACID vs. BASE approaches in Databases. Gain valuable insights to drive informed decisions for your business success. Join us on this journey.

  • October 2023 — Hazelcast: A Technical Evolution

    Discover how Hazelcast can assist you in achieving your distributed computing and real-time data processing objectives. From its inception, Hazelcast has evolved into a scalable, high-performance, in-memory data solution. Explore its significant technical advancements in this inaugural edition of our Community Newsletter.

Not subscribed?
Get the newsletter

"*" indicates required fields

By submitting this form, you are agreeing to the Hazelcast Privacy Policy, and you are agreeing to be contacted about this request. Manage your Hazelcast communication preferences here.
This field is for validation purposes and should be left unchanged.