Navigating Azure Hierarchy

#webdev #cloudcomputing #hierarchy #azure

As part of my cloud engineering journey, I've been diving deep into Azure architecture, and I'd love to share my experience with you.

Recently, I worked on designing an Azure hierarchy for Beysville, and I'm excited to walk you through it.

Let's break it down:

Root (Tenant): The foundation of our Azure setup is the tenant, which represents Beysville's unique identity - beysville.online.
Management Groups: These groups help organize subscriptions and resource groups, enabling efficient management and governance.
Subscriptions: We created separate subscriptions for different departments, ensuring isolated environments for development, testing, and production.
Resource Groups: Each subscription contains resource groups, which hold related resources (e.g., VMs, storage, networks).
Resources: Finally, we have individual resources, such as virtual machines, databases, and storage containers

Designing this hierarchy for Beysville taught me:

The importance of scalable architecture
Effective resource organization and governance
Seamless collaboration between departments

How to reduce TTFB

In the past few years in the web dev world, we’ve seen a significant push towards rendering our websites on the server. Doing so is better for SEO and performs better on low-powered devices, but one thing we had to sacrifice is TTFB.

In this article, we’ll see how we can identify what makes our TTFB high so we can fix it.