Things I wished more developers knew about databases

#1

Post by zdw » Wed, Apr 22, 2020, 4:45 AM UTC

Things I wished more developers knew about databases
medium.com

Re: Things I wished more developers knew about databases

#2

Post by Jaruzel » Wed, Apr 22, 2020, 1:31 PM UTC

Since when did Medium.com offer to log you in with your Google account like this?

http://www.jaruzel.com/files/medium-google.png

I've got uBlock and Cookie Cleaner running - but it's clearly doing some sort of cross-site shenanigans to create this pop up.

Time to stop visiting Medium.com I think.

Re: Things I wished more developers knew about databases

#3

Post by AtlasBarfed » Wed, Apr 22, 2020, 1:36 PM UTC

One thing I've noticed that in the medium term of a software service (2-5 years) is that your software should have the ability to do double-writes to and flip reads between two different datastores.

That will afford migration with as close to transparent migration with as reduced a downtime or no downtime.

Re: Things I wished more developers knew about databases

#4

Post by benatkin » Wed, Apr 22, 2020, 1:53 PM UTC

Jaruzel wrote: post #2

Since when did Medium.com offer to log you in with your Google account like this? http://www.jaruzel.com/files/medium-google.png I've got uBlock and Cookie Cleaner running - but it's clearly doing some sort of cross-site shenanigans to create this pop up. Time to stop visiting Medium.com I think.

Since a long time ago. This is old news. iFrame sandboxing is now a two-way street, depending on configuration. Not only can an iFrame be prevented from accessing the parent frame, a parent frame can be prevented from accessing the child frame. It is still vulnerable to clickjacking, but to reduce the impact of that, using one-tap sign up only allows the most basic Google permissions. https://news.ycombinator.com/item?id=17044518 https://developers.google.com/identity/one-tap/web

Re: Things I wished more developers knew about databases

#5

Post by delecti » Wed, Apr 22, 2020, 1:58 PM UTC

Jaruzel wrote: post #2

Since when did Medium.com offer to log you in with your Google account like this? http://www.jaruzel.com/files/medium-google.png I've got uBlock and Cookie Cleaner running - but it's clearly doing some sort of cross-site shenanigans to create this pop up. Time to stop visiting Medium.com I think.

I've been seeing that for ages, months at least, maybe years.

Re: Things I wished more developers knew about databases

#6

Post by [deleted] » Wed, Apr 22, 2020, 1:59 PM UTC

Jaruzel wrote: post #2

Since when did Medium.com offer to log you in with your Google account like this? http://www.jaruzel.com/files/medium-google.png I've got uBlock and Cookie Cleaner running - but it's clearly doing some sort of cross-site shenanigans to create this pop up. Time to stop visiting Medium.com I think.

[deleted]

Re: Things I wished more developers knew about databases

#7

Post by falcolas » Wed, Apr 22, 2020, 2:03 PM UTC

(The 80/20 rule applies below, some developers do care)

Developers... just don't care. They want to spin up an ORM, point it at a URI, and forget about it.

I've fought this for over a decade now as a DBA, SRE, DevOps, and architect. Most of the developers don't want to deal with anything infrastructure-wise; they want to spend all the time they can just focusing on the problem they're writing software to solve.

Observeability, reliability, scalability - these are all words that are translated into either "someone else's problem" or "unproductive busywork" in their minds.

Re: Things I wished more developers knew about databases

#8

Post by mattferderer » Wed, Apr 22, 2020, 2:05 PM UTC

> AUTOINCREMENT’ing can be harmful

I'll add that they should never be trusted to not jump around either! I imagine everyone makes this mistake at least once in their life.

There is a very high chance that the database will skip a few numbers from time to time. You will then have someone from an accounting department asking where Record #XX is.

Re: Things I wished more developers knew about databases

#9

Post by smitty1e » Wed, Apr 22, 2020, 2:06 PM UTC

AtlasBarfed wrote: post #3

One thing I've noticed that in the medium term of a software service (2-5 years) is that your software should have the ability to do double-writes to and flip reads between two different datastores. That will afford migration with as close to transparent migration with as reduced a downtime or no downtime.

That sort of flexibility does not sound as though it would scale well as the data get big.

Re: Things I wished more developers knew about databases

#10

Post by arvinsim » Wed, Apr 22, 2020, 2:13 PM UTC

falcolas wrote: post #7

(The 80/20 rule applies below, some developers do care) Developers... just don't care. They want to spin up an ORM, point it at a URI, and forget about it. I've fought this for over a decade now as a DBA, SRE, DevOps, and architect. Most of the developers don't want to deal with anything infrastructure-wise; they want to spend all the time they can just focusing on the problem they're writing software to solve. Obser…

Perhaps development work has reached complexity where it demands full-time attention?

Perhaps there is a reason why DBA, SRE, Devops and Architects are separate roles?