Take a look at the code

The supply for chessmsgs.com is offered on GitHub at https://github.com/gregsramblings/chessmsgs

Deciding the place to host it

The internet hosting necessities are easy. I wanted help for Node.js/Categorical, area mapping, and SSL. There are a number of choices on Google Cloud together with Compute Engine (VMs), App Engine, and Kubernetes Engine. For this app, nevertheless, I needed to go fully serverless, which shortly led me to Cloud Run. Cloud Run is a managed platform that allows you to run stateless containers which can be invocable by way of net requests or Pub/Sub occasions. 

Cloud Run can also be mainly free for one of these undertaking as a result of the always-free-tier contains 180,000 vCPU-seconds, 360,000 GiB-seconds, and a pair of million requests per thirty days (as of this writing—see the Cloud Run pricing page for the most recent particulars). Even past the free tier, it’s very cheap for one of these app since you solely pay whereas a request is being dealt with in your container occasion, and my code is straightforward and quick.

Lastly, deploying this on Cloud Run brings plenty of added advantages reminiscent of steady deployment by way of Cloud Build, and log administration and evaluation by way of Cloud Logging, each of that are tremendous simple to arrange.

What’s subsequent?

If this all of the sudden turns into the preferred web site of the day, I’m really in good condition from a scalability perspective due to my choice to make use of Cloud Run. If I actually needed to engineer this for excessive masses, I may simply deploy it to a number of areas all through the globe and set up a load balancer and presumably a CDN. I additionally may separate the hosting performance from the picture technology performance to permit every to scale as wanted.

Once I first began excited about the picture technology, I naturally thought of caching the photographs in Google Cloud Storage. This may be simple to do and storage is loopy low-cost. However, then I did a little bit of analysis and realized the next enjoyable details. After two strikes (one transfer for every participant), there are 400 completely different distinct board positions. After every participant strikes once more (two strikes every), this quantity is now 71,782 distinct positions. After every participant strikes once more (three strikes every), the quantity is now 9,132,484 distinct positions! I may achieve a little bit of efficiency by caching the preferred openings, however every recreation would shortly transcend the cached photographs so it didn’t appear value it. By the way in which, to cache each doable board place could be about 1046 positions, which is a huge quantity that doesn’t actually have a identify.


This was a enjoyable undertaking – nearly therapeutic for me since my “day job” doesn’t enable a lot time for writing code. If this turns into in style, I’m positive others may have concepts on how you can enhance it. 

This was my first hands-on with Cloud Run past the wonderful Quick Starts (examples for Go, Node.js, Python, Java, C#, C++, PHP, Ruby, Shell, and many others.). Due to my function in developer advocacy at Google, I used to be conscious of most Cloud Run capabilities and options however after utilizing it for one thing actual, I now perceive why builders adore it!

The place to study extra

Leave a Reply

Your email address will not be published. Required fields are marked *