10 ms·
In my previous job I was the lead engineer of the MessengerPeople Unified Messaging API, so congrats, this looks awesome! :) I wonder how you solved media file
by 9dev 5y ago
In my previous job I was the lead engineer of the MessengerPeople Unified Messaging API, so congrats, this looks awesome! :)
I wonder how you solved media files and attachments? I remember having major headaches around transporting, storing and retrieving media files for different messaging backends, especially WhatsApp and Telegram.
Also, any plans to support WhatsApp Business containers directly?
- chrismatic 5y agoHi, Chris from Airy here. Glad that you like it! Yes this was a very challenging problem. After many iterations we came to the conclusion that in general it's best to have no opinion on the structure of the content that is being sent. So we store every message exactly as we receive it and do platform specific file interactions in a separate stream. We then store the results in a metadata topic and use that to render messages on-demand. This immutable approach makes retrying and storage migrations easy and safe. Regarding WhatsApp Business containers we are still waiting for them to wrap up their Beta. Currently we support WhatsApp and SMS via our Twilio messaging source (https://airy.co/docs/core/sources/whatsapp-twilio https://airy.co/docs/core/sources/whatsapp-twilio), but we definitely plan on making it a first class citizen. Hope I could answer your questions! :)