Featured Issues

5 Knobs That Save You from Nightly HeadachesCloudPro #106Hunt Threats, Recover Fast: Next-Gen Cyber Resilience for Google CloudJoin Hunt Threats, Recover Fast: Next-Gen Cyber Resilience for Google Cloud, a virtual event about going beyond traditional backup.You'll see:- Real-time ransomware detection and automated threat hunting for Google Cloud- Turbo Threat Hunting in action to trace attack paths and accelerate incident response- Streamlined recovery workflows that simplify protecting your Google Cloud workloadsSave Your SpotToday’s CloudPro is about the five batch-scoring knobs most engineers overlook. If you’ve ever watched a job stretch from minutes to hours and wondered why, this is where you start.This article is adapted fromChapter 5 ofHands-On MLOps on Azure. In that chapter, author Banibrata De dives into the gritty details of model deployment: batch scoring, real-time services, and the YAML settings that make the difference between smooth pipelines and midnight firefights.(The book goes much further, covering CI/CD pipelines, monitoring, governance, and even LLMOps across Azure, AWS, and GCP. CloudPro readers can grab it at the end of this piece with an exclusive discount.)Cheers,Shreyans SinghEditor-in-ChiefGET THE BOOKSAVE THIS ARTICLE AND READ LATERTuning Batch Jobs on Azure ML: 5 Knobs Every Engineer Should KnowSHARE THIS ARTICLEIt’s late. The batch run you trusted starts crawling. Dashboards spike, Slack pings light up, and you’re debating whether to kill the job or ride it out. You don’t need a re-platform. You need to tune the controls Azure ML already gives you.Below are thefive knobsthat tame throughput, flakiness, and costs. They live in your batch deployment YAML, and they work.1) mini_batch_size: The throttle for your workloadBatch jobs in Azure ML process data in chunks.mini_batch_sizecontrols how big each chunk is. Push it too high, and you’ll hit memory or I/O bottlenecks; keep it too low, and you’ll waste time on overhead. Think of it like loading a truck: too few boxes and you’re underutilizing space, too many and you risk breaking the axle. Getting this balance right often cuts hours off long-running jobs.2)max_concurrency_per_instance: How many cooks in the kitchenEach compute node can process tasks in parallel, but how many at once depends on its resources.max_concurrency_per_instanceis that dial. If you pack too much onto a single node, CPU and memory will thrash, and everything slows down. Start low, then gradually raise it while watching system metrics. The goal is steady throughput, not chaos.SAVE THIS ARTICLE AND READ LATER3)instance_count: Scale out, don’t just scale upEven with tuned concurrency, sometimes one node just isn’t enough. That’s whereinstance_countcomes in. It decides how many nodes you’ll spread the workload across. It’s the knob you turn when you need predictable completion times. For example, making sure the nightly run finishes before business hours. More nodes mean more cost, but also fewer late-night surprises.4)retry_settings: Resilience for the real worldIn batch jobs, things fail: a network hiccup, a corrupted file, a transient storage timeout. Without retries, the whole job can collapse because of one small blip.retry_settingslets you say, “Try again a few times before giving up.” Set sensible timeouts and retries per mini-batch so small failures don’t derail the entire pipeline.5)error_threshold: Fail smart, not earlyWhat happens if some data records are bad? By default, too many errors can abort the run. Witherror_threshold, you control how many you’ll tolerate. Setting it to-1tells Azure ML to ignore errors completely. For messy real-world datasets, this is a lifesaver: you can still ship 99% of results and deal with the outliers later, instead of losing the entire batch.Extra sanity checksRespect the contract:Batch jobs are built forfiles/blobs in, files/blobs out. Don’t try to wrap them around per-record HTTP calls.Keep scripts separate:Usebatch_score.pyfor batch andonline_score.pyfor real-time. Different handlers, different expectations.Watch metrics that matter:Throughput, per-batch latency, error rate, and CPU/GPU/memory use. Wire alerts so you’re not caught off-guard at 2 a.m.TakeawayBatch scoring doesn’t have to be a black box. Azure ML gives you the levers. You just have to use them. Tune these five settings, keep batch and online flows separate, and you’ll get faster, more reliable runs without babysitting every night.This walkthrough is pulled straight from Chapter 5 ofHands-On MLOps on Azure. The full book expands on everything here: deployments, monitoring, alerting, governance, pipelines, and operationalizing large language models responsibly.For the next48 hours, CloudPro readers get35% off the ebookand20% off print. If Azure ML is part of your stack, or about to be, this is the reference worth keeping open on your desk.GET THE BOOK📢 If your company is interested in reaching an audience of developers and, technical professionals, and decision makers, you may want toadvertise with us.If you have any comments or feedback, just reply back to this email.Thanks for reading and have a great day! *{box-sizing:border-box}body{margin:0;padding:0}a[x-apple-data-detectors]{color:inherit!important;text-decoration:inherit!important}#MessageViewBody a{color:inherit;text-decoration:none}p{line-height:inherit}.desktop_hide,.desktop_hide table{mso-hide:all;display:none;max-height:0;overflow:hidden}.image_block img+div{display:none}sub,sup{font-size:75%;line-height:0}#converted-body .list_block ol,#converted-body .list_block ul,.body [class~=x_list_block] ol,.body [class~=x_list_block] ul,u+.body .list_block ol,u+.body .list_block ul{padding-left:20px} @media (max-width: 100%;display:block}.mobile_hide{min-height:0;max-height:0;max-width: 100%;overflow:hidden;font-size:0}.desktop_hide,.desktop_hide table{display:table!important;max-height:none!important}}

