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 Alex Blewitt on Sep 09, 2011
Today's release of SpringSocial 1.0 brings a standardised way to connect to social providers under a consistent API. The providers supported for the initial release include connectivity to Twitter, Facebook, GitHub and Trippit, and includes an SPI for other providers to be added.
The goal of SpringSocial is to provide programmatic access to social oriented sites (those that deal with a 'status' or have other ways of exchanging messages). It can also be used to provide a sign-in controller which allows the user to sign in with their Facebook/Twitter handle rather than having to have a dedicated authentication provider.
Since many of these sites use OAuth to provide authentication, the primary use case for SpringSocial is in a web-based application that can perform the web redirects necessary to authenticate a user in a web flow. For example, an on-line shopping application might allow a user to sign in with their Facebook credentials and provide a means to post offers to that site.
However, not all providers use the same variation of OAuth. There are three versions of OAuth in use; 1.0, 1.0a and 2.0 – and a variety of providers use different flavours. The SpringSocial core SPI has means for talking across these dialects, and each provider (Twitter, Facebook) has the definitions built-in to allow connectivity for that specific provider. (The 1.0 and 1.0a are almost identical, but the latter fixes a security bug which uses the OAuth key to sign the originating domain as well as the request, not just the URL.)
A variety of quick start documentation and samples are available. SpringSocial 1.0 requires Spring Core 3.0.5 or greater, although Spring Core 3.1 is recommended. It is available for immediate download, or can be added to a project by adding Maven dependencies.
Introducing SQLFire: a memory-optimized, high performance SQL database
RDBMS to NoSQL: Managing the Transition
App Server Evolution: REST, Cloud, and DevOps Support in Resin 4
VMware vFabric SQLFire - Test drive the data management system with memory speed, horizontal scalability and a familiar SQL interface
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.
1 comment
Watch Thread Reply