Why Do Developers Care About Cloud API Compatibility?
I’m a bit confused as to why respected members of the OpenStack community would disagree on what I don’t even consider to be a problem, as the OpenStack APIs didn’t feel foreign at all when I used them myself! (see this talk from the OpenStack summit)
Since you’re reading this post, I’m hoping you agree! But I digress.
I decided to consult with the developers here at Scalr. After all, they have a fair bit of experience integrating different and API-incompatible clouds: the Scalr Cloud Management Platform works with numerous Public Clouds (Amazon EC2, Google Compute Engine and more) and Private Clouds (OpenStack, CloudStack, Eucalyptus).
So, in a quest for a better understanding, I asked three Scalr developers for their opinion:
- Igor Savchenko, CTO at Scalr.
- Vitaliy Demidov, who owns the “Scalr Core” project, which is the backend for the Scalr UI.
- Marat Komarov, who’s responsible for the “Scalarizr” project, which is the guest agent for Scalr that lives on Scalr-managed instances.