Five years ago when I started tracking media buzz around stateful architectures, I’d see a few articles every month about running stateful containers. That's about when Caitie McCaffrey first shared this awesome …

Aggregating data from heterogeneous REST APIs and streaming sources can be a pain. In order to achieve real-time insights or visualizations, developers need to efficiently combine REST and streaming data …

I’ve written previously about Scott Clarke’s Greenhouse demo app because it’s a good example of how to build integrations between external frameworks and Swim. While Swim functions perfectly well on …

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 last post in a three part series about the future of the Web. You can read parts 1 and 2 here. Like MS-DOS, Swim is "integrated software that consists of a persistent transactional memory …

This is the second post in a three part series about the future of the World Wide Web. Click here to read part 1 or part 3. "The World Wide Web was designed to …

This is the first post in a 4 part series about the future of the World Wide Web. Read part 2 here and you can find part 3 here. How do you write …