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 Jonathan Allen on Feb 14, 2012
Simon Cropp has released an IL weaving tool that wires property changed notifications into automatically implemented properties. IL weaving is a technique in which the IL code in an assembly is rewritten to add functionality. In a broader context this is known as aspect-oriented programming.
An interesting feature of Simon’s Notify Property Weaver is that it doesn’t require attributes or any other form of tagging. Instead it analyzes the code to determine the relationship between normal and calculated properties. These relationships are then used to ensure that all of the appropriate property changed notifications are raised.
Notify Property Weaver runs as an MSBuild task so projects that use it do not need to distribute any additional libraries. It can be configured manually or via a Visual Studio Extension. It supports .Net 3.5+, Silverlight 3+, and Windows Phone 7 and has been released under the MIT License.
Agile Development: A Manager's Roadmap for Success
Branching & Merging Efficiently: A Guide to Using Process-Based Promotional Patterns
Adopting Git for the Enterprise: Risks and Considerations
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