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 Werner Schuster on Dec 26, 2010
Ruby VMs are improving steadily and the last few weeks have seen a bunch of new releases.
Rubinius 1.2 has been released, bringing improvements in memory efficiency and debugging. Evan Phoenix explains the details of the changes in Rubinius 1.2, such as the per object memory use:
[..] We focused on improving the memory usage per object. Specifically, how an object stores its instance variables in memory. Because Ruby does not require instance variable declaration, the simplest way to model instance variables is with a hash. This is precisely what Rubinius used to do. The issue is for classes that have a small number of instance variables. In this case, the size of the hash table is substantial, needing more than 100 bytes of memory just to store one word (either 4 or 8 bytes)! [..]
The new code is based upon an easily observable assumption about a class, namely that it defines the vast majority (usually all) of its methods before an instance of the class is created. We exploit this by running some code the first time an instance of a class is created which looks at all methods available to instances of this class. This means all methods defined in the class itself, its superclasses, and any mixed in modules. From the methods, we build a table of all instance variables those methods use.
Now we can construct a very good picture of how memory should be laid out for instances of this class, allowing us to store the instance variables in memory without needing a hash table. The memory usage typically goes from 100 bytes to 8 bytes on a 64bit machine.
Rubinius has long had a powerful Debugger API, and now Rubinius 1.2 adds ruby-debug support. Debugging memory usage or memory leaks is aided by the heap dump feature, which can be used with Rubinius::VM.dump_heap("/path/to/file"). An alternative way of creating a heap dump is to use another useful Rubinius feature: the Query Agent, which allows monitoring tools to access Rubinius information as well as trigger certain actions.
MacRuby 0.8 is available and mostly improves stability and compatibility. The project will now focus on the 1.0 release:
We intend to deliver starting from now releases much more frequently than before. We hope that users will then test MacRuby more frequently, and as such, report more bugs.
However, we do not expect further releases to introduce significant features, as we are now focusing on stability and compatibility issues.
Finally, both old and new MRIs have just received patchlevel releases: MRI 1.8.7 with p330 and 1.9.2 with p136, the first update since the 1.9.2 release.
RDBMS to NoSQL: Managing the Transition
Banking Case Study: Scaling with Low Latency using NewSQL
Tools to unit test your JavaScript
App Server Evolution: REST, Cloud, and DevOps Support in Resin 4
Introducing SQLFire: a memory-optimized, high performance SQL database
VMware vFabric SQLFire - Test drive the data management system with memory speed, horizontal scalability and a familiar SQL interface
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