vasanthk

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

1. Clarify and agree on the scope of the system

• User cases (description of sequences of events that, taken together, lead to a system doing something useful)
  • Who is going to use it?
  • How are they going to use it?

mislav

Hypothetical setup:

sender → email to user@example.com → forwarder app at example.com → Mailgun → user@gmail.com → Gmail recipient

The problem with Mailgun being used as middleman is when recipient marks the email from a particular sender (who might be malicious) as spam, Mailgun will block the forwarder app from sending any more emails to user@gmail.com.

This is because Mailgun is designed for a scenario where the app at @example.com is the originator of the messages and not simply the proxy.

So if one uses Mailgun (or DNSimple, that uses Mailgun) for email forwarding, they will stop receiving email completely as soon as they mark one email as spam.

endolith

# -*- coding: utf-8 -*-
"""
Go to Google Bookmarks: https://www.google.com/bookmarks/

On the bottom left, click "Export bookmarks": https://www.google.com/bookmarks/bookmarks.html?hl=en

After downloading the html file, run this script on it to generate a KML.

"""