What is Apache HTTP Server?
Who uses Apache HTTP Server?
Apache HTTP Server Integrations
Why developers like Apache HTTP Server?
Here are some stack decisions, common use cases and reviews by members of with Apache HTTP Server in their tech stack.
As a web server for my local dev environment as well as deployment servers. Apache HTTP Server
Good old Apache2 hasn't failed me yet. I use it because I know it. Apache HTTP Server
Here are some stack decisions, common use cases and reviews by companies and developers who chose Apache HTTP Server in their tech stack.
When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?
So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.
React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.
Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.
Early job listings for “Application Engineer” required applicants to have “Fluency with the LAMP stack”. Linux, Apache, MySQL, PHP was and still is a popular choice for web applications which Slack started out as. Other requirements included an excellent understanding of networking, HTTP, JSON, and Smarty (template engine for PHP). According to an AWS case study “Tiny Speck—the original company name for what became Slack Technologies—used AWS in 2009 when it was the only viable offering for public cloud services.”
We've been happy with nginx as part of our stack. As an open source web application that folks install on-premise, the configuration system for the webserver is pretty important to us. I have a few complaints (e.g. the configuration syntax for conditionals is a pain), but overall we've found it pretty easy to build a configurable set of options (see link) for how to run Zulip on nginx, both directly and with a remote reverse proxy in front of it, with a minimum of code duplication.
Certainly I've been a lot happier with it than I was working with Apache HTTP Server in past projects.
nginx or Apache HTTP Server that's the question. The best choice depends on what it needs to serve. In general, Nginx performs better with static content, where Apache and Nginx score roughly the same when it comes to dynamic content. Since most webpages and web-applications use both static and dynamic content, a combination of both platforms may be the best solution.
Since both webservers are easy to deploy and free to use, setting up a performance or feature comparison test is no big deal. This way you can see what solutions suits your application or content best. Don't forget to look at other aspects, like security, back-end compatibility (easy of integration) and manageability, as well.
A reasonably good comparison between the two can be found in the link below.
I had a Wallet/Exchange project, I have been developing both #Backend and #Frontend, Giving #REST API to mobile developers too. I decided to use Laravel for backend and build my #RESTfulAPI over that. So I used Laravel Passport for #JWT Authentication and host it over #cPanel hosting using Apache HTTP Server and using MySQL for database. Not the perfect choice but it worked perfectly as a starter for project. We used GitLab private repository for this project and we have been slightly unhappy because of several down-time we had over GitLab. All our team used Linux based system for developing project so we shared our bash scripts over the repo and saved lots of time.
I use Apache HTTP Server because it's the first http server I learned to use. Besides that being the main reason I use it, it's still the most used http server for a reason and that's because it works. I've never experienced any issues with Apache that weren't caused by any error besides my own. The only problem I have with it is the tedious setup for virthualhosts but, at Absolum this was our first open-source project to solve with Apache-VHC.