Skip to content

Language diversity

If you look at the projects within the ASF, you'll notice right off the bat that the vast majority are Java. We do have a handful of other projects based on other languages but, for better or worse, most of 'em are Java. But if you look at the code that *powers* the ASF you'll notice a big difference. For one thing, for the most part, we do not run anything that requires a JVM (well, we prefer not to). Also, we prefer all of our sites be as static as possible, which makes mirroring them easier. But the biggest surprise might be just how much we use scripting languages for all the tasks/applications/tools that we need. We use a suite of Perl, Python and Ruby, with Perl being the clear frontrunner (mostly since JoeS is such a Perl monger). What I think is so useful about all this is that it gives a true, clear perspective on how real infrastructure is architectured (my word). People tend to focus, unjustly, on the applications themselves, and give little thought or credence on the infra required to truly support and implement all that. And this skewed perspective can easily result in bad, dangerous mistakes when making the transition from one architectural design to another, because it ignores a big, big part of the puzzle. As people look at, investigate and migrate into the cloud, this will become even more of an issue. And a concern.
Categories: ASF


No Trackbacks


Display comments as Linear | Threaded

No comments

The author does not allow comments to this entry

Add Comment

Standard emoticons like :-) and ;-) are converted to images.

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.

Form options