tkyjonathan

Could there be an onsite version of this just for the use of setting up dev/test/staging databases?

I realize that its not the intend use, but this would solve a very real pain most technology companies have.

Bare in mind that SQL was designed to allow non-technical business users to use it. In most offices, a vetern business user or BI person will know how to use SQL. So SQL is a DSL for relational deconstructing of data models that is conceptually simple enough for people to grasp.

Templating can absolutely save time and boilerplate, but adding a DSL over a DSL in the form or ORM may well be the problem.

That is not the same graph that I have seen, sorry. And this study tells an opposite story. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3045642/

Red meat is down. Chicken however is dramatically higher.

Not sure how you made that classification so narrow with such a strange statement.

Maybe that tax can be used to fund that research or subsidise popular plant-based meats like Beyond Burger or Impossible Burger.

Insurance Giant to Doctors: Recommend Plant-Based Diet https://eatdrinkbetter.com/2013/08/24/insurance-giant-backs-...

I'm gonna go on a limb here, but I would say a great software engineer is someone that can block out email, slack, meetings, the huge noise of open offices and get some 'deep' work done.

on MySQL or any database that doesn't have it as a datatype, its 36 char on latin charset. If you leave everything as UTF-8, then its x3 that amount.

Try it for yourself.

So, you would rather have your primary keys be a 36 character UUID string instead of a 4-8 byte integer?

This is for every single row in your database and will increase the size of your database substantially.

System Administrators, largely gone.. Only around in old/large companies. DBAs, largely gone as well.. Its not that those skills are not needed at all, its just that 80% of them have been automated by the likes of AWS. Now those remaining 20% that have no one with the expertise to fix them. AWS will also start leeching away developer jobs with the Lambda marketplace. Why build your own backend code that consumes from an API when you can buy a lambda that pushes directly to your own DynamoDB or in a table to your RDS?

However, business users always knew SQL. SQL was designed for non-technical people. Thats why 2-3 years back, even google brought back SQL to its big data platforms. Even at my last job, some finance guys had no problem using it. Also, 'integration engineers' should have been 'data engineers' and while that is hot right now, people need to remember that its a solved problem as there have been ETL tools that do that for you for about 20 years (see informatica).

Absolutely disgusting. I hope the Animals Welfare Party and the Green Party might be able to do something about it.

I agree with the race to the bottom part.

Not knocking the DB. I use it myself. Just noticing a trend.

Lots of love for MariaDB in the comments here..

I am a bit disappointed at this article and the hierarchy of how to optimise postgres. As a MySQL specialist that has worked on a few Postgres projects, I can tell you that Postgres has a VERY RICH toolkit to speed things up. Between optimising queries and load balancing, you have indexing, partitioning.. (Postgres even allows you to index EACH partition differently) and triggers to do summary/rollup tables for you.

Its just that Postgres may need a little more coding and is less automatic than MySQL that people shy away from it..

I do like the time and information spent about spreading load accross database servers and not nearly enough people are considering splitting reads and writes from a master/slave setup.

Its just that its frustrating to me that engineers view databases as some sort of mysterious black box that you need to solve by working around it or replacing it entirely.

DBAs knew about this for many years now. We would simply change the schedular on the DB servers.

What about Postgres DBAs? I don't see too many of those around to allow Postgres to be picked up more....

Is there a similar script for Redshift?

He did not say that his database died. He said the "DB just kills it" as in, the query reached some sort of timeout.

I do this everyday for the past 10 years.. This is my bread and butter. http://www.jonathanlevin.co.uk

I think you are reading this wrong. Imaging you are a technical co-founder of a new start up... Someone is now telling you: 'you will not need to hire as many devops or DBAs if you buy this technology and you are also future proof, because we tune things for you and scale up your hardware without any effort from you.'

If the price is good (and considering you would not have to pay for salaries as well) you would be a fool not to take it.

I f the reason they want to distribute was performance then as a DB performance engineer, I can tell you first hand that tuning a database, indexing and caching can keep 99.9% of the internet companies very happy.

I know its hard to imagine, but it is true and most devops teams look to a shiny new tech they saw at a meet up than (like you said) fix 90s era technologies.

Yaniv, they just leapfrogged everyone back into the game with an obvious large investment of R&D. Who invests in R&D these days anyway?

Are you saying that this news article is anecdotal and incorrect about the actual situation? It seems to me that as a whole, the situation with adjunct teachers is quite bad..

I do this already... with a notebook and a pen.

I'm not against the idea of using postgres, but I have a sneaky suspicion, that you could have gotten that 30% speed benefit from MySQL, if you did some performance work on it. Or in other words, I don't feel that migrating from one relational database to another similar relational database was worth that much trouble.

Pretty cool

Take it from me (MySQL performance engineer).. if you are on AWS, the secret sauce is very tight data modelling. AWS is very unforgiving if you use it badly - on physical, you could have gotten away with a lot more. Some config tweaks will take you a bit further and smoothen those peaks, but data modelling(includes indexing, partitioning) is where you will get the most benefit.

Yeah, I really don't think we were made to outrun ostriches or any animal, really. Saying so set off a red light with me at the very start of the article. We can set traps and scavenge already dead bodies - thats pretty much it. Most of our actual calories were from plants/berries/corn/root vegetables. We were able to do very well for ourselves, calorically speaking, when we cooked/boiled those foods.