ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

The Motivations of A shift From Apache to Apache Solr

Updated on May 30, 2014

The Apache HTTP Server especially versions 2, 2 and 17 with applications in windows 2003, and 2008 has some problems related with transfer performance with users on some windows for instance windows 7 and XP. Other problems of the software include slow installations especially when using the IBM installer and network performance issues in some platforms such as windows 7 and Vista. In essence, the consistent performance issues and network problems of Apache on some windows are what prompted a shift into Apache Solr. For instance, it was realized that the performance was exceedingly slow on Windows 7 and XP clients. Despite various investigations, the technical operators could not establish the cause for these phenomena. Owing to this hindrance, the management advised the affected clients to use other alternatives such as 11S or Linux instead of Apache. The purpose for coming up with Apache Sorl was to eliminate the net work and low performance of this software (Gosaammer, 2013, 1).

Overall, the Apache server could be described as being moody. It can perform well at other times while at some other time, the pages could take long to load for no apparent reason. Moreover, Apache’s default installation system has unnecessary stuff. This unnecessary stuff is eliminated in Apache Solr. Many apache clients also complained on slow loading of pages especially those with many images to be displayed. These constant delays and hangings could make many of them to be annoyed. These were contrary to other sites where the sites or images load instantly. When this slowness became widespread, there was no alternative but to shift to another platform. Although the problem was a random one (that is not consistent), there are specific sites and windows, which have a tendency of loading slowly and other sites, have no images displayed in them (Apache, 2013, 2)

Another reason that necessitated the shift from apache to Apache solr is that the server administrator in apache had no control on the application since someone else wrote it, the Apache Sorl application is written by administrators. A gain, apache did not offer support for its running its application with some network privileges. Further, it did not offer security on local machines. The primitive support for some operating systems such as windows existed to help users on developing the content in WebPages as well as acting as an intranet server. This points out to the reason why the Apache Software Foundation did not endorse some operating systems such as Windows 9x to run on Apache server (Apache, 2013,1).


    0 of 8192 characters used
    Post Comment

    No comments yet.


    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at:

    Show Details
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the or domains, for performance and efficiency reasons. (Privacy Policy)
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)