Systems | Development | Analytics | API | Testing

The global financial services industry is a complex landscape: a patchwork quilt of regulatory frameworks, technologies, and markets with very different customer needs. To be the most profitable, the most competitive, and the most efficient it can be, a financial services provider must find a way to navigate that complexity, and sales and finance teams hold pieces of the puzzle. And putting the pieces together isn’t as easy as it may look at first glance.

Confluent has been instrumental in enabling customers from various industries to develop real-time stream processing solutions using Apache Kafka. While many of these use cases demand low-latency and real-time processing, stream processing is also increasingly being utilized for ingesting logging and telemetry data. This type of data typically features a high ingest rate, but allows for a higher tolerance for end-to-end processing time.

Concurrency is the ability of an app to perform multiple tasks at once, and it’s a crucial concept for apps that need to perform multiple tasks at once in an efficient, usable way. Thankfully Swift has made great strides with concurrency, and now provides simple tools for writing robust apps that are responsive and enjoyable to use. In this article we’ll explore two main ways of using threads for concurrency models.

Exceptions in C# are like fire alarms – they're loud, disruptive, and absolutely essential. And much like fire alarms, most beginners either ignore them or disconnect the batteries. Let me explain what we're dealing with here. In the C# world, exceptions are specialized objects that capture all the details when something goes wrong in your code. They're not just error messages – they're fully-fledged objects that inherit from the System.Exception class.

In the fast-paced world of API development, understanding the distinction between stateful and stateless applications can be a game-changer. Did you know that stateless REST APIs are the backbone of scalable web applications, handling millions of requests with ease? Yet, for many developers, the nuances of these architectures remain a mystery. As the demand for efficient and scalable systems grows, grasping the fundamentals of stateful vs. stateless applications becomes increasingly vital.

Playwright is a Microsoft-created NodeJS package with capabilities that are quite similar to Puppeteer. Both libraries enable you to automate browser-based tasks. With Playwright, you can launch or connect to a Chrome, Edge, Safari, or Firefox browser and exchange instructions. The DevTools protocol (for Chrome browsers) and a bespoke protocol (for Firefox and WebKit browsers) are used for these messages.

The evolution of diagramming in software mirrors the evolution of software development: from static and planned upfront → to lightweight and iterative → to automated and real-time. The 1968 “Mother of All Demos” by Douglas Engelbart wasn’t just a showcase of new technology—it was a glimpse into the future of how we interact with and visualize complex information, including software systems.

Last week, industry leaders gathered at the Game Technology Summit during GDC 2025 to explore emerging trends and challenges in game development. The panel discussion, moderated by Jase Lindgren (Sr. Solutions Engineer and P4 Evangelist, Perforce), featured insights from Colin Walder (Engineering Director, CD PROJEKT RED), Joshua Orellana (Head of Animation and Games, Halon Entertainment), and Matt Ellis (Game Dev Advocate, JetBrains).

Software has become a core component of modern vehicles, so much that software defined vehicles (SDVs) are transforming the automotive market, bringing key features to the software rather than the hardware of the vehicle. But developing high-quality code for software defined vehicle architecture is challenging.

When building Node.js applications that interact with relational databases, you have a large variety of tools at your disposal to manage and execute queries. The three most common approaches — raw SQL, query builders, and Object-Relational Mappers (ORMs) — offer unique advantages and challenges, making it difficult to decide which is best. In this guide, we will compare the strengths, trade-offs, and use cases of all three approaches.