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 Alex Blewitt on Feb 14, 2012
JetBrains, the company behind the popular IntelliJ Java IDE, have open-sourced their Kotlin programming language under the Apache License.
The basic compiler (which they call kompiler, starting a new legacy of K-prefixed terms – even kontributors, which they are looking for …) is available separately and can be embedded in Maven, Ant or Gradle toolchains. This allows code to be developed in the IDE to be built with existing mechanisms, requiring minimal intervention in order to use in a new environment, or even if working on a project with other developers who do not have the Kotlin plugin installed.
The IntelliJ Kotlin plugin extends the Java compiler to allow Kotlin code to be written, compiled and debugged. In addition, helper functions have been written for the basic Java collections, which allow a more fluid interface ahead of the Collections extensions coming up in Java 8.
There are separate Kotlin to Java comparison and Kotlin to Scala comparison papers available, compare and contrasting the features of both. Whilst Scala may remain more powerful, Kotlin tries to be a better Java with functions, mattern matching, null pointer avoidance and generics. The language also supports traits and pattern matching.
The Kotlin plugin will be available in a future release of IntelliJ (though the Early Access Program has preview builds available, and snapshot builds of Kotlin are available via the JetBrains GitHub page). However, you can get a feel for the language now with a web-based demo which allows you to edit Kotlin code, compile and run via your web browser.
Kotlin, like Xtend, is aiming to be a better Java rather than an entirely new platform. Both compile down to bytecode (although Xtend translates into Java source first and lets the Java compiler do the hard work), and both bring functions and extension functions (the ability to statically add a new method to an existing type within a limited scope). Whilst Xtend is Eclipse-based, and Kotlin is IntelliJ based, both have headless builds. The winner might just be the language which evolves to the other IDE first.
Alex Blewitt can be reached on Twitter as @alblue and blogs regularly at alblue.bandlem.com.
Tools to unit test your JavaScript
Introduction to WebSphere Liberty Profile
The WebSphere Liberty Profile for Developers: An Introduction
Improving Software Delivery Cycles: Pre-requisites and Inhibitors
I haven't heard of Xtend yet. Interesting, but... if it generates java sources, and then javac/ejc compiles it into the final bytecode, I suppose the debug information is about the java sources, not Xtend sources, which would make it completely useless. I'd just hate having to debug generated code...
Debugging is a tooling aspect. JSR-45 to the rescue : vimeo.com/26046484
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