Crafting the Web: Tips, Tools, and Trends for Developers Advertise with Us|Sign Up to the Newsletter @media only screen and (max-width: 100%;} #pad-desktop {display: none !important;} } @media only screen and (max-width: 100%;} #pad-desktop {display: none !important;} } WebDevPro #107: Postgres 18 RC1, zoneless Angular, Fresh + Vite, and V8 speed gains 🌍🔍 Crafting the Web: Tips, Tools, and Trends for Developers Hi , Welcome to WebDevPro #107! The JavaScript world has been buzzing again. Did you catch the debate about who really owns the “JavaScript” name? It’s one of those conversations that reminds you just how much of the ecosystem rests on decisions made decades ago. At the same time, developers have been trading stories about browser behavior. Ever notice how your timers sometimes slow down for no apparent reason? You weren’t imagining it. Browsers throttle JavaScript timers in the background, and it’s sparking plenty of conversation about the trade-offs between performance and predictability. Of course, that's not all this week! On the practical side, React Server Components are back in the spotlight, this time outside the comfort zone of frameworks like Next.js. Would you be tempted to try them barebones, or does the structure of a framework feel essential? Angular’s summer update also turned heads with zoneless change detection and some early AI-powered tooling that hints at where the framework is heading next. And over at React.dev, the docs keep evolving quietly but steadily, making it easier to navigate and learn from even if you only notice the improvements when you need them most. PostgreSQL 18 RC1 dropped as well, putting September’s GA release on the radar for database fans. Scroll down to the Developer Tip section, where we discuss a big performance win in V8 13.8 where JSON.stringify runs more than twice as fast, no code changes required. Plenty to dig into, so let’s get started. Advertise with us Interested in reaching our audience? Reply to this email or write to kinnaric@packt.com. Learn more about our sponsorship opportunities here. Take the Survey Now Latest news: what's new in web development? 🧑‍💻 🐘 PostgreSQL 18 RC1 Is Now Public: The first release candidate for PostgreSQL 18 is live, with general availability set for September 25, 2025. The update includes fixes such as vacuum refinements and better full-text index guidance, and it requires a major-version upgrade plan using pg_upgrade. Careful migration planning will help avoid index issues. AWS has also added support for PostgreSQL 18 RC1 in its RDS preview, giving teams a managed environment to experiment before the full release. 🔧 React.dev Docs Earn Useful Upgrades: The React documentation site keeps evolving through steady community contributions. Recent changes include a restructure of the Compiler section, fixes for runtime errors in interactive challenges, improved sidebar toggles, and clearer guidance for React Dev Tools, all aimed at making learning smoother and reducing confusion. 🌞 Angular Summer Update: Zoneless & AI Tools Arrive: Angular 20.1 and 20.2 introduce production-ready zoneless change detection, an experimental MCP server for LLM-assisted code generation, built-in DOM animation APIs, and DevTools upgrades including signals and router visualization. The releases also bring improvements to template authoring and set the stage for an upcoming developer-focused event, marking a clear step toward productivity and AI-powered workflows. 💼 Digital Silk Forecasts High Demand for Design Innovators: Digital Silk reports rising client demand for advanced design and digital branding services, with companies increasingly investing in distinctive digital experiences to stand out in crowded markets. For product and creative leaders, the signal is clear: UI/UX and brand presence are no longer secondary concerns but core levers for visibility, engagement, and long-term differentiation. 🤖 Fresh meets Vite: The Fresh framework from Deno is rolling out Vite integration in its 2.0 beta, bringing boot times down from 86 ms to just 8 ms. Developers get hot module replacement that preserves UI state, React aliasing by default, and the return of the <Head> component, all without the overhead of build tooling Bug of the week 🐞 A tiny flaw in Node.js crypto just earned a high-severity CVE and could crash apps from a single async call. Every active release line was hit. The patch is out, but the real story is how this slipped through. 👉 Read the official Node.js security release Hunt Threats, Recover Fast: Next-Gen Cyber Resilience for Google Cloud Join Hunt Threats, Recover Fast: Next-Gen Cyber Resilience for Google Cloud, a virtual event about going beyond traditional backup. You'll see: Real-time ransomware detection and automated threat hunting for Google Cloud Turbo Threat Hunting in action to trace attack paths and accelerate incident response Streamlined recovery workflows that simplify protecting your Google Cloud workloads Save Your Spot Expert corner: what's the web community talking about?🎙 ⚛️ React Server Components Without a Framework: Krasimir Tsonev experiments with running React Server Components directly in vanilla Node, skipping framework scaffolding. The post illustrates both the power and the complexity of going barebones, raising the question of how much abstraction developers actually want to peel back. ⏱️ Why Browsers Throttle JavaScript Timers: Nolan Lawson explains how and why browsers cut back the frequency of JavaScript timers in background tabs and idle contexts. It’s a clear deep dive into the performance trade-offs and resource management behind quirks many developers have noticed but not understood. 📈 Big-O Explained Visually: Sam Who delivers a visual, interactive guide to Big-O notation that turns abstract complexity analysis into intuitive graphics. The walkthrough is approachable without losing depth, making it easier to internalize how algorithms scale. 📝 Who Owns “JavaScript”?: Dr. Axel Rauschmayer unpacks the legal and historical twists of the “JavaScript” trademark, controlled by Oracle. The piece explores what this means for the language’s naming, branding, and the broader ecosystem. 🔐 An Illustrated Guide to OAuth: Ducktyped.org offers a visual explainer of OAuth’s moving parts, showing how tokens, clients, and authorization servers interact. It’s a resource that makes sense of terminology that often feels abstract or opaque. 🚀 Building a React Framework Faster than Next.js:Ryan Skinner describes building a custom full-stack React framework he claims runs four times faster and handles four times the throughput of Next.js. Benchmarks aside, it’s a compelling exploration of what’s possible when you challenge assumptions and optimize aggressively. Want to be featured in WebDevPro? Share your tips or takes, we’re all ears! This week's book drop 📚 📘 Microservices with Spring Boot and Spring Cloud, Fourth edition by Magnus Larsson Magnus Larsson’s updated August 2025 edition shows how to build and deploy production-ready microservices with Spring Boot 3.5, Spring Cloud 2025, Java 24, Kubernetes, and Istio. Covering resilience with Resilience4j, service discovery, API security, observability, and native builds with GraalVM, it’s a hands-on guide to creating scalable, cloud-native systems. Order your copy now! Developer tip 💡 JSON.stringify just got a major boost in V8 13.8, running more than twice as fast for common cases like API payloads and cached objects (v8.dev). The speedup comes from a streamlined fast path for plain objects and arrays, iterative instead of recursive serialization, SIMD-powered string escaping, and a switch to the faster Dragonbox algorithm for numbers. Takeaway: If you’re on V8 13.8+ (Chrome, Node, Deno), simple JSON.stringify calls automatically benefit, no code changes required. Got a minute? Tell us what clicked (or didn't) 🎬 And that’s a wrap. Got a request, a bug to bust, or a genius trick to share? Send it our way. Back in your inbox next week. Cheers! Kinnari Chohan, Editor-in-chief SUBSCRIBE FOR MORE AND SHARE IT WITH A FRIEND! Staying sharp in .NET means more than just skimming release notes. You need practical tips, proven patterns, and scalable solutions from experts who’ve been in the trenches. That’s exactly what you’ll get with .NETPro, Packt’s new newsletter, along with a free bestselling eBook as a welcome bonus when you sign up. Join .NETPro — It’s Free *{box-sizing:border-box}body{margin:0;padding:0}a[x-apple-data-detectors]{color:inherit!important;text-decoration:inherit!important}#MessageViewBody a{color:inherit;text-decoration:none}p{line-height:inherit}.desktop_hide,.desktop_hide table{mso-hide:all;display:none;max-height:0;overflow:hidden}.image_block img+div{display:none}sub,sup{font-size:75%;line-height:0}#converted-body .list_block ol,#converted-body .list_block ul,.body [class~=x_list_block] ol,.body [class~=x_list_block] ul,u+.body .list_block ol,u+.body .list_block ul{padding-left:20px} @media (max-width: 100%;display:block}.mobile_hide{min-height:0;max-height:0;max-width: 100%;overflow:hidden;font-size:0}.desktop_hide,.desktop_hide table{display:table!important;max-height:none!important}} @media only screen and (max-width: 100%;} #pad-desktop {display: none !important;} } @media only screen and (max-width: 100%;} #pad-desktop {display: none !important;} }