Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: swoole and hyperf exist, what does this project aim to do #1145

Open
nikola-b opened this issue Dec 27, 2019 · 1 comment
Open

Comments

@nikola-b
Copy link

Hello, forgive my rudeness, but I've to ask this out of sheer curiosity. After trying this project out, reading what's on your website and being aware of tools such as swoole and hyperf, I must wonder - what problem does this project solve? It looks like it's entirely subpar to the two projects I linked, does it even make sense to continue pursuing it? It resembles Java's servlets, a backwards technology that introduced more issues than it helped.. am I missing something obvious here? Performance-wise, swoole and hyperf are about 50 times faster on the same workload as this project, so the catch-phrase that it's next-generation is entirely misleading. Is this a school project by any chance?

I didn't want to offend anyone, these are genuine questions I've got. I can tell a lot of work went into creating this project, but it looks like it's already outdated and not needed.

@wagnert
Copy link
Member

wagnert commented Dec 27, 2019

Hi, you're welcome to ask those questions, because they're comprehensible.

First, we've to say, that we actually do not have the necessary time to develop appserver.io up to the next level, e. g. a PHP 7.4 update or something like this. So sticking on PHP 5.6, it is outdated indeed.

As many of the documentation stuff around and about Swoole (and hyperf also seems to) seems to be written in Chinese language was and still are not able to read and understand it, although it will be cool stuff for sure. appserver.io kept the focus on writing everything that's possible in PHP and avoid using C which allows PHP developers to understand and extend it, starting from the HTTP Protocol and the webserver itself. Besides this approach, appserver.io comes with some - at least from our points of view - very useful services like a persistence container, a timer service and a message queue without the need to orchestrate a highly complex set of tools commonly used in PHP projects. So, as both will work, and for sure not appserver.io or Swoole will be the performance bottleneck in most cases, but the developer that writes the software, we think, the best solution for you and your project depends highly on how you want to develop software. If you like developing software in a node.js style, you'll be best settled with Swoole or hyperf, if you like developing software in Java style, you can go with appserver.io and will be fine :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants