4 ms·
> Increasingly, you can swap out Oracle with Postgres. Well, there is also a huge decrease of DB competencies around (myself first, not shifting the blame on a
by mk89 4y ago
> Increasingly, you can swap out Oracle with Postgres.
Well, there is also a huge decrease of DB competencies around (myself first, not shifting the blame on anyone). So, now finally all you need is "just a db", DBAs are gone. Most people don't even need non-relational DBs but hey that's cool. Don't get me started :) I wouldn't blame it on the software (oracle) itself but on the fact that with microservices (and managed DBs) the role of a specific DB seems to have decreased significantly.
- to11mtm 4y agoI'd say the 'increasingly' isn't simply because of the loss of DB competency. I worked at a shop that for years was an 'always oracle' even though every license renewal visit left management paranoid and dejected, that got won over by the level of similarity between the two. MSSQL doesn't mesh well with oracle because it isn't MVCC by default, so risk of conversion goes WAY up. MySQL, well it was(is?) missing a number of other features alongside a touchy datatype model and other warts in people's memory. PG tends to do well at picking the right features from other DBs, and you just pay a quote tax to enjoy the benefits. > the fact that with microservices (and managed DBs) the role of a specific DB seems to have decreased significantly. I do think this is the third point in the trident. In some shops (I've yet to see one!) you can get a database per-microservice. More frequently I see 'database-per-ecosystem' which means your microservices share a DB.