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 Bienvenido David III on Jan 17, 2012
Mozilla has launched the Mozilla Labs Apps Developer Preview, an early view of the Mozilla Labs Apps marketplace. The Mozilla Labs Apps project allows developers to create HTML5 applications that run across multiple devices (desktop, mobile, tablet) using Web standards like HTML5, CSS and JavaScript. The Mozilla Labs Apps project will also operate its own marketplace to help in the distribution of these HTML5 applications. Mozilla is planning to launch the real marketplace for apps early 2012.
Mozilla Labs Apps are built using standard Web technologies with additional metadata from the Mozilla app manifest that allows the User Agent to discover, install, launch, and grant apps additional privileges. You only need to create an app manifest to create an app for an existing website. Of course, apps will have to take into consideration many factors to give the best user experience on different devices. This includes a responsive Web design that will look good on all devices, offline caching and storage, and device APIs like geolocation, orientation.
For these apps to work on a variety of different devices, Mozilla has created "App Runtimes". The HTML5 App Runtime is implemented in JavaScript and can be used in any browser. The App Runtime for Firefox is implemented using the Mozilla Add-on SDK and provides a better installation and launch experience for Firefox users. The App Runtime for Android allows these apps to work on the Android platform. The App Runtime for Android is a Java application with an embedded PhoneGap instance. Note that this current preview has no support for iOS.
Similar to the concept of the Mozilla Labs app manifest, the W3C Widgets specification standardizes the packaging and metadata of HTML applications. Opera fully supports the W3C Widgets specification and operates a "widget store" at http://widgets.opera.com. Google also allows you to create a Chrome Web App, taking metadata from a Chrome Web app manifest file. These Chrome Web Apps can be packaged and distributed on the Chrome Web Store.
What's coming next? Here are a few things the Mozilla Labs Apps team is working for the next few months.
To get started, visit the Mozilla Apps Getting Started page. The Developer Preview website where you can test the features of the Mozilla Apps marketplace is limited only to 3,000 developers and is currently closed. To get notified of future openings, you can subscribe to the Apps Developer Newsletter. For more information about the preview, read the official announcement at hacks.mozilla.org. For a more in depth look into the Mozilla Labs Apps system, read the Behind the Mozilla Apps Developer Preview blog post.
Big Data, Cloud & Mobile: Navigate the New Development Reality with Resources from IBM
Building HTML5 Apps in Hours, Not Days
Taming HTML5 and JS: High Performance Mobile, WebKit, FireFox Dev Tools @QCon New York
Early Access! Download JBoss Developer Studio 5.0 now, with packages for Mac, Windows or Linux!
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.
No comments
Watch Thread Reply