Develop a local websocket server backend #211

New Issue

Closed

opened 2022-07-05 01:39:14 +02:00 by blacklight · 0 comments

blacklight commented

2022-07-05 01:39:14 +02:00

Owner

Created by: BlackLight

A local websocket server backend (and later a more advanced implementation through a pub/sub mechanism like Apache Kafka) is a good alternative for people who don't want to rely on PushBullet to manage their automation tasks and prefer to have all the flows running on their own infrastructure. Moreover, it's a good start to develop a kind of backend-agnostic architecture, where you can plug any backend you prefer (PushBullet, Google pub/sub, Kafka, local websocket...) to dispatch and synchronize the events across all your devices.

*Created by: BlackLight* A local websocket server backend (and later a more advanced implementation through a pub/sub mechanism like Apache Kafka) is a good alternative for people who don't want to rely on PushBullet to manage their automation tasks and prefer to have all the flows running on their own infrastructure. Moreover, it's a good start to develop a kind of backend-agnostic architecture, where you can plug any backend you prefer (PushBullet, Google pub/sub, Kafka, local websocket...) to dispatch and synchronize the events across all your devices.