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 Jenni Konrad on May 26, 2011
In addition to Office Professional 2010, the Office365 Beta includes an updated communication and collaboration suite known as Microsoft Online Services. It consists of the cloud-based versions of Exchange 2010, Lync Server 2010, and SharePoint 2010.
The process of building solutions for SharePoint Online is similar to SharePoint 2010. Developers can use the same tools they’re accustomed to, such as SharePoint Designer 2010, Visual Studio, and the SharePoint API and SDKs. However, there are several key differences that must be taken into account when planning to deploy a SharePoint solution on Office365 Beta.
For example, Farm scope (for an entire server farm) is not available on SharePoint Online, as it runs in a shared datacenter with multiple clients. Only Site and Web scopes apply in the cloud. Full Trust is not available for the same reason.
While a majority of SharePoint 2010’s features are also available for SharePoint Online, some are not supported. (The Office365 documentation provides a full side-by-side comparison of the two platforms.) Business Connectivity Services are not currently included, but there are plans to add them at a later date. One of the more interesting exclusions from SharePoint Online is Web Services, because their use is not supported in only partial-trust applications. Microsoft does note, however:
“Although … external data connections are not available for use in sandboxed solutions, you can access them through client applications such as Microsoft Silverlight and ECMAScript (JavaScript, JScript).”
Because of the limitations of using SharePoint Online in the cloud, Microsoft recommends developing for it using Sandbox Solutions, so that applications will automatically meet the criteria for scope and trust.
Sandboxed SharePoint solutions in Visual Studio 2010 support IntelliSense, but do not include compilation support. To aid with this, Microsoft recently introduced Visual Studio 2010 SharePoint Power Tools, which add compilation support and a Visual Web Part project item template specifically tailored to sandboxed SharePoint Online projects.The SharePoint Online developer guide is available now from the Microsoft Download Center.Want to know how software releases can be stress-free and happen with one click? Try Go free!
Improving Software Delivery Cycles: Pre-requisites and Inhibitors
Automating Error Reporting for .NET Applications
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
Troubleshoot Java/.NET performance while getting full visibility in production
Go: Agile Release Management Solutions. Go enables predictable, defect-free and timely software releases.
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