Junwei Zhao

Earlier this month, AWS released some news regarding Lambda users! On the 1st May, AWS is rolling out major updates to Lambda logging: - Volume-based tiered pricing for Amazon CloudWatch Logs. - New Lambda log destinations: Amazon S3 and Amazon Data Firehose. Designed to cut costs for high-volume Lambda deployments and offer greater flexibility for integrating with preferred monitoring tools. #AWS #AWSPartner #Lambda #CloudWatch #Serverless #DevOps #CloudComputing https://lnkd.in/e_p4TdsW

7

A quick update on Brighter support for AWS SDK V4. We will support AWS SDK V4 in V10 from RC2 onwards. RC2 is due out within a fortnight, with a final release of V10 hopefully in early August. We will continue to support AWS SDK V3 in V9 and in V10 for a period of time. We are aware that forced upgrades to AWS SDK V3 to V4 caused by frameworks updating causes issues with missing method exceptions and are seeking to prevent that. We will review if we need to look at AWS SDK for V4 when we review V10 uptake and migration.

11

Redis has officially returned to open-source licensing with the release of Redis 8 under AGPLv3, marking a significant shift from the controversial SSPL licence that divided the community for years. The decision represents a victory for open-source advocates, driven by internal discussions at Redis and the recognition that SSPL failed to gain acceptance from both the Open Source Initiative and the broader software community. Why This Matters for Rails Developers: 🔹 Redis remains the most popular caching and session store for Rails applications 🔹 AGPLv3 provides clearer licensing terms than the ambiguous SSPL 🔹 Open source status ensures continued community contributions and ecosystem growth 🔹 Rails developers can confidently build on Redis without licensing concerns 🔹 Vector Sets data type and other Redis 8 features are available under true open source terms Redis creator Antirez played a key role in advocating for the licence change, expressing his commitment to writing open source software and ensuring his new Vector Sets implementation would be truly open. His influence helped build internal momentum for the switch across the Redis company hierarchy. Rails applications heavily rely on Redis for caching, background job processing with Sidekiq, and session management. The return to open source licensing removes the uncertainty that enterprise Rails teams faced when evaluating Redis for new projects. Redis 8 also brings performance improvements and new features alongside the licensing change, reinforcing Redis's position as the go-to data structure server for modern web applications. What role does Redis play in your Rails application architecture? We're connecting with Rails developers who understand distributed caching and performance optimisation strategies. #Redis #OpenSource #RubyOnRails #CachingStrategy #TechRecruitment

5

🚀 Introducing ter-k8s-api: A Practical Project Integrating FastAPI, Kubernetes, and Infrastructure as Code 🚀 If you are looking to enhance your expertise in building, containerizing, and orchestrating modern applications, this project provides a comprehensive hands-on experience. 🔍 Project Highlights: A streamlined FastAPI service for customer management featuring complete CRUD operations. Interactive API documentation generated automatically with Swagger UI, facilitating endpoint testing and exploration. A simple web interface built with Jinja2 templates and static files for improved user experience. Dockerfile for containerizing the application to ensure consistent deployment across environments. OpenTofu modules defining Kubernetes infrastructure, enabling automated deployment of the API to a local cluster. Integrated monitoring using Prometheus and visualization dashboards with Grafana for real-time application health insights. Continuous Delivery automation through ArgoCD, optimizing deployment workflows. PowerShell scripts automating common development and deployment tasks to increase efficiency. 💡 Why Engage with ter-k8s-api? This project combines essential development and DevOps concepts in a single local setup, ideal for understanding end-to-end modern application workflows. Whether your goal is to advance your skills, build a professional portfolio, or explore industry-standard technologies, ter-k8s-api offers a valuable resource to differentiate yourself. 👉 Explore the repository, experiment, learn, and contribute: https://lnkd.in/dtEXig-9 Together, let’s shape the future of technology! ⚡

3

1 Comment

Your monolithic application just crashed during peak trading hours. Again. Whilst synchronous architectures might seem simpler, they're creating cascading failures that cost Australian enterprises millions in downtime. The solution isn't just breaking systems apart - it's fundamentally rethinking how services communicate. Modern microservices leverage asynchronous communication patterns through message brokers like Apache Kafka, enabling services to operate independently even when others fail. Instead of blocking operations that tie up resources, async patterns allow systems to handle thousands of concurrent users with the same hardware. We've seen this transformation firsthand with enterprise clients. When properly implemented with event-driven architectures, services can process messages at their own pace, eliminating the bottlenecks that plague traditional monolithic systems. The key isn't just adopting microservices - it's implementing the right communication patterns that ensure resilience at scale. Ready to transform your legacy systems into scalable, fault-tolerant architectures? Let's discuss how microservices can deliver speed to value for your digital transformation journey.

