Final decision on WebSocket state updates

A follow-up to earlier decisions around using WebSockets to communicate.

In this audio clip, I talk about how the design did work out as well as the initial indications but there were a few other points I wanted to make.

First of all, I ended [...]

I talk a little about my love-hate relationship with notification-based design patterns in application development, based on some recent ideas around Cacophony.

While these approaches seem to make the high-level responsibilities within the system [...]

I was reminded of the very powerful and elegant concept of binary streams when resolving a memory problem caused in the network library under Cacophony, recently.

I talk about how data streams can move data in and out of a program without needing [...]

I talk a little bit about the idea in software development of "eating your own dogfood" as well as the narrower idea of self-hosted systems (for example, building the version control system you use to manage the software you are building).

There [...]

As an update from my last post about using WebSockets to stream updates to the front-end, instead of just using REST-based polling, I talk a bit about some observations made through this.

In general, this seems to lend itself to thinking about the [...]

Using WebSocket-backed event-based updates instead of REST polling

Something I started playing with in Cacophony 2.0-pre5 was using WebSockets to send dynamic data updates to the front-end, instead of polling a REST end-point. Specifically, I did this for the status page as its changes of state weren't directly [...]

Just a quick talk about the thought process behind the "StandardAccess" approach used in Cacophony 2.0 pre4. That is, using a coarse-grained locking and data abstraction instead of the more fine-grained approach previously being used.

Basically, I [...]

We often hear companies talking about how their offering is "new technology" but how true is that, really? In this video, I talk about how this distinction is missing and that most of what is pitched as "new technology" is just a product or [...]

A short bit of a ramble about a concern I sometimes see people make where they "don't want to block" while blocking is actually a pretty fundamental way that the system works. The concern isn't with blocking, so much as blocking in the wrong place.

Just a quick one, mostly just to test out the new Cacophony 2.0-pre0 release (doing this with in-browser recording).

I talk about the difference between code and data or, more correctly, how they aren't as different as often thought and that the [...]

While I am not someone who does much work in tradition web back-ends, this is idea I find interesting.

I talk a little bit about what an event store is and how that differs from a traditional database.

This involves discussions of some scalability [...]

I talk about some concerns I have related the direction of the conversation around block production, related to proof-of-work and proof-of-stake systems.

Basically, I think that the discussion centres too strongly around environmentalism and energy [...]

As a way of further testing and dog-fooding Cacophony, I wanted to start a channel to bring up or discuss technical topics in a fairly ad-hoc way. This is just a quick intro to that idea.

(recorded a few weeks ago)