logoalt Hacker News

reticulates • today at 12:10 PM • 2 replies • view on HN

I'm not familiar with your product, just the blog post + cell architecture documentation. Question: the documentation states that basins are assigned to a cell on creation and cannot move. Why choose to have explicit DNS records instead of wildcards with a subdomain per location? e.g: {basin}.us-east-1.s2.dev where *.us-east-1.s2.dev points to the cell? My best guess is that you prefer to have explicit architecture in case you need to move to a new cell for some reason, but maybe there was a different reason? The stuff around hitting the database on every query that necessitates a firewall seems like a huge risk vs. a wildcard CNAME which adds no additional burden.


Replies

reticulates • today at 12:31 PM

Also, unsolicited advice but having your website, integration endpoints, status page and email under the same domain is a bad idea, a single point of failure. Especially a domain that is due to expire in just a few months. You should have a separate domain for infrastructure and a separate status page domain, each renewed for 10 years in advance (the maximum). e.g: s2.dev for website, s2status.com for status page and s2stream(s).com for your Basin URLs.

➕ show 1 reply
misker1 • today at 1:04 PM

The main two reasons: we have multiple cells per location (we want to keep cells decent in size to reduce failures) and a move between cells is something we have on the roadmap. I tried to find a wildcard solution at the beginning of building this, I just couldn't find a good one.