2

30 years in tech. 10 AWS certs at peak. I know what separates a useful cert from a vendor checkbox. Anthropic just released the exam guide for their first certification: Claude Certified Architect, Foundations. It covers Claude Code, the Agent SDK, the Claude API, and Model Context Protocol. I read all 40 pages. Then I held every domain up against a system I've been building for two weeks. It completely reframed how I see my own work. Three out of five domains describe exactly what I built without knowing the exam existed. The exam covers agentic architecture. I built a breaking news pipeline where Stage 1 scores RSS headlines, escalates to Stage 2 for research and content generation, and handles failures with structured retries. The exam calls this "coordinator-subagent orchestration." I called it "the pipeline that kept breaking under launchd at 5 AM." The exam covers Claude Code configuration. I have a CLAUDE.md hierarchy, path-scoped rules, six custom skills, and a daily automation that runs Claude Code non-interactively via launchd. The exam frames this as "CI/CD integration." I framed it as "why does TMPDIR break everything in a headless environment." The exam covers MCP tool design. I integrate two MCP servers for social publishing and video generation. I learned the hard way that vague tool descriptions cause misrouting, that error responses need structure, and that giving an agent too many tools degrades its judgment. The exam formalizes these as design principles. I learned them from 2 AM failures. But here's the part that matters. Two domains reframed what I thought I was doing well. Structured output with validation-retry loops. I use structured output for scheduling, but I don't systematically validate and retry when extraction fails. I'm absorbing errors I should be catching. Context management. I do some of this with morning/evening snapshot diffs and a memory system. But the exam describes patterns like "case facts" blocks and position-aware input ordering that I'm not doing deliberately. My context fills up and I start a new session. That's not a strategy. That's giving up. 30 years of building systems gives you instincts. But instinct and intention are not the same thing. The three domains I matched? I was doing those things from pattern recognition. Reps. Muscle memory. The two I missed? Those were the areas where I was getting by on instinct when I should have been operating with discipline. A good framework doesn't teach you new tricks. It reframes the ones you already have. It turns "things I do" into "things I do deliberately versus things I'm just getting away with." That's the difference between experience and growth. Experience is the reps. Growth is when something makes you see your own reps differently. What's a framework, certification, or conversation that reframed how you see work you were already doing? #ClaudeCode #AI #CloudArchitecture #Certification #AgenticAI #Anthropic

4

🚀 Scaling Terraform? You Need Terragrunt. As Terraform projects grow, code duplication, state management, and environment sprawl become real challenges. That’s where Terragrunt comes in. In this video, I explain: ✅ How Terragrunt enforces the DRY principle ✅ Centralized provider & backend configuration ✅ Separate state files to reduce blast radius ✅ Managing dependencies (VPC → EC2) cleanly ✅ Running infrastructure changes across environments at scale If you’re working on production-grade cloud infrastructure, this is a must-watch. 🎥 Watch the full video here: 👉 https://lnkd.in/gzpEVYyx #Terraform #Terragrunt #DevOps #InfrastructureAsCode #AWS #CloudEngineering

9

1 Comment

