Submitted 22 hours ago by otto@programming.dev to technology@lemmy.world
https://optimizedbyotto.com/post/reasons-to-stop-using-mysql/
With few new features and heavy focus on code base cleanup and feature deprecation, it became obvious to many that Oracle had decided to just keep MySQL barely alive, and put all new relevant features (e.g. vector search) into Heatwave, Oracle’s closed-source and cloud-only service for MySQL customers.
In case anyone was wondering what is happening
Popularity != Good
I’m not sure I’m on board with this “fewer CVE’s reported means the product is more secure” logic in this article…
Does anyone start greenfield projects with normal mysql anymore? I know Meta internally whole infra relies on some mySQL + object store design pattern but I assume its so heavily modified from upstream atp. My company migrated everything we could to postgres awhile ago
sun_is_ra@sh.itjust.works 18 hours ago
It used to be LAMP (Linux - Apache - MySQL and PHP) that power the web.
Linux is the only thing still there.
Apache is losing ground to Nginx
MySQL is losing ground to Postgres
And PHP is ju losing ground to many new frameworks in different languages
felbane@lemmy.world 18 hours ago
Honestly, I’m fine with this outcome.
JasonDJ@lemmy.zip 15 hours ago
Is there something bad about nginx that I’m missing?
I prefer it for reverse proxy over apache…I’d just always found it to be much simpler.
But going forward I’m more likely to use caddy or traefik.
naticus@lemmy.world 14 hours ago
I wouldn’t say there’s anything bad about Nginx, but for a reverse proxy, Caddy just makes things so much easier since certificate issuance and management is the most frustrating thing about hosting web sites. At work, I pushed us to Caddy and we have 301 certificates running on it currently and it has zero issues with it. The other guys love how hands off it is too, especially now that I moved us to using Postgres for its storage.