🇯🇵🇧🇷🇺🇸Edson Yanaga

Amazon Web Services (AWS) released their most powerful and energy efficient CPU design in #AWS Graviton4. This new generation brings enormous power for customers including: - 50% more cores & 75% more memory bandwidth compare to previous generation. you can now provision these type of AWS EC2 instances as R8g in your AWS console with VMs with up to 192 vCPU core and 1.5TB memory, 50Gbps network bandwidth and 40Gbps EBS bandwidth, making it a great choice for scaled up applications. this amazing EC2 performance also consumes 60% less energy which is a great sustainability and environmental achievement too. Well done Amazon Web Services (AWS) . #AWSCloud #Cloud #sustainability #AWS #cloudcomputing

10

In this Mob Mentality Show episode, Chris Lucian and I dive into the complexities of modern CI/CD (Continuous Integration / Continuous Delivery) pipeline code and IaC (Infrastructure as Code), exploring why these critical components of software delivery often exhibit the same problematic attributes as classic Legacy Code. https://lnkd.in/ghJ2NJpy https://lnkd.in/gBgfDq3c Drawing inspiration from Michael Feathers' seminal book *Working Effectively with Legacy Code*, we analyze the paradox of cutting-edge DevOps practices turning into technical debt almost as soon as they're written. ### Episode Highlights: - **CI/CD Pipeline Code and Legacy Code Parallels**: Why does so much CI/CD and IaC code resemble legacy code? Despite being crucial for continuous delivery and automation, CI/CD pipelines can become fragile, difficult to change, and filled with technical debt if not handled carefully. Me and Chris discuss why this phenomenon is so common and what makes the codebases for CI/CD pipelines especially prone to these issues.    - **“Edit and Pray” vs. TDD Confidence**: Do your CI/CD changes feel like a roll of the dice? Chris and I compare how the lack of test-driven development (TDD) practices in CI/CD code leads to “edit and pray” scenarios. We discuss the confidence that TDD brings to traditional application development and how applying similar principles could reduce fragility in CI/CD code. - **The Pitfalls of YAML in IaC**: Is the problem inherent to YAML? We explore whether the complexity of YAML syntax and configurations is the root cause of the brittleness often found in IaC. We provide real-world examples of IaC configurations that suffer from high cyclomatic complexity—making them feel more like full-blown applications rather than simple configuration files. - **Fear of Change in CI/CD and IaC**: Why are developers often afraid to modify CI/CD pipeline code or IaC? Chris and I highlight the psychological aspects of fragile infrastructure—where fear of unintended consequences and lack of fast feedback loops result in slower iterations and more bugs. We explore why these codebases are often re-written from scratch instead of extended and safely enhanced. - **Reducing Fragility through Experiments**: The episode features a recent experiment where CI/CD pipeline code was developed in Python using TDD and separation of concerns. This case study reveals the pros and cons of less YAML and a shift towards more code-based "configurations." Could this approach be a solution to reducing brittleness in IaC and pipelines? - **A World Without Brittle Pipelines?**: Imagine a world without fragile pipelines and brittle configuration files. Chris and I discuss strategies to move towards more resilient infrastructure and how teams can focus on improving feedback loops, reducing complexity, and enabling safer, faster CI/CD iterations.

11

6 Comments

Here's a practical example of how Formal Methods can make code faster: AWS's new proven-correct authorization engine is 65% faster (even at p99.9) than the previous version. https://lnkd.in/gVCdurKh Sean says in the talk "we wouldn't have attempted a lot of optimizations we did without this backing of proof". Formal methods allow us to optimize systems more boldly, by removing the risk that optimizations will affect correctness. They also allow our teams to move faster, with lower risk, by building confidence in correctness early on in the software development process.

435

4 Comments

