Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MySQL for Developers

planetscale.com

Post reply on HN
Print view View original

81–90 of 119 posts

Re: MySQL for Developers

#81

Post by Aeolun »

SadWebDeveloper wrote: post #9
aarondf wrote: post #2

Hey HN, I made this course :D The course is a bit more than 7 hours long split over 64 videos. I was always frustrated by the lack of intermediate database content, it seemed like it was mostly intro stuff, or straight to DBA level. So I read as many database books as I could, read through the official docs, and made this course specifically for application developers. If yall have any feedback I'd love to hear it. I…

Quite difficult to review that many hours of video but from the syllabus there are probably some missing pieces, mainly stored procedures and triggers, yes i know MySQL sucks for that particular job and probably you didn't touch them because planetscale probably doesn't support them (not a planetscale dev but this is my wild guess). Also didn't see any topic on choosing the right charset/collation for the right data…

But then, most devs wouldn’t want their procedures inside the database anyway (with attendant lack of integration/versioning).

Re: MySQL for Developers

#82

Post by KronisLV »

hu3 wrote: post #77
KronisLV wrote: post #76

It's really nice to see more content for MySQL/MariaDB still being made, since it feels like they are still good solutions for a whole variety of situations! While I might look in the direction of PostgreSQL for more advanced in-database processing, for most CRUD apps the aforementioned two are going to be more than enough!

> While I might look in the direction of PostgreSQL for more advanced in-database processing, for most CRUD apps the aforementioned two are going to be more than enough I see this sentiment often here on HN. Something long the lines of "MySQL is enough for small apps but you want PotgreSQL for serious work." When in practice I find the opposite to be true. PotgreSQL is hard to scale and hard to upgrade when compared…

> What's PostgreSQL comparable list?

I'm sure that others can comment on that, but in my experience PL/pgSQL is the killer feature that's hard to beat in PostgreSQL, for those cases where you want to store some amount of logic in the database itself (MySQL stored procedures feel a bit more limited). That said, it's not even the only procedural language that is available: https://www.postgresql.org/docs/current/xplang.html

In addition, working with JSON in PostgreSQL can be pretty nice for niche use cases, as is using PostGIS for geospatial data, in addition to some of the REST (e.g. PostgREST) or GraphQL (e.g. PostGraphile) projects, if you want to interact with the database as something that exposes web endpoints to let you retrieve and manipulate data directly, as opposed to just SQL communication with some back end.

That's not to say that MySQL or MariaDB don't have their own great offerings, but it's clear that PostgreSQL has gotten a lot of love in regards to people developing various integrations and extensions. That said, usually not needing the equivalent of PgBouncer out of the box is nice and personally MySQL Workbench feels better than pgAdmin due to the advanced ER functionality (forwards/backwards engineering and schema synchronization, so that you can create versioned DB migrations more easily if you write them in plain SQL).

Edit: as for some crowd sourced data, a quick search turned up this from a few years ago: https://learnsql.com/blog/companies-that-use-postgresql-in-b...

But then again, all of the mentioned RDBMSes have proven themselves as viable for a variety of projects.

Re: MySQL for Developers

#83

Post by paulryanrogers »

AYBABTME wrote: post #79
KronisLV wrote: post #76

It's really nice to see more content for MySQL/MariaDB still being made, since it feels like they are still good solutions for a whole variety of situations! While I might look in the direction of PostgreSQL for more advanced in-database processing, for most CRUD apps the aforementioned two are going to be more than enough!

If by "advanced in-database processing" you mean stuff like PostGIS, then yes PostgreSQL is the right approach. But for most people building web-apps to scale, or established businesses who want to pick a solution and stick to it for basically ever, MySQL is much easier to scale. There's a ton of companies running MySQL at scale. I never heard of the same for Postgres, and for a long while I had an intellectual prefe…

MySQL also has had major bugs in recent GA releases like crashing your server when renaming a table.

PostgreSQL scales differently since it doesn't have redo-log based MVCC or other things as well. It does value correctness and has (mostly) better defaults. It has also had its own embarrassing bugs, though IME few put data integrity or availability at risk.

Re: MySQL for Developers

#84

Post by reactordev »

