-
cloudwithchris.com
Cloud With Chris is my personal blogging, podcasting and vlogging platform where I talk about all things cloud. I also invite guests to talk about their experiences with the cloud and hear about lessons learned along their journey.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
That's precisely the way that I architected Yu-Gi-Oh Cards, a pet project that I had started working on a while ago (please don't judge my software development skills!). This project actually implements a JAMStack approach by using VueJS as the front end framework, and then calling the backend APIs through a serverless API Management deployment which in turn calls serverless Azure Functions. There are aspects of the solution which aren't serverless, such as the CosmosDB and the Azure Search instance, but you can understand how designing the front end website and backend APIs in this way makes for great cost savings.
Similarly, Cloud With Chris is an example of a JAMStack site, driven by Hugo, a static website generator. Rather than calling any backend APIs, the content is all entirely driven by markdown which is hosted in the GitHub repository mentioned a moment ago. This means I'm not calling any external APIs. Instead, the content is finalised at deployment time. I run a command in my GitHub Actions (Hugo build) which goes ahead and takes my site's configuration, necessary theme information and content, and renders the needed files to generate the set of webpages to render to my clients. The content is then uploaded to an Azure Blob Storage account which is publicly accessible and configured using the Static Website functionality.
Similarly, Cloud With Chris is an example of a JAMStack site, driven by Hugo, a static website generator. Rather than calling any backend APIs, the content is all entirely driven by markdown which is hosted in the GitHub repository mentioned a moment ago. This means I'm not calling any external APIs. Instead, the content is finalised at deployment time. I run a command in my GitHub Actions (Hugo build) which goes ahead and takes my site's configuration, necessary theme information and content, and renders the needed files to generate the set of webpages to render to my clients. The content is then uploaded to an Azure Blob Storage account which is publicly accessible and configured using the Static Website functionality.