Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Why not treat email as a dynamic event source?

Imagine an architecture where incoming emails are parsed to extract key metadata such as sender, subject, category, priority, and body content and then published to a local Kafka queue. From there, applications can subscribe to specific topics or filters, just like they do with notifications or system events.

Think of the possibilities:

- A CRM system could subscribe to emails from clients and auto-log interactions.

- A task manager could subscribe to emails tagged as “Action Required.”

- A personal assistant app could subscribe to calendar invites or travel confirmations.

Users could manage these subscriptions through a simple UI, similar to notification preferences. This model treats email as a stream of structured events, enabling real-time automation, integration, and personalization.

Where things get interesting is what you could do with streaming from multiple sources: not just email, but Slack, Teams, social media accounts - all the different ways you connect with people.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: