4 ms·

>Apache is great at serving content; Apache isn't the best choice anymore for serving applications. What is?

• kbenson 13y ago
  To clarify, it's not the best choice for serving applications where Apache works as anything but a proxy. For what's best, take your pick of any framework that entirely decouples the application directory structure from the routes and keeps the logic for it all completely internalized. All logic for how URI's are handled should be within the application configuration or code. Something written in the target language will probably provide far more benefits than whatever is lost through Apache. Whether Apache is in the path to your application is irrelevant, whether Apache does anything except note that a request should be handled by another application and hand the entire request off without change is not.
  • cadalac 13y ago
    Oh I see. I'm a beginner programmer and I just started learning PHP with Apache yesterday. I was up until 3AM installing and configuring it all along with MySQL and MyPHPAdmin last night. I thought by your post that I should be learning something else instead ;-).
    • kbenson 13y ago
      In some respects, Apache + mod_php is actually harder to get set up and working that some of the other frameworks, assuming it's not already configured for your box (many linux distros include packages so "it just works").
• vec 13y ago
  Generally the application itself. Listening on an http port or a unix socket is pretty easy in most modern languages. Then use a normal HTTP server like apache to listen to incoming connections and proxy them on to whatever port on localhost your application is listening to.