Great post, beautiful site (and fast!). One passage caught my eye:
> Deployments are not zero-downtime at this point and I’m planning to switch to an AB-style deployment model once the site has enough traffic to warrant it
Do you mean blue-green deployment ( https://docs.cloudfoundry.org/devguide/deploy-apps/blue-gree... )? In any case note that you can do that even with just a single compute–just run both instances of the app in the same compute, on different ports–say, 3000 and 3001–and use a reverse proxy like Nginx to load-balance incoming HTTP traffic between them. Then you get blue-green deployment almost for free.
> The low runtime error rate is due to the amount of stuff that Racket manages to catch at compile time compared to other dynamic languages and to some fairly extensive automated testing.
Interested to know if typed racket was used for this, and if so, what the experience was like!
I'm a fairly experienced Racket developer (6 years) but it was my first time trying Typed Racket. I ended up not keeping the part of my code that I typed.
> Deployments are not zero-downtime at this point and I’m planning to switch to an AB-style deployment model once the site has enough traffic to warrant it
Do you mean blue-green deployment ( https://docs.cloudfoundry.org/devguide/deploy-apps/blue-gree... )? In any case note that you can do that even with just a single compute–just run both instances of the app in the same compute, on different ports–say, 3000 and 3001–and use a reverse proxy like Nginx to load-balance incoming HTTP traffic between them. Then you get blue-green deployment almost for free.