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 Jul 31, 2007
With the release of Beta 2, the feature set for the flagship .NET languages C# and Visual Basic have been solidified. In the past we have covered VB-only features like mutable anonymous types and XML Literals. Today we cover a couple of the C# only features.
The first feature is some syntactic sugar for creating data classes. Using the Automatic Properties syntax, C# developers can expose properties without writing the associated boilerplate code.
public int X { get; private set; }
In this example, a property called X is created with a public getter and a private setter. When using this sytnax, the compiler will automatically generate a private member variable and the associated getter and setter.
While an automatic property looks like a public member variable, it has some notable advantages. First of all, a lot of the built-in classes such as lists and grids only bind to properties. Over the long term, this allows developers to later add more complex logic without changing the public interface.
Another feature one will see in C# is collection initializers.
var mystrings = new List<string> { "Alice", "Bob", "Charlie" };.
Using a syntax similar to that of array initializers, this code will call the objects Add method for each item in the braces. This is not based on any particular interface, the type just needs to expose a method named Add that takes one variable.
These examples were pulled from Jomo Fisher's The Least You Need to Know about C# 3.0.
With all the excitement about closures and lambda expressions, it should be noted that Visual Basic will only be supporting one-line anonymous functions. C#, on the other hand, will continue to support multi-line line anonymous functions using the new delegate syntax.
Automating Error Reporting for .NET Applications
RDBMS to NoSQL: Managing the Transition
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
"In this example, a property called X is created with a public getter and a private setter. When using this sytnax, the compiler will automatically generate a private member variable and the associated getter and setter."
What will the private field's name be? I am hoping you say "the public property's name, with the first letter lowercase, and an underscore prepended". In this case that would mean "_x".
This reminds me of a desire for a new accessor, something like "super private", where the field is only accessible to a single property, and nowhere else, including methods and properties of the same class.
> New C# Features Not Found in VB
One it's always had is some modicum of respect by the community for those who use it...
The community of language snobs? Yeah the lack of their respect is something that kept me up at night, when I was a well paid and very successful VB programmer.
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