Facilitating the Spread of Knowledge and Innovation in Professional Software Development

1,699,303 Jan unique visitors

News Articles Presentations Podcasts Guides

Development

Designing for Concurrency: the Hilbert’s Hotel Problem in Go

In this article, we want to show how achieving concurrency is the result of an appropriate design. A concurrent solution may turn out to be more elegant and easier to reason about than an equivalent sequential algorithm. To illustrate these concepts we use, as an example, the Hilbert’s Hotel mathematical problem.

All in development

Architecture & Design

Expanding GraphQL Federation at Netflix with Tejas Shikhare

GraphQL can be a great choice for client to server communication, but it requires investment to maximize its potential. Netflix operates a very large, Federated GraphQL platform. Like any distributed system, this has some benefits, but also creates additional challenges. In this episode, Tejas Shikhare explains the pros and cons of scaling GraphQL adoption.

AI, ML & Data Engineering

Resilient Real-Time Data Streaming across the Edge and Hybrid Cloud

Kai Waehner explores different architectures and their trade-offs for transactional and analytical workloads. Real-world examples include financial services, retail, and the automotive industry.

All in ai-ml-data-eng

Culture & Methods

Your Tech Stack Doesn’t Do What Everyone Needs It To. What Next?

Stack extensibility is an essential trait of well-designed IT ecosystems. Low-code BPA (Business Process Automation) has advantages that puts it at the forefront of approaches to stack extensibility. Learn how low-code software increases process resiliency by empowering business teams with an easy-to-use, easy-to-understand and, most of all, IT-sanctioned set of tools.

All in culture-methods

DevOps

If Twitter Doesn’t Have a Staging Environment, Should Anyone?

With Twitter revealing they do not have a staging environment, how important is staging to delivering quality? When so many tasks are shifting to the developer these days and no one best developer approach fits all, how do dev teams determine the best developer methodology for them and their company?