aarondf wrote: post #2

Hey HN, I made this course :D The course is a bit more than 7 hours long split over 64 videos. I was always frustrated by the lack of intermediate database content, it seemed like it was mostly intro stuff, or straight to DBA level. So I read as many database books as I could, read through the official docs, and made this course specifically for application developers. If yall have any feedback I'd love to hear it. I…

I’ve been using MySQL since 1998. I know the source code very well. I’ve designed large platforms with MySQL but I run postgres in production. I also wrote my own SQL engine.

This is very VERY well done. Kudos. I’m loving that we have a contender for mongo atlas with planetscale. Keep this kind of content coming and you’ll be the next snowflake.

Re: MySQL for Developers

#85

Post by samlambert »

mulmen wrote: post #80
hu3 wrote: post #77

Earlier quoted context omitted.

> While I might look in the direction of PostgreSQL for more advanced in-database processing, for most CRUD apps the aforementioned two are going to be more than enough I see this sentiment often here on HN. Something long the lines of "MySQL is enough for small apps but you want PotgreSQL for serious work." When in practice I find the opposite to be true. PotgreSQL is hard to scale and hard to upgrade when compared…

> What's PostgreSQL comparable list? Netflix, Instagram, Spotify, Skype, Reddit, Twitch, Yahoo. e: removed Uber.

Yahoo, Uber, Instagram, and Spotify all run on MySQL.

https://www.uber.com/en-JP/blog/postgres-to-mysql-migration/

Re: MySQL for Developers

#86

Post by hu3 »

mulmen wrote: post #80
hu3 wrote: post #77

Earlier quoted context omitted.

> While I might look in the direction of PostgreSQL for more advanced in-database processing, for most CRUD apps the aforementioned two are going to be more than enough I see this sentiment often here on HN. Something long the lines of "MySQL is enough for small apps but you want PotgreSQL for serious work." When in practice I find the opposite to be true. PotgreSQL is hard to scale and hard to upgrade when compared…

> What's PostgreSQL comparable list? Netflix, Instagram, Spotify, Skype, Reddit, Twitch, Yahoo. e: removed Uber.

Did Uber reverted back to PostgreSQL after switching to MySQL?

https://www.uber.com/en-US/blog/postgres-to-mysql-migration/

And as far as I know Netflix was a big Cassandra user then migrated to CockroachDB. I tried to search for "Netflix Postgresql" and found this comment from 2016 stating that they chose MySQL over PostgreSQL: https://news.ycombinator.com/item?id=11950811

Could you share a source?

Re: MySQL for Developers

#87

Post by mulmen »

hu3 wrote: post #86
mulmen wrote: post #80

Earlier quoted context omitted.

> What's PostgreSQL comparable list? Netflix, Instagram, Spotify, Skype, Reddit, Twitch, Yahoo. e: removed Uber.

Did Uber reverted back to PostgreSQL after switching to MySQL? https://www.uber.com/en-US/blog/postgres-to-mysql-migration/ And as far as I know Netflix was a big Cassandra user then migrated to CockroachDB. I tried to search for "Netflix Postgresql" and found this comment from 2016 stating that they chose MySQL over PostgreSQL: https://news.ycombinator.com/item?id=11950811 Could you share a source?

I just did a few quacks for "companies using postgresql". Tried to keep it to posts in the last couple years. Didn't look too closely.

Best source I found is https://www.thomsondata.com/customer-base/companies-that-use... but not sure how current it is.

Re: MySQL for Developers

#89

Post by ttfkam »

This is excellent. My only gripes have nothing to do with the execution of the training, only the terminology co-opted by MySQL.

In MySQL, "schema" means the structure of the whole database. In other RDBMSes, "schema" means a namespace within the database.

With its cross-database queries, MySQL puts no distinction between a database and a schema.

Once again, not a fault of the training here, but a common source of confusion I've run into between MySQL devs and folks working on other systems.

Re: MySQL for Developers

#90

Post by heybrendan »

Hi @aarondf, this is bloody phenomenal! Fantastic work.

Can we eventually expect something similar for PostgreSQL [for Developers]?

And does this course include ORM's, like SQLAlchemy?

Post reply on HN