Data source: swyx's twitter data
id | user | created_at | full_text | retweeted_status | quoted_status | place | source | truncated | display_text_range | in_reply_to_status_id | in_reply_to_user_id | in_reply_to_screen_name | geo | coordinates | contributors | is_quote_status | retweet_count | favorite_count | favorited | retweeted | possibly_sensitive | lang | scopes |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1424172141289689090 | 33521530 | 2021-08-08T00:54:32+00:00 | "How do you cut a monolith in half?" LOTS of gold in @tef_ebooks's exploration of why msg brokers don't replace load balancers or databases. The long-lived section is very relevant to @temporalio (lock manager + db + scheduler + protocol). https://programmingisterrible.com/post/162346490883/how-do-you-cut-a-monolith-in-half https://twitter.com/swyx/status/1424172141289689090/photo/1 | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 266] | 1417315435892985856 | 33521530 | swyx | 0 | 1 | 10 | 0 | 0 | 0 | en | |||||||
1424310472350654464 | 33521530 | 2021-08-08T10:04:13+00:00 | @simonw tragedy of the critical bug commons: if everyone waits a few weeks before upgrades then the purpose of waiting a few weeks before upgrades is defeated! optimal - round robin upgrades to share bug discovery load? | 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [8, 220] | 1424078556406042625 | 12497 | simonw | 0 | 1 | 3 | 0 | 0 | en |