The Platform Advantage of Amazon, Facebook, and Google
Where’s the magic? [Amazon] The databasing and streaming and syncing infrastructure we build on is pretty slick, but that’s not the secret. The management tools are nifty, too; but that’s not it either. It’s the tribal knowledge: How to build Cloud infrastructure that works in a fallible, messy, unstable world.
Tim Bray, Senior Principal Engineer at Amazon, in Cloud Eventing
Ben Thompson makes the case in Apple's Organizational Crossroads and in a recent episode of Exponent that Apple has a services problem. With the reaching of peak iPhone Apple naturally wants to turn to services as a way to expand revenues. The problem is Apple has a mixed history of delivering services at scale and Ben suggests that the strength of Apple, its functional organization, is a weakness when it comes to making services. The same skill set you need to create great devices is not the same skill set you need to create great services. He suggests: “Apple’s services need to be separated from the devices that are core to the company, and the managers of those services need to be held accountable via dollars and cents.”
If Apple has this problem they are not the only Continue reading
Worth Reading: Gone in six characters
The post Worth Reading: Gone in six characters appeared first on 'net work.
Worth Reading: Gone in six characters
The post Worth Reading: Gone in six characters appeared first on 'net work.
Datanauts 033: Making Telemetry A Snap With Intel’s Open Framework
On today's episode of Datanauts we learn about Snap, an open source telemetry framework to make collecting, processing, and publishing data center metrics modular, dynamic, and open. Snap was originally developed by Intel.
The post Datanauts 033: Making Telemetry A Snap With Intel’s Open Framework appeared first on Packet Pushers.
Datanauts 033: Making Telemetry A Snap With Intel’s Open Framework
On today's episode of Datanauts we learn about Snap, an open source telemetry framework to make collecting, processing, and publishing data center metrics modular, dynamic, and open. Snap was originally developed by Intel.
The post Datanauts 033: Making Telemetry A Snap With Intel’s Open Framework appeared first on Packet Pushers.
Building the simplest Go static analysis tool
Go native vendoring (a.k.a. GO15VENDOREXPERIMENT) allows you to freeze dependencies by putting them in a vendor folder in your project. The compiler will then look there before searching the GOPATH.
The only annoyance compared to using a per-project GOPATH, which is what we used to do, is that you might forget to vendor a package that you have in your GOPATH. The program will build for you, but it won't for anyone else. Back to the WFM times!
I decided I wanted something, a tool, to check that all my (non-stdlib) dependencies were vendored.
At first I thought of using go list, which Dave Cheney appropriately called a swiss army knife, but while it can show the entire recursive dependency tree (format .Deps), there's no way to know from the templating engine if a dependency is in the standard library.
We could just pass each output back into go list to check for .Standard, but I thought this would be a good occasion to build a very simple static analysis tool. Go's simplicity and libraries make it a very easy task, as you will see.
First, loading the program
We use golang.org/x/tools/go/loader to Continue reading