{"id":71146,"date":"2009-12-08T10:48:00","date_gmt":"2009-12-08T15:48:00","guid":{"rendered":"http:\/\/www.cmswatch.com\/Trends\/1756-Taming-Apache-Menagerie?source=RSS"},"modified":"2009-12-08T10:48:00","modified_gmt":"2009-12-08T15:48:00","slug":"time-to-tame-the-apache-menagerie","status":"publish","type":"post","link":"https:\/\/mereja.media\/index\/71146","title":{"rendered":"Time to Tame the Apache Menagerie"},"content":{"rendered":"

Subscribers to our Search and Information Access Research<\/a> are well aware that we’ve been increasing our coverage of Apache<\/a> Lucene<\/a> lately, in keeping with the phenomenal — and still growing — popularity of Apache’s well-known open-source search engine.<\/p>\n

This has led to a coverage conundrum (of sorts) for us, inasmuch as it is no longer possible to cover Lucene properly without also devoting a good deal of discussion to closely related projects like Nutch and (especially) Solr. This becomes problematic at times, not just because we’re in essence covering multiple projects under one conceptual umbrella, but because the functional and architectural boundaries between things like Lucene, Nutch, and Solr — though well understood by developers — are easily blurred in a semi-technical writeup unless special care is taken to distinguish between concepts like search server<\/em>, search engine<\/em>, crawlers versus parsers, etc.<\/p>\n

Some of these bits are unique to Lucene (the "engine" part, for example, consisting of the indexer and query framework), whereas others are unique to Solr (e.g., the "query server" bits that handle data-fetching and -passing over HTTP), whereas other bits (like UI widgets for faceted search) aren’t there at all — you have to build them yourself.<\/p>\n

In short, as we expand our coverage of Lucene, we find ourselves investing ever-greater amounts of time and care in tiptoeing the conceptual boundaries around Solr, Nutch, Lucene, Hadoop<\/a>, and so on. We think we do a pretty good job. But it’s surprising how many people (including us, at times) still<\/em> have trouble keeping the various pieces of the Apache search world straight.<\/p>\n

Our job isn’t made easier by the Apache Foundation’s laissez-faire<\/em> attitude toward project naming, which has led to an out-of-control zoo of projects with some sensical but oftentimes nonsensical names like Hadoop, Mahout<\/a>, Tika<\/a>, Lenya<\/a>, James<\/a>, Mina<\/a>… and the list goes on.<\/p>\n

There’s a longstanding tradition in R&D (and elsewhere, of course) of using whimsical, short, purposely obscure code names for projects early in their lifetimes. And that’s fine for prototypes and pre-release versions of software. But a mature product needs a mature name, preferably something descriptive and apropos. For example, Droids<\/a> is not an entirely inappropriate name for Apache’s autonomous-robots project. It’s at least semantically aligned with the domain. But even if you know enough Hindi to figure out that Mahout is a term for the driver of an elephant, you’re not likely to divine that it is also an open-source project for distributed machine learning algorithms on the Hadoop platform (and you shouldn’t then be forced to look up what Hadoop means, and so on).<\/p>\n

So, Suggestion No. 1 for Apache: When a project graduates from incubation, give it a real name. <\/em><\/p>\n

It would also help if Apache namespaced subprojects and\/or related projects in a logical fashion — a fashion that shows the relationship. For example, would it hurt to call Solr "Lucene Search Server" — or at least "Lucene Solr"? Solr is, after all, strictly dependent on Lucene, much the way Sling<\/a> is dependent on Jackrabbit<\/a>.<\/p>\n

Suggestion No. 2: Make dependencies evident in project names. It helps people understand what the projects are about.<\/em><\/p>\n

If the world is headed toward a Lucene-* stack (as it surely is), wouldn’t it be nice to be able to refer to it that way? If people are having a hard time understanding that Solr is a search server, wouldn’t it make sense to put "server" in the name? Bottom line, a rational namespace for Apache projects would be a big win for all concerned.<\/p>\n

Those of us who regularly tiptoe the boundaries around Apache’s zoo of related projects would like to occasionally REST<\/a> our feet.<\/p>\n","protected":false},"excerpt":{"rendered":"

Subscribers to our Search and Information Access Research are well aware that we’ve been increasing our coverage of Apache Lucene lately, in keeping with the phenomenal — and still growing — popularity of Apache’s well-known open-source search engine. This has led to a coverage conundrum (of sorts) for us, inasmuch as it is no longer […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-71146","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/posts\/71146","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/comments?post=71146"}],"version-history":[{"count":0,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/posts\/71146\/revisions"}],"wp:attachment":[{"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/media?parent=71146"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/categories?post=71146"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/tags?post=71146"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}