Systems | Development | Analytics | API | Testing

Stepping into the world of Apache Kafka® can feel a bit daunting at first. I know this firsthand—while I have a background in real-time messaging systems, shifting into Kafka’s terminology and concepts seemed dense and complex. There’s a wealth of information out there, and it’s sometimes difficult to find the best (and, ideally, free) resources.

The greater tech community was front row for a high-stakes corporate saga this past weekend, complete with more plot twists than the Succession series finale.

In Swift there are 3 primary types of collections to store your data in a structured way, namely: In this article we aim to give you an overview of each. Specifically we want to show how they’re declared, illustrate the most common operations of each, provide comparisons between them where applicable and highlight the various performance considerations.

Hello there! My name is Maciej Mensfeld, and some of you might recognize me from my involvement in RubyGems Security, OSS commitments, or perhaps from Karafka: a multi-threaded, efficient Kafka processing framework tailored for Ruby and Rails. While I generally pen my thoughts on my personal blog, today's post is unique. This article results from a collaborative effort with the brilliant people over at AppSignal. To set the record straight, I don't work for AppSignal.

Closures provide a powerful, flexible way for iOS developers to define and use functions in Swift, replacing the blocks used in its predecessor Objective-C. They provide self-contained modules of functionality that you can move around in your code, similar to the lambdas found in other programming languages. Crucially, closures can capture and store references to any constants and variables from the context in which they’re defined.