🚀 Exciting news in the Rust and AWS communities! 🚀 On June 8th, Werner Vogels announced **distill CLI**, an efficient, Rust-powered tool for media summarization. 📜🔧 Check out his blog for more details: [Introducing Distill CLI](https://lnkd.in/dfUT4cmf) Notably, companies like Discord and Figma have achieved remarkable performance improvements by adopting Rust. Discord moved their Read States service from Go to Rust, resulting in a 10x speed increase and nearly 100x reduction in worst tail latencies. Similarly, Figma rewrote performance-sensitive parts of their multiplayer service in Rust, seeing a 6x reduction in peak average CPU usage per machine. 🌟💪 AWS is also embracing Rust with the general availability of Cargo support in CodeArtifact, enabling the storage of Rust libraries (crates) in CodeArtifact. 📦✨ More info: [AWS CodeArtifact and Cargo Support](https://lnkd.in/dYY_fgtU) As more customers leverage Rust for their critical workloads, AWS is providing robust building blocks. AWS Lambda, for instance, can now process HTTP events more efficiently with Rust. 🚀⚡️ Learn more here: [Rust HTTP Events in AWS Lambda](https://lnkd.in/diubf8bM) #RustLang #AWS #Serverless #Performance #CloudComputing #Innovation #TechNews #CodeArtifact #DistillCLI

11

I'm sorry about this, but GitLab might not matter as much as you think. 🤔 I keep having those kinds of discussions with (French) engineers, so I decided to write about it: no, GitLab is not as prominent as you think it is. We see it as so small that over the last five years, we have made no effort to support it at Mergify, preferring to continue developing new products without GitLab support as a first priority. Read below if you want to understand more. ⬇️

77

87 Comments

Sometimes small changes are a big deal. S3's per-account bucket limit has meant that buckets have been more of a human provisioning thing, starkly different from objects, which tend to be interacted with primarily from code. For years, customers have been asking us to increase this limit -- and in the storage innovation talk at re:Invent this year, i'd tell a bit of a story about why it was a more complicated bit of work than you might expect. With this limit increase, buckets have become a much more programmatic construct. We hear customers talking about using buckets, with these limit increases, as a way of managing data sharing with their own customers and using them to more effectively isolate data for specific jobs and teams. If larger numbers of buckets opens up a new pattern for you, I'd love to hear more about it. These launches, like object consistency, S3 conditionals, and big bucket limit increases have a tendency to fly a little below radar. But they are the ones that I actually hear the most excitement back from developers about, because they really broaden S3 as a programmatic interface to your data, and a building block for really incredible systems. I'm so impressed with the hard and careful work on the team that went in to getting this one out. https://lnkd.in/gA2cWATM

189

8 Comments

Agents for Amazon Bedrock support memory retention and code interpretation - now in preview. Dynamically generate code and run code snippets and enable your agents to learn and adapt over time. #AWSome #GenAI #AmazonBedrock https://lnkd.in/gAj2N9q4

7

#throwbackthursdays What are things conducive to personal fulfillment at work? Specifically with mob programming, what would it look like to optimize for personal fulfillment? For example, how do you find joy even in the midst of disagreement? Join us as we discuss with Kelly Rankin "Optimizing for Personal Fulfillment in Mob Programming." Starting with autonomy and fulfillment, we share what that looks like in an ensemble including things that make it harder and things that make it easier. Then we jump into kick starting and maintaining continuous learning. Lastly, we focus on keeping a holistic perspective in the work and the impact of full-stack development, which ultimately goes full circle and ties back into continuous learning and personal fulfillment. https://lnkd.in/gRfzG8KF #MobProgramming

3

This is a notable increase in the number of S3 buckets that a single account can have, and I could see this being a welcome improvement for folks that use a lot of S3 buckets. It should be mentioned that with this change comes the possibility of a new fee, $0.02 per additional general purpose bucket (when you have more than 2,000 S3 buckets in your account). So you still probably want to be smart about the number of S3 buckets you create. #aws #s3 #cloudstorage #awspricing https://lnkd.in/eQFNd48c

3

Don't Cry Mr. Donkersgoed = My posts come with quirky headlines, here is a recent example: You Want To Be A Cloud Engineer? Leave Cloud ASAP. lnkd.in/g9gbZPQF This post headline is also strange: Don't Cry Mr. Donkersgoed What is going on?? I claim that this post (Don't Cry Mr. Donkersgoed) and the earlier post (You Want To Be A Cloud Engineer? Leave Cloud ASAP.) are the same even though post headlines are widely different. Please read on to find out. = Luc van Donkersgoed published a heartfelt note: Dear Amazon Web Services (AWS), please let me be a cloud engineer again lnkd.in/gFKVPcZH I published my earlier post as a reaction to this cry for restoring sanity in Amazon Web Services (AWS) Product Management. In this post I am encouraging Mr. Donkersgoed to not cry but take some alternative positive steps. What are these alternative positive steps? Here: 1) Build open source stacks 2) Use open source stacks I have a very good recent example: Bengaluru-based Moving Tech has raised $11 million in a pre-Series A funding round co-led by Blume Ventures and Antler, the startup said. Google, which has pledged to invest $10 billion in India, participated in the round. Namma Yatri works atop the Open Network For Digital Commerce (ONDC), an interoperable scheme backed by the Indian government that is aiming to democratize e-commerce in the country. Namma Yatri’s app connects customers with auto-rickshaw and cab drivers without charging either party for rides. Instead, the startup collects a small monthly fee from its driver partners. Uber and Ola, in comparison, charge their driver partners as much as 25%-30% of the ride cost, and have refused to join the ONDC network for their core mobility offerings. Moving Tech’s co-founders, Magizhan Selvan and Shan M S, told TechCrunch that they identified an opportunity after they found out how frustrated drivers were with their treatment in the existing system. “There was a lack of differentiated approach,” Shan said, reflecting on the decade-long duopoly that Uber and Ola have enjoyed unchallenged in India. Moving Tech doesn’t offer customer discounts or driver incentives, and it is banking on providing a service that people find genuinely useful, he added. See what I mean by: 1) Build open source stacks 2) Use open source stacks = India Stack refers to the project of creating a unified software platform to bring India's population into the digital age. Its website describes its mission as follows: "India Stack is a set of open APIs that allows governments, businesses, startups and developers to utilize a unique digital Infrastructure to solve India’s hard problems towards presence-less, paperless, and cashless service delivery" India Stack is the largest open API in the world. Since its deployment, India has been organizing hackathons to develop applications for the APIs. Don't Cry Mr. Donkersgoed - Think Different.

12

The article "Continuous Reinvention: A Brief History of Block Storage at AWS" chronicles the evolution of Amazon's Elastic Block Store (EBS) from its 2008 launch. Initially hampered by HDD limitations, EBS transformed with SSDs in 2011, boosting performance to 1,000 IOPS. AWS's strategy of incremental innovation tackled challenges like performance isolation and "noisy neighbors," using advanced telemetry for optimization. Creative solutions, like retrofitting SSDs, exemplify their innovation under constraints. With cutting-edge tech like the Nitro system and SRD protocol, EBS has become a powerhouse of AWS infrastructure, showcasing relentless reinvention and adaptation to customer needs and tech trends.

1

To solve #Kubernetes complexity, digital bank PicPay adopted a Kubernetes platform engineering strategy and unified observability. Read about their challenges and how they overcame them in this conversation with their VP of Engineering, Martin Spier.

2

Folks I've spoken to about Amazon have likely heard me talk about the importance of the PR/FAQ process, a.k.a. "the working backwards process". This blog posts gives a very nice example of a PR/FAQ. https://lnkd.in/edTeuVRQ. Note that the blog doesn't capture the presumably 100s of reviews/discussions/rewrites that this doc represents, which is a part of the real value. When the process is done it all looks so simple, but getting a large organization to make a decision to something simple and do it in a BIG way is the challenge the fun of it all.

40

1 Comment

Yesterday, I celebrated 8 years at Amazon Web Services (AWS). Rather than tell you all about my 2920 day ones, I'm here to let you know that Martyn Storey and I have created the second video in our series on Observability. This video is all about metrics, particularly the importance of monitoring for business outcomes. #awscloud #observability

112

8 Comments

ICYMI, Google Cloud Platform and Technical Infrastructure Director, Jennifer Petoff, gave the opening keynote at DevOpsDays Zurich this year. You can check out the video here if you want to learn more about the importance of education in driving an SRE or DevOps culture.

3

GenAI in the Enterprise, and why MongoDB is such an integral part of the conversation today! Stack Overflow's newest podcast features Miku Jha, Director of AI/ML and Gen AI at Google Cloud, alongside Shane McAllister and Stanimira Vlaeva, Developer Advocates at MongoDB to explore the world of generative AI in enterprise organizations. Don't miss out on valuable insights into scaling AI models and overcoming deployment challenges! Tune in today! 👇 https://lnkd.in/eZyhu99t

10

1 Comment

Agile software development can be done at scale with the use of #technology like self-service APIs, infrastructure provisioning, real-time collaboration software, and distributed versioning systems. In this piece, Ben Linders shares some insights from Fabrice Bernhard on how his company uses #technology with lean thinking for agile #SoftwareDevelopment at scale. Value for the customer should absolutely become the North Star of the whole organization, and this can happen through value models, obeyas, and value streams scaling customer #collaboration. Trying to scale an agile organization? Lean thinking could help.

4