About
With over 20 years of IT experience spanning multiple industries and technologies, Mark…
Experience
Licenses & Certifications
Volunteer Experience
Languages
-
English
Native or bilingual proficiency
Other similar profiles
Explore more posts
-
John Adewumi
Why I love OCI Most clouds attempt to be “helpful” by rebooting infrastructure in the background when a label is changed. Not OCI. OCI prioritizes Data Plane Integrity. When you change a tag, OCI protects your workload and waits for you to make the call. In this 60-second clip, I break down: - The “Metadata Gap” in OKE - Why the dashboard isn’t the source of truth - How to build intelligent triggers to truly control your infrastructure Don’t trust the green light. Trust your code.
-
Stephen Jones
I watched Werner Vogel's AWS re:Invent Keynote this week, which inspired my latest post. 🤔 The five pillars of the Renaissance Developer are a modern engineering mindset that blends depth, breadth, curiosity, and systems thinking into a practical career advantage. Here’s what’s inside: ✨ How the keynote’s themes map directly to what engineers need next 🧭 Curiosity as a core engineering multiplier 🔧 Mechanisms > magic — thinking like an architect, even when you’re hands-on 🧩 Why T-shaped capability is no longer optional 🎨 A visual model that merges Renaissance artistry with cloud-era engineering Check it out - https://lnkd.in/g3J3JJzp
-
Arun Seetharaman
𝗪𝗵𝗲𝗻 𝗔𝘇𝘂𝗿𝗲 𝘀𝗻𝗲𝗲𝘇𝗲𝗱, 𝗔𝗪𝗦 𝗰𝗮𝘂𝗴𝗵𝘁 𝗮 𝗰𝗼𝗹𝗱 - 𝗲𝘃𝗲𝗻 𝘁𝗵𝗼𝘂𝗴𝗵 𝗔𝗪𝗦 𝘄𝗮𝘀𝗻’𝘁 𝘀𝗶𝗰𝗸. In the outage yesterday, Microsoft’s Azure Front Door went down, users across the internet started reporting outages on AWS too, even though AWS was fully operational. It looked like both were “down.” In reality, it was a domino effect. Modern applications rarely live in one place. A single user-facing service might route through Azure for content delivery, AWS for compute, and Cloudflare for DNS. So when one link fails upstream, it cascades, producing symptoms across other clouds that look like outages but aren’t. The internet doesn’t fail neatly; it fails sideways. AWS’s clarification that its own systems were healthy underscores how nuanced cloud monitoring and communication must now be. As architectures go hybrid and distributed, the ability to interpret context becomes as critical as uptime itself. It’s no longer enough to know whether a service is “up.” You need to know why something appears down — and whether the root cause lives in your cloud, your provider, or your provider’s provider. That’s where verified telemetry (like AWS Health Dashboard) and calm, data-driven communication matter most. The lesson: 𝗖𝗹𝗼𝘂𝗱 𝗿𝗲𝗹𝗶𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗶𝘀𝗻’𝘁 𝗯𝗶𝗻𝗮𝗿𝘆 𝗮𝗻𝘆𝗺𝗼𝗿𝗲. 𝗜𝘁’𝘀 𝗮 𝘀𝘆𝘀𝘁𝗲𝗺 𝗼𝗳 𝘀𝘆𝘀𝘁𝗲𝗺𝘀. 𝗔𝗻𝗱 𝘀𝗼𝗺𝗲𝘁𝗶𝗺𝗲𝘀, 𝘆𝗼𝘂𝗿 𝗼𝘂𝘁𝗮𝗴𝗲 𝗶𝘀 𝘀𝗼𝗺𝗲𝗼𝗻𝗲 𝗲𝗹𝘀𝗲’𝘀.
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top content