Cloud Foundry: Design and Architecture
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Abel Avram on Oct 16, 2009
Wolfram|Alpha now has a Webservice API which can be used by web applications, desktop or mobile, to query the Wolfram|Alpha engine.
The responses are computed by Wolfram|Alpha in real-time using a supercomputer-class cloud infrastructure. The cloud needs fast processors and relatively little storage contrary to search engines which need lots of storage but slower processors. Search engines look through existing web pages or documents while Wolfram|Alpha computes query results based on raw data.
The queries sent to the API need to have the following REST-style format:
http://api.wolframalpha.com/v1/query?input=pi&appid=XXXX
The application sending this request must provide an APPID obtained from Wolfram Research upon registration. Each application must have its own APIID. The response returned by the Wolfram|Alpha engine is wrapped in XML or it can be returned as HTML/JavaScript. The contract does not allow caching because many of the responses depend on the location of the user making the request considering parameters like geographical position, currency, units, linguistic, and Wolfram|Alpha is in a continuous process of updating the raw data. The requests can specify geo-location information like latitude, longitude, geoIP.
The API is accompanied by several language bindings helping developers to start integrating such API calls in their programs. The languages covered are: .NET (VB), Perl, PHP, Python, Ruby, and soon to come C++, Java and Mathematica.
The API Reference document offers detailed information on how to make API requests and how to interpret the response. A pricing plan applies based on the number of requests sent per month. Grants are offered to selected start-ups and developers writing innovative applications using the API.
Requirements, quality and test management e-Kit
Architectures You've Always Wondered About @QCon New York
Introduction to WebSphere Liberty Profile
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
The WebSphere Liberty Profile for Developers: An Introduction
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
Andrew Watson talks about the work of the OMG, where CORBA is alive and well (hint: in your car), UML and UML Profiles vs. custom Modeling languages, DDS and other middleware, and much more.
Sohil Shah discusses creating iPhone and Android enterprise mobile applications based on cloud services using the open source platform OpenMobster.
Paul Sanford presents the transformations supported by data throughout its life cycle, and how that can be better done with Splunk, an engine for monitoring and analyzing machine-generated data.
A common “best practice” for unit tests is to only write a one assertion in each test. I intend to question this advice by showing that multiple assertions per test are both necessary and beneficial.
John Rauser presents the architectural and technological evolution of Amazon retail websites starting with 1994 and ending with adopting Amazon Web Services.
Michael Stal discusses system architecture quality, how to avoid architectural erosion, how to deal with refactoring, and design principles for architecture evolution.
Every developer has had to integrate with another system, API or component. Tis article provides strategies to handle the change and for he separating system boundaries.
2 comments
Watch Thread Reply