#message-broker

The procedure that gives a new project its whole infrastructure from generators, in the order the stacks depend on each other: log first, then storage and broker, then the gateway, then the application — with the public steps kept manual.

Opening a broker to browsers and devices on the internet is less about encryption than identity. Each entrance now accepts one kind of credential, every token is bound to its own name and addressed to this broker, and TLS ends in nginx.

A laptop and a borrowed Colab GPU talked through a public MQTT broker that anyone could read. Giving that channel an identity took an afternoon on the broker and eight obstacles in the clients — mostly safeguards that were right for the old setup and wrong for the new one.

A Colab runtime has no address anyone can call, so a laptop and a borrowed GPU talk through a broker both of them dial out to. Sending commands was the easy half. Knowing — whether the worker is alive, whether a command arrived once — is where six silent failures hide.