Swoole VS Apache

Swoole

It's a management UI where concerns were raised that it downloads from third party server. However this issue was handled very fast and code was removed: https://github.com/swoole/swoole-src/issues/4434

The contribution log of the original swoole seems to be active: https://github.com/swoole/swoole-src/graphs/contributors

FOMO is created by Iranian developer amirfaramarzi. This framework sits on top of the asynchronous event driven framework swoole that creates insane levels of performance out of apps (we're talking Go/Rust level of performance)! Check out the performance on the Web Frameworks Benchmark.

> I tend to install FOSS because imo they are more "future-proof", but some of them are developed by companies (e.g., Fedora Linux) and that makes me wonder if they're truly future-proof.

The story of CentOS should be telling that, no, many pieces of software that are backed by a company will not be future-proof and will probably experience certain changes as a consequence of that, be it being transformed to better fit corporate goals (CentOS Stream), or being retired eventually so the company may focus on something else (Atom), or will just be left to slowly rot over time as happens with most code (OpenOffice).

Then again, it's not like open source projects are that future proof or safe from "drama" either - for example, the Lubuntu project has 2 homepages for no reason: the official one at https://lubuntu.me/ and some other one that serves old versions and is not trusted by my ad blocking solution https://lubuntu.net/

There are also cases, when open source projects experience fragmentation like happened with Gogs https://gogs.io/ and Gitea https://gitea.io/en-us/ and sometimes there are cases where particular individuals simply cannot work together and as a consequence pretty much the same happens, as was the case with Swoole and Open Swoole: https://github.com/swoole/swoole-src/issues/4434

Treat most pieces of software that you use as if they might not be there in a year.

It's known by devs, it's simple, it's getting updates... I like PHP. Sure it has downsides but what doesn't. Oh, and with Swoole, even performance is bumped.

To allow for synchronous execution and prioritize speed, we decided to depart from the task-based system that most of our workers use and instead create a new component to Appwrite called the executor. The executor would handle all orchestration and execution responsibilities and remove the Docker socket from the functions worker. The executor is an HTTP Server built with Swoole and Utopia using various Appwrite libraries to interact with the database.

Swoole will be shipping something really-really cool that is it's own CLI. You can checkout the development at https://github.com/swoole/swoole-cli and you can start playing with it using the pre-compiled binary distributed under Swoole's releases at https://github.com/swoole/swoole-src/releases/tag/v4.8.7.

It's been around for more then 8 years. Its a very established project with more the 17k stars https://github.com/swoole/swoole-src

Single-page applications (SPAs) existed before S3, but given that you still had to set up, scale, and maintain servers using something like Apache or NGINX in order to serve them, the advantages for “Ops” or “DevOps” were not so different to running a “real server” with a language like PHP, python, or Java.

Apache(prefork mode) + mod_php.

Simiplicity is nice, but there are reasons why Perl and PHP were the popular choices for web stacks in the early 2000's--they are faster and easier to develop with than C and likely safer than C too.

mod_perl (https://perl.apache.org/) and mod_php (https://cwiki.apache.org/confluence/plugins/servlet/mobile?c...) helped to make Apache httpd (https://httpd.apache.org/) the number one web server in the early days of the web.

https://httpd.apache.org/ - Apache2 website

The Apache HTTP Server project was initially launched in 1995 by a group of web developers and administrators who sought to improve upon the existing web server software available at the time. The project has since evolved into a collaborative effort, with contributors from around the world working together to maintain and enhance the server. Today, the Apache HTTP Server is managed by the Apache Software Foundation, a non-profit organization that oversees the development of numerous open source software projects.

Apache websites of friends and acquaintances

Apache: This is the web server that is used in the LAMP stack. Apache is an open-source web server that provides a flexible and scalable platform for hosting web applications.

Install the web server software: Download the appropriate version of Apache HTTP Server for your operating system from the official website (https://httpd.apache.org/). Follow the installation instructions provided in the documentation.

Popular web servers include Apache and Nginx. Apache is the most widely used web server on the internet, and it is known for its flexibility and extensibility. Nginx, on the other hand, is known for its speed and efficiency, and it is often used as a reverse proxy or load balancer.