“𝗗𝗮𝘁𝗮 𝗿𝗲𝘀𝗶𝗱𝗲𝗻𝗰𝘆, 𝗹𝗼𝘄 𝗹𝗮𝘁𝗲𝗻𝗰𝘆, 𝗮𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 𝘀𝗼𝘃𝗲𝗿𝗲𝗶𝗴𝗻𝘁𝘆 𝗻𝗼𝘄 𝗹𝗼𝗰𝗮𝗹 𝗳𝗼𝗿 𝗞𝗶𝘄𝗶𝘀.” 🇳🇿 — 𝗮𝗻𝗱 𝗶𝘁 𝗰𝗵𝗮𝗻𝗴𝗲𝘀 𝗲𝘃𝗲𝗿𝘆𝘁𝗵𝗶𝗻𝗴.” 𝗔𝗪𝗦 𝗔𝘀𝗶𝗮 𝗣𝗮𝗰𝗶𝗳𝗶𝗰 (𝗡𝗲𝘄 𝗭𝗲𝗮𝗹𝗮𝗻𝗱) 𝗥𝗲𝗴𝗶𝗼𝗻 with three Availability Zones and API name 𝗮𝗽-𝘀𝗼𝘂𝘁𝗵𝗲𝗮𝘀𝘁-𝟲 is now GA (general availability) 𝘞𝘩𝘢𝘵 𝘥𝘰𝘦𝘴 𝘵𝘩𝘦 𝘎𝘈 𝘭𝘢𝘶𝘯𝘤𝘩 𝘰𝘧 𝘈𝘞𝘚 𝘈𝘴𝘪𝘢 𝘗𝘢𝘤𝘪𝘧𝘪𝘤 (𝘕𝘦𝘸 𝘡𝘦𝘢𝘭𝘢𝘯𝘥) 𝘙𝘦𝘨𝘪𝘰𝘯 𝘮𝘦𝘢𝘯?  • 3 Availability Zones, API name ap-southeast-6 — now you can run workloads and store data in‑country, reducing latency for NZ users.  • AWS invested NZD 7.5 billion; the region is expected to contribute NZD 10.8 billion to GDP and create ~1,000 jobs annually.  • Integrates compliance and security certifications (PCI, HIPAA, GDPR, etc.) to support regulated workloads.  • Opens doors for AI & ML innovation locally using AWS’s generative AI stack (Bedrock, Q) — without leaving NZ. #AWS #cloud #newzealand #Kiwis #cloudengineering #devops #cloudsecurity #compliance #gdpr #pcidss #cloud #artificialintelligence

12

“We’re empowering developers to move fast and own their code in production.” Translation: We gave every dev kubectl and now we’re praying to the observability gods they don’t nuke prod. SRE and Platform work means something different everywhere you go but gets buried under the same buzzword compost. “Shift left.” “You build it, you run it.” “Platform as a product.” “Developer self-service.” “Blameless culture.” It's getting harder to tell jobs apart. What any of them actually do. Or how they’re any different. Meanwhile, candidates want the basics: Real autonomy. Meaningful project work. Backing from leadership when production hits the fan. Everything else? Just noise.

11

5 Comments

It's that time… What’s been happening in the wonderful world of DevOps, Cloud & SRE? 📃 The question everyone asks is "How is the market?" Well here is everything you need to know across the DevOps space and broader Technology sector for Q1 of FY2026. → Overview of Q1 and Outlook for Q2 → Rates & Salaries → Market trends & insights for Candidates & Clients Want to view the full report? Click here >https://lnkd.in/gJFGc6Ft

20

GitLab has announced the general availability of GitLab Duo with Amazon Q for its Ultimate self-managed customers on AWS. Here are the key points: Integration: Embeds Amazon Q's software development agents into GitLab's DevSecOps platform to streamline development cycles. Automation: Automates complex tasks like feature development, legacy codebase modernization, security vulnerability remediation, and quality assurance. Autonomous Feature Development: Transforms new feature ideas into merge-ready code. Security Enhancements: Reduces vulnerability remediation time with explanations, root cause analysis, and one-click remediation. Quality Assurance: Generates automatic code reviews with inline feedback and improvement suggestions. This integration aims to enhance development workflows, allowing teams to focus on innovation while ensuring security. What are your thoughts? #article #devops #gitlab

4

3 Comments

Most .NET systems do not need RabbitMQ on day one. Many teams in Australia are paying for cloud complexity and message brokers before they have a real scale problem. We just published a new guide on how to make a monolith feel modern using .NET Channels, without adding extra servers or monthly fees. Read the full decision guide: 👉 https://lnkd.in/gskBQPa2

1

Voyage AI by MongoDB just launched rerank-2.5 & rerank-2.5-lite, improving retrieval accuracy and adding instruction-following capabilities for the first time. Learn more in the blog! https://lnkd.in/gcK2GQ2f

5

🔥 Timescale Changelog – June 13, 2025 ⚙️ Improved Terraform Support (v2.3.0) - Create & attach observability exporters - Secure services with AWS Transit Gateway - Configure CIDRs for VPC + Transit Gateway connections 🐘 TimescaleDB v2.20.3 Patch - Fixes for SkipScan costing, chunk skipping restore issues, and dropped conditions in queries 👉 More: https://lnkd.in/gqee-6AU #PostgreSQL #Timescale #Terraform #CloudInfra #Changelog

7