• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Hardware choice query

 
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am wandering about If I have to justify my choice of HW profile or not.

Also I want to know the minimum requirements for running Apache HTTPD server , as I have searched on apache website but I only found storage requirements.

Thanks in advance
 
Bartender
Posts: 3648
16
Android Mac OS X Firefox Browser Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Marwan Adel wrote:I am wandering about If I have to justify my choice of HW profile or not.

Also I want to know the minimum requirements for running Apache HTTPD server , as I have searched on apache website but I only found storage requirements.

Thanks in advance



I personally did not in mine even though I mentioned hardware profile. But I did mention in deployment diagram that such profiles are references and in html about stress testing and load testing

Regarding HTTP web server who knows but I reckon a typical server spec will suffice.
 
Saloon Keeper
Posts: 27808
196
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Apache HTTPD is not a really resource-hungry program, although it will happily spawn multiple threads for performance. I have one server whose thread memory lists at a "mere" 240 MB virtual.

Total resource requirements depend very much on what modules are installed and in-use and what resources the webapps and their frameworks (such as PHP and django/python) consume.

However, a Raspberry Pi is quite sufficient for many things.

If you have a 2GB RAM/2HGz CPU/5GB disk machine, you're pretty much home free. That will host Apache and quite a bit more.
 
Ranch Hand
Posts: 46
2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
It's up to you to justify your hardware profile. In my solution I did justify some special aspects of the profile that would allow me to achieve my NFRs. Other than that I went with pretty conventional server hardware.

The minimum requirements for Apache HTTPD are quite low, as mentioned. However, I would say it's safe to go with a "standard" business level server even if it's going to be underutilized.
 
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Based on my experience, I think choice of infrastructure and platform depends on,

1. NFRs
2. Direction from enterprise architecture group (unless NFRs demands new HW/platform)

Where EA group is not established, you are free to your choice.

In my solution, I assumed about platforms and kept conventional hardware. Please do mention assumptions in your deployment diagram notes & assumption section.
reply
    Bookmark Topic Watch Topic
  • New Topic