September 2016 Summaries

Aggregated feeds are designed to streamline the organization of similar activities into grouped feeds, with activities sorted by the "updated_at" field to prioritize recent interactions. The process of aggregation involves inserting an activity into a feed, applying a defined aggregation format, and grouping activities with the same group identifier. This grouping is achieved through a customizable aggregation format that can be adjusted to meet various needs, such as grouping by actor, verb, or specific time frames. Changes to the aggregation format only affect new activities, and debugging tools like the aggregation preview screen and feed reading are available to assist users in refining their formats. For more complex needs, GetStream offers enterprise solutions with custom aggregation logic, and users can explore the feature through an interactive tutorial or contact support for further assistance.

GetStream.io has launched an official Go client library, version 0.9.0, marking it as a beta release and the first community-adopted library to receive official support. The library, derived from community projects, focuses on enhancing feature functionality and test coverage, with particular attention to improving JSON Web Token (JWT) authentication support. The development was a collaborative effort, notably involving contributions from MrHenry and HyperWorks, and the company is eager for community feedback and participation to refine the library further. Additional notes will be available on the Rest API Documentation page, and GetStream.io is enthusiastic about ongoing collaboration with community developers to enhance their library offerings.

Stream has introduced a feature called Firehose to enhance its real-time platform, allowing users to monitor feed changes via Amazon SQS or webhooks, complementing the existing websocket framework. This addition is specifically designed to improve application speed for real-time functionalities such as games and chat applications, with the infrastructure capable of supporting sub-500 millisecond round-trip times. The blog post provides a step-by-step guide on integrating Firehose into Stream applications using AWS Lambda, Simple Queue Service (SQS), and Redis, detailing the process of setting up an IAM role, creating a Stream application, configuring a new SQS queue, and setting up a Lambda function to handle message processing. It also covers the creation of a serverless infrastructure to generate emails and push notifications, highlighting the use of Redis as a datastore for queuing messages and enabling batch notifications. The post concludes by encouraging readers to share their experiences and any queries regarding the setup process.