Ideal extension Architecture

Different people do things in different waits that meets their requirements to achieve the needs of their application.

The method you describe might work perfectly fine for your application.

Also note, that every 30 mins or so, Twitch will refresh the Access Key for the user/extension which will generally result in an EBS ping saying “here’s the new key”

I have three extensions published, all three have different client/EBS communication methods, because all three do different things and have different needs.

So “ideal”, there is no “ideal”, design meets what the application and available resources needs.