Joe Duffy - Blog

Time 2020-11-21 11:05:11

Web Name: Joe Duffy - Blog

WebSite: http://joeduffyblog.com

ID:122784

Keywords:

Joe,Duffy,Blog,

Description:

Founder/CEO Pulumi • Cloud, languages, and developer tools guy • Eat, sleep, code, repeat September 5, 2019 Journey to Pulumi 1.0 We started Pulumi a little over two years ago with an ambitious mission: to enable as many people on the planet to harness as much of the modern cloud as possible. The raw capabilities of modern cloud platforms are astonishing and are growing at an unbelievable pace. Yet they remain out of reach or hard to use for most of us. Pulumi’s mission starts by helping those who are already using the cloud — operations and infrastructure teams, as well as developers doing infrastructure — with an eye to empowering the growing number of over 20 million developers in our industry. I’m happy today that we’ve reached our first 1.0 milestone and would love to share a bit of background into why we’re so excited about the release and what comes next. July 25, 2018 Program the Cloud with 12 Pulumi Pearls In this post, we’ll look at 12 “pearls” – bite-sized code snippets – that demonstrate some fun ways you can program the cloud using Pulumi. In my introductory post, I mentioned a few of my “favorite things”. Now let’s dive into a few specifics, from multi-cloud to cloud-specific, spanning containers, serverless, and infrastructure, and generally highlighting why using real languages is so empowering for cloud scenarios. Since Pulumi lets you do infrastructure-as-code from the lowest-level to the highest, we will cover a lot of interesting ground in short order. To continue reading, head on over to the Pulumi blog… Hello, Pulumi! Today we launched Pulumi, a new open source cloud development platform. Using Pulumi, you author cloud programs usingyour favorite language, spanning low-level infrastructure-as-code to highly productive and modern container- andserverless-powered applications. We started on Pulumi a little over a year ago and I’m blown away by the progress we’vemade. This is our first step on the journey, and it’s a huge one, and I’m eager to share what we’ve built. June 1, 2017 A Brief Update on Me (in a Word, Pulumi) Almost unbelievably, it’s been six months since I blogged. I promise to return soon with more goods than ever before.And no, I haven’t become a professional MMA fighter. November 30, 2016 15 Years of Concurrency In a Tale of Three Safeties, we discussed three kinds of safety: type, memory,and concurrency. In this follow-on article, we will dive deeper into the last, and perhaps the most novel yetdifficult, one. Concurrency-safety led me to the Midori project in the firstplace, having spent years on .NET and C++ concurrency models leading up to joining. We built some great things thatI’m very proud of during this time. Perhaps more broadly interesting, however, are the reflections on this experienceafter a few years away from the project. Performance Culture In this essay, I’ll talk about “performance culture.” Performance is one of the key pillars of software engineering,and is something that’s hard to do right, and sometimes even difficult to recognize. As a famous judge once said, “Iknow it when I see it.” I’ve spoken at length about performanceand culture independently before, however the intersection of the two iswhere things get interesting. Teams who do this well have performance ingrained into nearly all aspects of how theteam operates from the start, and are able to proactively deliver loveable customer experiences that crush thecompetition. There’s no easy cookie-cutter recipe for achieving a good performance culture, however there are certainlysome best practices you can follow to plant the requisite seeds into your team. So, let’s go! The Error Model Midori was written in an ahead-of-time compiled, type-safelanguage based on C#. Aside from our microkernel, the wholesystem was written in it, including drivers, the domain kernel, and all user code. I’ve hinted at a few things alongthe way and now it’s time to address them head-on. The entire language is a huge space to cover and will take a seriesof posts. First up? The Error Model. The way errors are communicated and dealt with is fundamental to any language,especially one used to write a reliable operating system. Like many other things we did in Midori, a “whole system”approach was necessary to getting it right, taking several iterations over several years. I regularly hear from oldteammates, however, that this is the thing they miss most about programming in Midori. It’s right up there for me too.So, without further ado, let’s start. Safe Native Code In my first Midori post, I described how safety was thefoundation of everything we did. I mentioned that we built an operating system out of safe code, and yet stayedcompetitive with operating systems like Windows and Linux written in C and C++. In many ways, system architectureplayed a key role, and I will continue discussing how in future posts. But, at the foundation, an optimizing compilerthat often eeked out native code performance from otherwise “managed”, type- and memory-safe code, was one of our mostimportant weapons. In this post, I’ll describe some key insights and techniques that were essential to our success. November 19, 2015 Asynchronous Everything Midori was built out of many ultra-lightweight, fine-grained processes, connected through strongly typed message passinginterfaces. It was common to see programs that’d’ve classically been single, monolithic processes – perhaps with someinternal multithreading – expressed instead as dozens of small processes, resulting in natural, safe, and largelyautomatic parallelism. Synchronous blocking was flat-out disallowed. This meant that literally everything wasasynchronous: all file and network IO, all message passing, and any “synchronization” activities like rendezvousingwith other asynchronous work. The resulting system was highly concurrent, responsive to user input, and scaled like thedickens. But as you can imagine, it also came with some fascinating challenges. November 10, 2015 Objects as Secure Capabilities Last time, wesaw how Midori built on a foundation of type, memory, and concurrency safety.This time, we will see how this enabled some novel approaches to security.Namely, it let our system eliminate ambient authority and access control in favor of capabilities woven into the fabricof the system and its code. As with many of our other principles, theguarantees were delivered “by-construction” via the programming language and itstype system.

TAGS:Joe Duffy Blog 

<<< Thank you for your visit >>>

Joe Duffy's Blog | Adventures in the high-tech underbelly

Hot Websites