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 Jun 21, 2011
Richly formatted emails can require quite a bit of CSS, but since email clients don’t always handle CSS well the styles need to be inlined. With Ruby this is easily handled with the Alex Dunae’s Premailer library, but calling it from .NET isn’t palatable to most developers. So Martin H. Normark built a .NET version called PreMailer.NET.
PreMailer.Net is based on code from these two projects:
For those who would like to try the original you can check out Kevin Blake’s introduction on executing Ruby code from .NET. Changes to Premailer may be needed to support the IronRuby runtime.
The original Premailer is licensed under the BSD 3-Clause License. Premailer.NET doesn’t include a license.
Building HTML5 Apps in Hours, Not Days
Early Access! Download JBoss Developer Studio 5.0 now, with packages for Mac, Windows or Linux!
Tools to unit test your JavaScript
Automating Error Reporting for .NET Applications
Introducing SQLFire: a memory-optimized, high performance SQL database
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