Bird’s Eye Insights

Many transit agencies offer a public API for 3rd parties to request the latest information on vehicle status and scheduling. However, handling a large volume of API requests with limited infrastructure and resources can be challenging - either from the thousands of concurrent users making requests or due to frequent pull requests necessary when trying to build a live dashboard. The limitations of traditional architectures restrict these public agencies to throttling API requests at the lowest speed in order to handle the load. With Swim, any existing REST API is automatically transformed into a real-time "streaming" API.


digital twin vehicles


streaming aggregations


data reduction

Whereas traditional API’s for real-time dashboards are initiated by endless pull requests looking for data updates, Swim API’s only push state changes and can reduce the volume of data traffic by a factor of 800%. Even more, Swim allows anyone to add “zero-latency” analytics and continuously monitor routes, operational performance, and the overall efficiency of any complex system at marginal cost.

The Future of Transit

Each vehicle was modeled with Swim to capture speed, direction, and the next stop for approximately 40,000 buses on a public transit feed. Swim was then deployed in a single environment to continuously poll that REST API and deliver the first continuously streamed updates to any subscriber of this real-time API.

Other Streaming Apps

Want to see how we’ve used Swim to build other streaming applications? Check out some of our other projects to experience Swim in action and learn tips, tricks and best practices for building streaming applications.

Swim applications continuously provide the latest updates to empower users with the most relevant insights. Swim doesn’t just stream data; it runs application logic in-stream to power real-time analytics, business workflows, dashboards, and UIs. Instead of out-of-date snapshots, Swim mirrors your entire application in real-time.