Last year, Adaptive Computing introduced Moab Web Services (MWS) in the 7.0 product releases. This marked a significant shift in the way that we thought about APIs. Historically, we sliced and diced APIs that were in C, Java, Perl, Python, and so on. Moab Web Services attempts to tackle the problem from a different angle using RESTful APIs. With Moab touching so many different aspects of a system, we see the need to provide a toolkit to connect into customer specific components that customize workload execution, diagnostics, visualization, and more.
So, instead of trying to reinvent the wheel, we drew upon principles that are easily understood, widely adopted, and clearly espoused, creating a type of “API Gold Standard.” Implementing a user centered design strategy with regards to our APIs has paid significant dividends. We believe strongly in “eating our own dog food.” We have been able to get feedback and validation from external consumers and internal consumers of the APIs, whether it is our UI developers or professional services engineers, and we have improved MWS with each release.
We are seeing a growing trend of HPC sites adopting their own RESTful APIs. Adaptive is committed to delivering and supporting simple and usable APIs that satisfies developers who are integrating into the Moab ecosystem. However, in the cloud environment, the battle of trying to standardize on cloud APIs is only getting bloodier.
Comment and share: Through a user-centered design strategy, Adaptive Computing is working to create APIs that work specifically for our customers’ environments. What do you think about MWS? Are Adaptive Computing’s APIs heading in the right direction?