Curated articles, resources, tips and trends from the DevOps World.
Google laid out an ambitious roadmap for its Dart framework, Flutter — including plans to support WebAssembly (Wasm) — at the Flutter Forward conference in Nairobi, Kenya. The internet giant is looking to its developer community to help build out the plan. It also released Dart 3.
Platform engineering is the new thing. Like all new things, there are different takes on what it really means and does, and more importantly, what it’s used for. The same goes for internal developer portals, which are the main developer-facing tools used by platform engineering folks.
Recently, a suggestion was made to adopt Tim Peters’ “The Zen of Python” as an overall guiding principle for designing good automation content. That gave me pause because it didn’t seem like the right thing to me.
By 2017, Uber’s codebase was incredibly fragmented to the point where problems would bleed into library versions, build tools, dependency management and collaboration, and code sharing was deeply affected.
If you’re an organization building a platform engineering team, that team’s new customers are application developers. This may seem obvious, but it’s a huge shift from the usual way infrastructure builders think about their job.
And down went all Microsoft 365 services around the world. One popular argument against putting your business trust in the cloud is that if your hyper-cloud provider goes down, so does your business. Well, on the early U.S. East coast morning, it happened.
The IOTA Foundation, the organization behind the IOTA open source distributed ledger technology built for the Internet of Things, envisions a future where every single trade item in the global supply chain is tracked and its provenance sourced using distributed ledgers.
By now, almost everyone agreed platform engineering is probably a good idea, in which an organizations builds an internal development platform to empower coders and speed application releases.
Serverless functions, which account for around half of the workloads today at cloud-first companies, have become a popular means of deploying applications largely because serverless minimizes the number of complexities that teams need to think about.
Like every product at AWS, these were scaled with a product-led growth (PLG) market motion: no gated features, no subscription tiers to choose from. Instead, a Usage-Based Pricing (UBP) model is used to charge based on consumption, directly correlated to the value being delivered to the user.
Have valuable insights to share with the DevOps community? Submit your article for publication.
Get the latest DevOps news, tools, and insights delivered to your inbox.
Made with pure grit © 2025 Jetpack Labs Inc. All rights reserved. www.jetpacklabs.com