TechOps Examples
Hey — It's Govardhana MK 👋
Welcome to another technical edition.
Every Tuesday – You’ll receive a free edition with a byte-size use case, remote job opportunities, top news, tools, and articles.
Every Thursday and Saturday – You’ll receive a special edition with a deep dive use case, remote job opportunities, and articles.
AI skilled professionals are earning up to 56% higher wages.
Companies are rewarding engineers who can build with AI.
THE CODE - Learn how to code faster with AI in 5 mins a day.
Loved by 350k+ devs, engineers at Meta, Google, OpenAI, and more.
Somehow, it’s free - Sign up to get The Ultimate Claude Code Guide + 200 Free Engineering resources.
👀 Remote Jobs
BlancVPN is hiring a Senior Infrastructure Engineer
Remote Location: Worldwide
Northflank is hiring a Cloud Infrastructure Engineer
Remote Location: Worldwide
📚 Resources
Looking to promote your company, product, service, or event to 50,000+ Cloud Native Professionals? Let's work together. Advertise With Us
🧠 DEEP DIVE USE CASE
How CORS Works in Modern Applications
In modern cloud apps, the frontend and backend rarely sit on the same domain. Your UI may be on your-domain.com, while files, APIs, or services could live on other-domain.com. This split architecture improves scalability but also triggers browser security checks that block requests across domains.
What is CORS?
Cross Origin Resource Sharing (CORS) is the mechanism that lets a browser safely fetch resources from a different origin. It’s essentially a contract: the server explicitly states which external origins are trusted and which request methods are allowed. Without it, cross domain calls fail by default.
Key terms you should know:
Origin → The domain where your app runs (e.g., your-domain.com).
Cross Origin Server → The domain hosting the resource (e.g., other-domain.com).
Access-Control-Allow-Origin → The server response header that decides if the browser can use the resource.
How a Typical CORS Flow Works
Preflight Request
The browser first sends an OPTIONS request to the cross-origin server (other-domain.com).
This request checks whether the origin (your-domain.com) is allowed to access the resource.
Preflight Response
The cross origin server responds with its CORS policy.
It specifies which origins and HTTP methods (GET, PUT, POST, etc.) are permitted.
Actual Request
If the preflight check passes, the browser makes the real request to the cross origin server.
Response
The cross origin server responds with the resource.
Since the origin was allowed, the browser accepts the response and delivers it to the app
Without the preflight negotiation, browsers would block the request entirely. This handshake ensures only trusted origins can access sensitive data, keeping cross domain interactions both functional and secure.
Having covered the basics, let us look into the real world patterns in AWS.
🔴 Get my DevOps & Kubernetes ebooks! (free for Premium Club and Personal Tier newsletter subscribers)
Upgrade to Paid to read the rest.
Become a paying subscriber to get access to this post and other subscriber-only content.
UpgradePaid subscriptions get you:
- Access to archive of 250+ use cases
- Deep Dive use case editions (Thursdays and Saturdays)
- Access to Private Discord Community
- Invitations to monthly Zoom calls for use case discussions and industry leaders meetups
- Quarterly 1:1 'Ask Me Anything' power session
