Whether React is your favorite JavaScript framework or not, it is the most commonly used web framework. If you're building single-page apps, high fidelity frontends, or even in some cases static sites, there's a high chance that you're using React to do it. In the past it was sometimes difficult to decide on the best place to put code from libraries, such as ably-js, which can cause re-renders, and which have their own state management.

This is an article about the complexity of maintaining data consistency in distributed environments. It introduces conflict-free replicated data types (CRDTs) as a way to resolve concurrent data changes.

We are excited to announce our partnership with Aerospike, the world leading realtime data platform, to solve intermittent connectivity, massive scale, and real-time processing challenges for organizations looking to deploy realtime digital experiences at global scale.

An event indicates a state change: that something has happened. This ‘something’ could be a hardware sensor reading that passes a threshold, or a software event from game logic, or user input such as a keystroke or mouse click. Events are used to signal to interested parties that a state change occurred.

As the post-pandemic world emerges, the future of events such as summits, conferences or concerts is brighter than ever. Thanks to hybrid events, in-person events are now doubled by online happenings, which allows event organizers to reach much larger, geographically distributed audiences. For organizers and ticket distributors, providing a great ticket-booking experience to their global audiences has become more important than ever.

We are excited to announce our new Kafka connector. The Ably Kafka Connector provides a ready-made integration between Kafka and Ably, helping companies distribute data from Kafka to internet-connected client devices in a fast, easy, dependable and secure way. As part of our partnership with Confluent, the connector is available on the Confluent Hub as a Gold standard connector.

Hello again! Welcome to Part 2 of this article series where we go through database-driven architectures by understanding the nitty gritties of a chat app where you can edit messages. Here's the Part 1 of this article series, if you missed it: Database-driven realtime architectures: building a serverless and editable chat app - Part 1 Check out the editable chat app or explore the project on GitHub.

Database-driven realtime architectures are becoming more and more common as evidenced by key backers and widespread use of software like Firebase and Supabase. The two key priorities for an app following database-driven realtime messaging are long-term storage and change data capture (CDC) updates from the database. In this two part article series, we’ll take a detailed look at a fully serverless chat app where you can edit previously published messages.

In Part 1 of this two-part series, we walked through how to bypass Ably’s SDKs and connect to Ably’s backend using websocat, where every JSON message has to be typed out by hand. In this second part, we’ll fix that tedious bit by switching to NodeJS, and we’ll continue our process of building our own minimal Ably (NodeJS) SDK.

Built by our long-time community expert Apoorv Vardhan, the Ably-Postgres connector can listen to changes in a Postgres table and publish realtime messages on Ably channels whenever a change occurs. The connector enables building database-driven realtime applications where long-term storage and update triggers from previously published messages are essential. One such example is an editable chat app, which we’ll talk about later in this article.