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 Roopesh Shenoy on Sep 01, 2011
Windows Azure Integration Pack for Enterprise Library will bring support for a lot of Azure-only scenarios. One of these is auto-scaling of both web and worker roles, depending on various parameters such as CPU Utilization, message queue backlogs, specific date and time or even business metrics (such as # of unprocessed orders).
The Enterprise Library will get a new block – the Autoscaling Application Block. According to Grigori Melnik, the primary persona for this block is the application operator, and not the developer. The Application Operator can specify autoscaling rules in following steps -
The constraint rules can be mainly timetable based – you can set the minimum and maximum number of instances limits for given calendar date-time ranges. Reactive rules on the other hand react to metrics or KPIs, which could be performance metrics or business metrics. The rules can also be ranked so that conflicts are resolved more easily. Following actions will be supported by rules -
The block will have to be hosted in a client – a Windows Azure worker role, an on-premise Windows service or a standalone on-premise application. The features are scheduled to be released this fall but the team promises regular code drops on the Codeplex project, for receiving feedback. The team also has a feedback site allowing users to vote on features that should be taken up for the next release.
The Microsoft Enterprise Library is a collection of reusable software components (application blocks) designed to assist software developers with common enterprise development challenges. Developers can use these as-is or modify/extend them as necessary to build complicated enterprise applications. You can learn more about it from the msdn website.
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.
A preview of the Windows Azure Autoscaling Application Block (codenamed "WASABi") has been released via NuGet. We have also recorded a walkthrough using the block.
See blogs.msdn.com/agile/archive/2011/09/12/announc...
WASABi Beta has shipped. bit.ly/phMZj9
WASABi final release is available now, along with another new application block - the Transient Fault Handling Application Block and several additional nifty features (Wasabi Powershell cmdlets, blob configuration source, protected configuration provider). Check them out. bit.ly/v6A1aU
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.
3 comments
Watch Thread Reply