· · Cloud
· I work in AWS’s Serverless group, and in the process of pulling together my presentation at re:Invent, discovered that I have a lot of opinions on the subject and, while they may well be wrong, are at least well-informed. You can watch that YouTube, but who’s got an hour to spare? And anyhow, blogging’s really my favorite medium, so here we go. If I tried to glom them all together into one mega-essay it’d be brutally long, so let’s go short-form ...
SF-2: Why Serverless?
· Well obviously: Frugality, security, and elasticity. But I want more, I want better software ...
SF-3: Serverless Everything?
· Sometimes we fans get a little over-excited and declaim that everything should be serverless. After all, we’re pretty convinced that owning data centers and computers is becoming a thing of the past. Well then, how could configuring your own hosts and paying for them even when they’re not working ever be a good idea? Let’s try to be moderate and pragmatic: Serverless, where possible ...
SF-1: What Is Serverless?
· I don’t think it’s that complicated: If you can’t see the servers in the service, then it’s serverless. Yeah, they’re still there, but the whole point is that you can mostly not worry about them ...
· We were arguing at work about different modes of computing, and it dawned on me that the big arguments for going serverless are business arguments, not really technology-centric at all. Maybe everyone else already noticed ... [3 comments]
· I did some recreational programming over Christmas and the blog I wrote about it is now guesting in Jeff Barr’s space for your amusement; try the software at IsItOnAWS.com. What I didn’t do there was relay the lessons I picked up along the way; one or two are around AWS, but most follow from this being my first nontrivial expedition into the land of NodeJS. So (acknowledging that only 0.8% of my profession aren’t already Nodesters), here they are. Spoiler: I don’t like Node very much ... [5 comments]
Two AWS Years
· Wow, it was December 2014 when I climbed on board this train. I’m sitting in a pretty interesting place and feel I owe the world some reportage ... [5 comments]
· A couple days ago in New Home Network I posted a request for advice on a home NAS box and networking hardware. Now I have the storage box, and boy was it ever easy and straightforward and anxiety-relieving. If you haven’t done this already, you might want to ... [11 comments]
· So, I helped build Amazon CloudWatch Events (blog, AWS console), which just launched. Been a while since my last extended spell of being an actual software engineer. Shipping feels good ... [1 comment]
One Amazon Year
· December first made it a year here at Amazon Vancouver’s engineering castle in the sky. I’m working with good people in a cool office on interesting stuff. It’s at the white-hot center of server-side computing but surprisingly unsurprising ... [10 comments]
re:Invent in Vegas
· That was intense. AWS’s customers are great. But I wish I could like Vegas more ...
· As of December I’m working for Amazon. This will be different from my last few gigs; in particular, don’t expect to read about it here ... [20 comments]
· We’re working on a fairly substantial revision of the Sun Cloud API, motivated by this problem: In a RESTful context, how do you handle state-changing operations (POST, PUT, DELETE) which have substantial and unpredictable latency? ... [26 comments]
By Tim Bray.
I am an employee
of Amazon.com, but
the opinions expressed here
are my own, and no other party
necessarily agrees with them.
A full disclosure of my
professional interests is
on the author page.