Recently by George Reese

10 steps that help online systems architects build authentication systems that empower their users to protect themselves against the multi-site attack strategies behind a number of recent high-profile attacks.
One of the little discussed features of the Tesla Model S is that it is another block in the "Internet of Things" in which everything has an API and everything needs to be secured reasonably. There's a common thing emerging in the Internet of Things in which security is an afterthought in API design. While the Tesla Model S REST API does not compromise the safety of the vehicle, it carries an authentication architecture that is lacking.
Microsoft and Google moving into the IaaS space is the clearest signal the market has seen that Platform as a Service just isn't ready for the big leagues yet. These moves may even indicate that PaaS isn't the grand future of cloud everyone has been predicting, but instead just a component of a cloud infrastructure. At VMware, however, PaaS is their answer to AWS and the various cloud platforms competing with vCloud. If the world isn't ready for PaaS, then VMware has a huge hole in its cloud strategy because vCloud just doesn't cut it for cloud-scale infrastructure.
One of the more snarky things you will hear said about NoSQL databases is that they are "write-only" databases or "no query" databases. It is fair to say that NoSQL databases are often challenging to pull data from when you are doing more than fetching values by their keys. The Open Source Dasein Persist object/relational mapping tool helps solve that problem for Java programmers using Riak.

API Versioning

By George Reese
October 12, 2011

API versioning is something a lot of API designers don't worry about until the second version of their API. API versioning, however, is a controversial subject with strong opinions on both version representation and behavior.
The argument for EC2 as a defacto standard is, at some level, the same as it is for any defacto standard: through the EC2 API, you eliminate the need for others to learn some custom API and you can leverage the existing, sizable ecosystem. But there is no such thing as the EC2 API. EC2 is actually many different APIs and adopting the EC2 API as a standard ultimately implies supporting all of those APIs.
I've never seen a perfect REST API. But I have seen some of the most horrible mistakes repeated over and over again by people building heavily consumed APIs. Here's a list of the Good, the Bad, and the Ugly of REST API design.
So many cloud pundits are piling on to the misfortunes of Amazon Web Services this week as a response to the massive failures in the AWS Virginia region. If you think this week exposed weakness in the cloud, you don't get it: it was the cloud's shining moment, exposing the strength of cloud computing.
In my discussion of the Whole Cloud, I assumed as fact that a mature cloud computing infrastructure leverages all kinds of clouds. Given the amount of energy put into arguments on the subject, it's obviously not a given to most people. Today, I want to talk about how these different "pieces of cloud" can be integrated together from a decision-making perspective
A few companies are currently well positioned to create a view of cloud computing that encompasses all aspects of cloud from IaaS to SaaS, public cloud and private cloud, internal and external. A mature cloud infrastructure, however, will be made up of all pieces of the cloud puzzle.

News Topics

Recommended for You

Got a Question?