12 Reviews and Ratings
98 Reviews and Ratings
No answers on this topic
It is really helpful for managing [the] scaling of systems with need and utilizing resources when needed. Also, DevOps support for deployment plans is quite useful when deploying applications. Monitoring systems with graphQL and utilizing them in APIs is quite helpful when used in Microservices systems to identify system capabilities and user utilization of applications.Incentivized
As I mentioned earlier, the Apache HTTP Server has a small disadvantage compared to the competition (NGINX) in terms of performance. If you run websites that really have a lot of visitors, NGINX might be the better alternative. On the other hand, the Apache HTTP Server is open source and free. Further functionalities can be activated via modules. The documentation is really excellent.Incentivized
Graphically representation in GraphQLScaling systemDevOps managementIncentivized
Street Cred: Apache Web Server is the Founder for all of Apache Foundation's other projects. Without the Web Server, Apache Foundation would look very different. That being said, they have done a good job of maintaining the code base, and keeping a lot of what makes Apache so specialStability: Apache is rock-solid. While no software is perfect, Apache can parse your web sources quickly and cleanly.Flexibility: Need to startup your own Webpage? Done. Wordpress? Yup. REST Endpoint? Check. Honeypot? Absolutely.Incentivized
Quota enforcement can be simplifiedCaching mechanism for API with akamai can be improvedGateway configuration can be simplified as details are not much elaborateIncentivized
The default configurations which comes with Apache server needs to get optimized for performance and security with every new installation as these defaults are not recommended to push on the production environment directly.Security options and advanced configurations are not easy to set up and require an additional level of expertise.Admin frontend GUI could be improved to a great extent to match with other enterprise tools available to serve similar requirements.Incentivized
I give this rating because there is so much Apache documentation and information on the web that you can literally do anything. This has to do with the fact that there is a huge Open Source community that is beyond mature and perhaps one of the most helpful to be found. The only thing that should hold anyone back from anything is that they can not read. RTFM, my friend. And I must say that the manual is excellent.Incentivized
Akamai [API Gateway] helps better in terms of representation of graphQL and its consumption in monitoring system making a package for deployment speed with monitoring and scaling application with all services and utilizing most of a system without much knowledge of other aspects. Also, [a] user-friendly system helps people to handle [the] system with necessary optionsIncentivized
I has a lot more features, except that IIS is more integrated in a Windows environment. But now with .net core also possible from Apache it would work anywhere really. Only in a full Windows environment where full integration is needed I would chose to go for IIS. Otherwise Apache it is.Incentivized
Decrease in time required for deployment and monitoring by significant amount causing less support resources neededScaling applications on month-end at high usage time has reduced TAT time for issues and no of issues occurringQuota enforcement has allowed [managing] multiple systems and their needs in respective stakeholders hands and reduced infra teams involvement in [the] management of reoccurring problemsIncentivized
Works as intended, so it's less to worry about.Works great on elastic environments (like EC2).As an Open Source project, you can get support for almost any problem you can have.Configuration files, while powerful, can be tricky to dominate for some.Incentivized