Hacker News new | past | comments | ask | show | jobs | submit login

> But when pressed, very few people were able to describe the contents of those messages in any detail.

Can you explain why this matters? It’s an architecture interview right? Not an API/Worker/Queue design exercise.

It’s not like I don’t expect someone to be eventually able to figure out the contents of the payload, I’d just not expect it to be at the forefront of their mind.




Emails with attachments vs plain text messages. Binary content. Compressed content. Size matters, especially at scale.


Ah, gotcha. We're still talking about 'what kind' of messages. Not, 'which fields', which is what I understood.




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

Search: