Systems | Development | Analytics | API | Testing

In less than 20 years, mobile apps have grown from a bright new idea to a cornerstone of our daily lives. And while Android accounts for the lion’s share of the market, iOS usage continues to grow exponentially: in 2024 alone, iOS apps and games were downloaded around 35 billion times. The Apple App Store is both a shop window and a marketplace for this global industry. But as iOS developers, how do we actually submit a mobile app to the store?

Integration testing verifies that multiple components of your Django application work together correctly. Unlike writing unit tests that examine isolated functions or methods, the Django integration testing process validates entire user workflows, tests database transactions, and system interactions. Django's testing framework provides specialized tools for creating realistic automated test scenarios that mirror production environments.

Boosting the scalability of your backend applications often means rethinking how you manage asynchronous data. That’s where reactive programming comes into play: a paradigm that treats data streams as first-class citizens, allowing your code to respond to data changes as they occur. While Node.js wasn’t built with reactive programming in mind, libraries like RxJS and Bacon.js support that approach.

In parts one and two of this series, we familiarized ourselves with the ins and outs of Showcase. Now, we'll dive into samples, Showcase's main feature. Samples show how a component can be used in a real application.

‍San Francisco, US — November 12, 2025 — Bitrise, the leading DevOps platform for mobile, today released Bitrise Mobile Insights 2025, a comprehensive benchmarking report based on aggregated, anonymized data across 10M+ Bitrise builds over 3.5 years across its global customer base (January 2022–June 2025). “Innovation is accelerating, user expectations are rising, and engineering teams face constant pressure to deliver,” said Barnabás Birmacher, CEO of Bitrise.

We are noticing that some of our requests are starting to get slow and server load increases. Checking the process list of our server, for example with htop reveals that our FPM workers are taking up all of our CPU time. Checking the health with our basic toolset of lsof to show open network connections and strace to show syscalls does not reveal any activity. This means that the workers are spending time processing data without any externally visible activity.