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 Apr 05, 2011
ronPython 2.7 has been released with new features including improved tooling inside Visual Studio, better interoperability with LINQ and extension methods, better documentation, and full language parity with Python 2.7.
The release notes give the following new set of improvements
This release implements the new builtin _io module, includes dictionary and set comprehensions, set literals, supports multiple context managers in the with statement, and adds several new functions to the itertools methods, and auto indexing for the new string formatting. There are also numerous updates to the standard library such as ordered dictionaries and the new argparse module.
and bug fixes
This release includes major performance improvements in cPickle, the sum built-in function, and includes support for fast exceptions which do not use the .NET exception mechanism. There have also been improvements to significantly reduce memory usage of the IronPython ASTs. One of the end results of these numerous improvements is that IronPython’s startup time has decreased by 10% when compared to IronPython 2.6.1.
This release also includes the option to install “IronPython Tools for Visual Studio” within the IronPython installer. This works on top of VS 2010 and now supports XAML and WPF including databinding to Python classes dynamically.
This is the first full community release, and is a major milestone in IronPython development – it proves that there is a vibrant community willing to continue improving the language even without funding from Microsoft. This release all the more exciting since strong integration with Visual Studio was a very popular feature request by Microsoft customers and Jeff Hardy, IronPython MVP and one of the co-ordinators of the IronPython project, himself once said that adding IronPython support to Visual Studio is very hard.
However, there is already some confusion about the default tooling for IronPython, with Microsoft announcing the Python tools for Visual Studio project which is currently in Beta.
IronPython is an implementation of the Python programming language targeting the .Net Framework and Mono. The project was started by Microsoft with the first version shipping in 2006. In 2007, the Dynamic Language Runtime was announced to enable interoperability between Dynamic Languages. After nearly 3 years of development, recently, Microsoft handed over the further development of IronPython to the community.
RDBMS to NoSQL: Managing the Transition
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
The WebSphere Liberty Profile for Developers: An Introduction
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.
2 comments
Watch Thread Reply