现在线上服务通知用户无非就两种方式,email与push notification。email是异步的通知机制,假设用户不会及时看到消息并且不用立刻做出响应;而push notification是syncronous的,假设用户能及时看到消息并会用户立即响应。配合阅读前几天的这篇:恰当的通知用户的手段:短信,邮件还是推送? 文中认为push notification最重要的指标是用户损耗率:有多少用户是因为收到过多push notification而卸载了你的app。
Churn — the most important thing about Push Notifications you’re probably not measuring
我对这篇文章产生共鸣,因为最近在清理公司里邮件和push notification 的代码。
来自Jay Kreps的博文(当时他在Linkedin,现在是基于Kafka的实时数据处理服务Confluent的创始人/CEO)。相信很多人已经拜读过这篇神文了。每次读都有新的体会。
You can't fully understand databases, NoSQL stores, key value stores, replication, paxos, hadoop, version control, or almost any software system without understanding logs; and yet, most software engineers are not familiar with them.
想要更深入了解的同学,可以看他最近出的书: I Heart Logs: Event Data, Stream Processing, and Data Integration