New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
When you develop your site/service what you will prefer to use: LAMP or MERN?
rustelekom
Member, Patron Provider
in General
I created my first site on Perl and Posgress in about 2000-2001 year. It was e-showcase with prices for over 1000ed computer components. Then i learned PHP and MySQL and use for next my sites LAMP. Then i switched to CMS because i leaved coding. But i could see that many web application now developed using MERN. So i guess some templates to simple run MERN on VPS/Dedi might be useful. What you think?
What would you prefer to develop a web application?
- Traditional LAMP using CMS or coding stacks like MERN?35 votes
- LAMP62.86%
- MERN11.43%
- Other (please describe more in comments)25.71%
Comments
linux (debian) + nginx +PHP + mariaDB + redis + wordpress
Ten minutes to build a website
LNPM
i develop my websites with PMS
I have nginx or apache 2 running in the front and reverse proxy to actual web app (mostly coded in Python) . Just personal stuff for fun so no problem so far.
alpine + caddy + php8 + typecho
Jamstack
I use whatever is suitable for the job.
Sometimes it's LAMP, sometimes it might be some BSD with nginx or whatever, sometimes it's MERN/MEAN/Jamstack or whatever the buzzword of the day is.
If you chose the same tools regardless of the task you are a fool.
Nginx, Debian, PHP 8. I try to avoid DBs where able. Company site is a basic CMS I wrote, no DB required.
Well... How do you even compare LEMP and MERN?
First is back/fullstack including OS, second is front/fullstack without OS.
For me its:
Linux + Nginx + PostgreSQL + .NET 5/C#
LNPN stack
PostgreSQL + ExpressJS + Vue + NodeJS
PEVN stack
I would rather say vue+.net+psql instead.
Stay with perl. You will be safe.
If i wrote AMP that would be less clean for understanding:) But you are right - correct question would be AMP or MERN or other stacks.
Actually, i just seen on some chat answer to post: "i code site on PHP" with lot of recommendation to topic starter forgot PHP and use MERN. Would not like begin holivare here, i interesting in modern trends.
Clean Code.
Is this the famous PHP+Mongo+SQL?
I've been using various stacks in my day jobs, but now primarily on Ruby/Rails+PgSQL+Tailwinds+Turbolinks(Or Vue)
My newer sites are using Preact + NDNts or RE:DOM + NDNts.
I don't use ExpressJS because it cannot properly support async functions.
In its place, I have Koa or Fastify, chosen randomly.
Data storage uses NDN repository, which is usually based on LevelDB.
Yeah, the push-ups are ultimately stored in the repository / database, not as files.
So the thing with current-day "stacks" is that MERN, Jamstack etc. are all basically marketing exercises (to hype up MongoDB and Netlify respectively, in these cases) rather than genuine sensible technical options. It's just companies trying to bank on the historical fame of LAMP to sell more services.
If you're going to be using Node.js, for starters, the whole concept of a 'stack' goes out of the window - "stacks" are a workaround for getting a set of known-compatible tools/dependencies that you can be assured will work together, and it's a result of rather lacking dependency ecosystems. The workaround makes sense in those ecosystems; you lose flexibility, but get to avoid dependency conflicts in exchange.
But JS doesn't have such a broken ecosystem - the JS ecosystem is highly interoperable, so you can basically just assume that any given two tools will work together, which eliminates the purpose of a pre-defined stack altogether; it's a workaround for a problem that JS simply doesn't have to begin with.
In other languages the situation is usually more nuanced, but the basic point isn't that different - a pre-defined "stack" is a very specific workaround for a very specific problem, not some fundamental law of programming, there is no such thing as a 'best' or 'perfect' stack because different projects have different requirements, and a hosting environment shouldn't be designed for one specific collection of tools and dependencies either.
(All this is leaving aside that MongoDB itself is terrible, and should realistically never actually be used for anything)
Supabase + SvelteKit + Tailwind or FastAPI + SvelteKit + Tailwind
Php 7.4 + lsphp(openlitespeed) + mariadb + redis/memcache + wordpress
and mariadb/mysqld eating cpu, all the time
WordPress unfortunately is not so "light" as it can be. Database usage is big enough.
right, even consume all the cpu, with redis database module/cache
MongoDB can rot in hell. I've heard horror stories of Mongo just discarding random documents during replication.
I prefer Flask for most tasks since with gevent its not all that bad performance wise for server-side rendered apps.
Writing APIs, I use Fastify + MySQL. GraphQL is a plague.
I don't know why so many people use Postgres, 99% of apps don't need the advanced features and the fork based connection model is not great.
Exactly my setup, do you think it's too soon to switch to PHP 8?
I heard good things about it.
When the server hardware is sufficient, I will prefer to use WAMP😆
MAMP on the Hetzner M1 Mac Minis