How do you evaluate open source technologies, like Kubernetes and Swim, when there's so much hype? Last post, we explored the challenges of architecting a real-time application, which are due in part …

We need to have a serious talk about "real-time." These days, it seems like there are more real-time Web technologies to choose from than trendy superfoods (see: Irish black pudding, …

Here's a cool demo from Swim developer, Scott Clarke. The Swim Greenhouse Demo (found here on GitHub) uses Swim, NodeJS, and Python to make an application which learns in real-time from a …

Swim can be a challenge to explain to people, even if the audience is fairly technical. Unless you've had firsthand experience building and running at-scale distributed applications with low latency requirements, it's difficult …

This is the third post in a four part series about the future of the Web. You can read parts 1 and 2 here. Stay tuned, part 4 is coming soon! Like MS-DOS, Swim is "integrated software that consists …

This is the second post in a 4 part series about the future of the World Wide Web. Click here to read part 1. Stay tuned, parts 3 and 4 are coming soon! …

This is the first post in a 4 part series about the future of the World Wide Web. Read part 2 here. Stay tuned, parts 3 and 4 are coming soon! …

Serverless computing is a seductive and powerful addition to a cloud developer’s arsenal. But despite its elegance, serverless is not the right architecture for most edge applications. Combined with the …

Application developers frequently choose REST in the name of simplicity, but for real-time apps, REST introduces unnecessary complexity and performance bottlenecks. REST based APIs, stateless computing and database-centric applications are the …

The web and IaaS clouds only work because of REST and stateless computing. That and a couple of other infrastructure abstractions: load balancing, and a database of some sort. The …