News for hackers. Stuff that matters.
Re:HSBC moves from 65 relational databases into one global M... by sohamsankaran on Saturday June 13, 2020 @05:09AM (#23508026)
Jepsen's latest analysis of MongoDB -- https://jepsen.io/analyses/mongodb-4.2.6 -- finds that it doesn't even preserve snapshot isolation when set at the highest consistency level. This seems like a pretty terrible decision.

I've never wanted to short a company more in my life.

Re:HSBC moves from 65 relational databases into one global M... by rndgermandude on Saturday June 13, 2020 @06:04AM (#23508328)
Data loss is a good thing at HSBC, banker of the criminals and terrorists™️[1], for when the feds come knocking

[1] https://www.theguardian.com/business/2012/dec/11/hsbc-bank-u...

Re:HSBC moves from 65 relational databases into one global M... by tluyben2 on Saturday June 13, 2020 @07:10AM (#23508641)
2012 ... they are very strict now. Not saying it cannot happen but at least for normal people it's hard. They check far more than any other bank i'm with and compared to challenger it's almost a black comedy how much you need to fill out, prove, sign etc to open an account. At least in HK hometown. Disclaimer: I have an account there.
Re:HSBC moves from 65 relational databases into one global M... by rapsey on Saturday June 13, 2020 @09:40AM (#23509279)
Or it is all theatre.
Re:HSBC moves from 65 relational databases into one global M... by omginternets on Saturday June 13, 2020 @11:32AM (#23510130)
Please stop with the FUD. If you have a substantiated claim, please make it. Otherwise you’re not adding anything to the discussion.
Re:HSBC moves from 65 relational databases into one global M... by ric2b on Saturday June 13, 2020 @08:08PM (#23513969)
They've been caught laundering money many times over the years, what makes you think they finally changed?
Re:HSBC moves from 65 relational databases into one global M... by tluyben2 on Saturday June 13, 2020 @09:44AM (#23509304)
Like I said, could be, but if I wanted to do something not entirely on the up-and-up, I would just open a challenger/neo-bank account in 5 minutes from my home and do it in there. Not somewhere where they have proof of everything I have and do which I need to refresh every year.
Re:HSBC moves from 65 relational databases into one global M... by omginternets on Saturday June 13, 2020 @11:32AM (#23510125)
That’s a stretch. Carefully-controlled deletion with plausible deniability is a good thing.

Uncontrolled data loss is most assuredly not.

Re:HSBC moves from 65 relational databases into one global M... by mpweiher on Saturday June 13, 2020 @07:00AM (#23508593)
MongoDB: The best DLAAS solution money can launder. (Data Loss as a Service™)
Re:HSBC moves from 65 relational databases into one global M... by ncmncm on Saturday June 13, 2020 @07:01AM (#23508602)
Is HSBC still the bank favored by the CIA for its money laundering needs? I had read that for an FBI agent to look into HSBC was a "career-limiting move", but that was 10 years ago. Maybe CIA have moved to another by now?
Re:HSBC moves from 65 relational databases into one global M... by rumanator on Saturday June 13, 2020 @08:25AM (#23508904)
> I had read that for an FBI agent to look into HSBC was a "career-limiting move"

Do you have any source that substantiates your assertion?

Re:HSBC moves from 65 relational databases into one global M... by HenryBemis on Saturday June 13, 2020 @08:46AM (#23508994)
I was daydreaming earlier on how these mega-big banks can get away with everything (HSBC, Barclays, DB, MS, BAML, etc. etc.) and how nice would it be if all these super complex scheming products that are leverage upon leverage upon leverage would disappear tomorrow..

These mega-big banks and their practices, ranging from LIBOR manipulation, scamming retail banking practices, scamming their own IB/FX customers..). And they get away with it.

As much as I dislike religion (I love the notion of Faith, but I dislike the self-identified 'representatives of gods'), I believe that the most ethical type of Banking is the Islamic Banking (again, not about the religion)(gods that give cancer to little kids to "test their faith" are not my type of gods).

Re:HSBC moves from 65 relational databases into one global M... by downerending on Saturday June 13, 2020 @06:17AM (#23508386)
I got a credit card with them a few years back and immediately regretted it. Their tech (website, security, etc) seems okay at first glance, but almost immediately it turned into agony. Even just logging in is a chore, and often doesn't work. Their two-factor implementation is a mess.

In short order, I cut the card up. Still get sad emails (which they provide no way to stop) begging me to use it.

Also, interviewed at MongoDB once. Couldn't shake the feeling of a cult, where everyone was careful not to speak of the product's serious limitations.

Re:HSBC moves from 65 relational databases into one global M... by drevil-v2 on Saturday June 13, 2020 @06:27AM (#23508429)
Haha I feel this. Did you also have the credit card sized token generator with a keypad? How convoluted was that login process? Agony is the correct term!!
Re:HSBC moves from 65 relational databases into one global M... by jen20 on Saturday June 13, 2020 @10:27AM (#23509571)
I had forgotten about this but the dumb 2FA generator is the reason I switched away from HSBC for Citibank (UK) many years ago!
Re:HSBC moves from 65 relational databases into one global M... by amaccuish on Saturday June 13, 2020 @01:18PM (#23510962)
> Even just logging in is a chore, and often doesn't work. Their two-factor implementation is a mess.

My parents switched from Lloyds (UK) to HSBC and are looking to switch again.

You can't have multiple devices logged in. I.e. you can log in just fine on your "security key" device (say a phone), but if you want to login on your iPad to check something, you have to get a code from the app on your phone. Absolutely pointless.

Re:HSBC moves from 65 relational databases into one global M... by quickthrowman on Saturday June 13, 2020 @11:51AM (#23510270)
I also have an HSBC credit card. I am unable to pay my card balance on the app, I have to log in to the website and get redirected to a separate web app to make payments on it. I’m keeping the account open and paying a single monthly recurring bill so I only have to do this once a month. All my other credit card balances can be paid down through their corresponding app.
Re:HSBC moves from 65 relational databases into one global M... by davchana on Saturday June 13, 2020 @03:36PM (#23512054)
Do they offer auto pay?
Re:HSBC moves from 65 relational databases into one global M... by ddalex on Saturday June 13, 2020 @10:45AM (#23509739)
I dunno. I am banking with them (also other banks) and they are pretty good - most of the other banks face similar problems around the same areas, which I ascribe to very strict regulation.
Re:HSBC moves from 65 relational databases into one global M... by mathattack on Saturday June 13, 2020 @09:51AM (#23509348)
Sounds like a marriage made in heaven between these two.
Re:HSBC moves from 65 relational databases into one global M... by ansible on Saturday June 13, 2020 @10:51AM (#23509780)
Cutting up the credit card is good, but you may want to officially close the account.
Re:HSBC moves from 65 relational databases into one global M... by downerending on Saturday June 13, 2020 @01:04PM (#23510842)
Considered it, though by the strange rules of the US credit system, it would harm my credit score to do so.
Re:HSBC moves from 65 relational databases into one global M... by whack on Saturday June 13, 2020 @07:28AM (#23508700)
Shorting a banking company because they chose to use MongoDB... you can tell that an engineer wrote this comment. You're missing the forest for one particular tree.
Re:HSBC moves from 65 relational databases into one global M... by joaomacp on Saturday June 13, 2020 @12:20PM (#23510498)
I thought the parent was talking about shorting MongoDB ("MDB" NASDAQ ticker)
Re:HSBC moves from 65 relational databases into one global M... by bdcravens on Saturday June 13, 2020 @12:08PM (#23510407)
I agree, though decisions made is isolation can give some peeks into company culture. After all, forests often have many of the same kinds of trees.
Re:HSBC moves from 65 relational databases into one global M... by DonHopkins on Saturday June 13, 2020 @02:30PM (#23511510)
And some forests have a few carefully arranged trees of a different type.

https://en.wikipedia.org/wiki/Forest_swastika

Re:HSBC moves from 65 relational databases into one global M... by isatty on Saturday June 13, 2020 @07:53AM (#23508779)
Eh it sounds snarky but not a bad idea because the downtime seems inevitable when using MongoDB.

I'm not informed enough to know if it'll affect the share price for a bank but if a tech company did onboard mongo that'd be a major red flag for me.

Re:HSBC moves from 65 relational databases into one global M... by mushi on Saturday June 13, 2020 @11:23AM (#23510060)
Why expected down time for dB that has built in replication?

I would expect downtime from RDBMSS and most banks have scheduled downtime nearly every weekend they say when I log in.

Re:HSBC moves from 65 relational databases into one global M... by reitanqild on Saturday June 13, 2020 @11:21AM (#23510053)
Yep, also we always remember the markets can stay irrational longer than we can stay solvent or something to that effect.
Re:HSBC moves from 65 relational databases into one global M... by blablabla123 on Saturday June 13, 2020 @06:21AM (#23508399)
Transactions in bank accounts are actually not realized through DB transactions. It's easily visible if you ever had a failing payment: the amount gets subtracted but added again right away after that. They have pretty strong auditing requirements.
Re:HSBC moves from 65 relational databases into one global M... by brainless on Saturday June 13, 2020 @07:01AM (#23508601)
What has "amount gets subtracted but added again right away after that" have to do that with DB transactions?

Basically each Banking transaction is an immutable log, which can easily reside in a DB with DB transactions feature. They are not related.

Can you please elaborate in technical terms what you mean?

Re:HSBC moves from 65 relational databases into one global M... by willcipriano on Saturday June 13, 2020 @08:20AM (#23508883)
Not the OP but I think it's essentially a event driven system as opposed to real time.

Think of a account with $0 in it.

1. A -$25 event comes in

2. A +$50 event comes in

3. A -$25 event comes in

The first event would fail in a transactional/real time system, but in my bank it doesn't. This tells me the balance is only calculated every once in a while. The balance you get in a app is only a estimate.

This makes sense when you think how slow bank transfers and using paper checks is. At some point it is decided to run the events "for real" and that's where overdrafts and the like are applied.

Don't think of them as transactions, instead it's a transaction request that can be rejected.

Re:HSBC moves from 65 relational databases into one global M... by lscharen on Saturday June 13, 2020 @09:10AM (#23509122)
Related to this — Wells Fargo was sued[1] (and lost) around 2010 for the practice of ordering daily transaction to (indirectly) maximize fees and penalties.

In your example, a “good” bank would order the transactions: +$50, -$25, -$25 resulting in a zero balance with no penalties. What Wells Fargo did could result in the transactions being ordered as: -$25 (overdraft), -$25 (overdraft), +$50.

Each overdraft could charge a fee up to $35, leaving the account holder with a -$70 balance.

[1] https://www.latimes.com/nation/la-fi-court-bank-overdraft-fe...

Re:HSBC moves from 65 relational databases into one global M... by alexchamberlain on Saturday June 13, 2020 @12:05PM (#23510389)
Seems much simpler only to charge fees at the end of the day...
Re:HSBC moves from 65 relational databases into one global M... by eqvinox on Saturday June 13, 2020 @01:06PM (#23510860)
Unfortunately, the optimization goal for commercial entities generally is maximum money extraction, not simplicity :)
Re:HSBC moves from 65 relational databases into one global M... by kenniskrag on Saturday June 13, 2020 @10:09AM (#23509442)
It depends on the country and currency but there is the SWIFT system, which works like messaging. There is also the SIC and EuroSIC. For SWIFT system as a bank you have an account on the other bank and sends an instruction to decrease your amount and book it to a receiver. If there are more than one bank between them it gets routed but always "own decrease and other bank increase". Only the receiver bank books to the client. This system works because every bank has an account on other banks and you can build up some paths.
Re:HSBC moves from 65 relational databases into one global M... by bouncycastle on Saturday June 13, 2020 @08:47AM (#23508997)
Sure, it just means that the processing is done in a batch job at the end of the day. However, it doesn't mean that the batch jobs don't use a database. There's probably something like db2 on the mainframe, possibly even COBOL or RPG
Re:HSBC moves from 65 relational databases into one global M... by sohamsankaran on Saturday June 13, 2020 @08:58AM (#23509053)
Yep, it's pretty clear they use IBM db2 on z/OS internally for some applications. Here's an example job posting: https://webcache.googleusercontent.com/search?q=cache:Aqb9oU...
Re:HSBC moves from 65 relational databases into one global M... by tigershark on Saturday June 13, 2020 @09:14AM (#23509145)
How slow bank transfers are? Is 2 seconds really that slow?
Re:HSBC moves from 65 relational databases into one global M... by willcipriano on Saturday June 13, 2020 @09:30AM (#23509220)
In the US they clear overnight, as I understand (from a previous hn post I can no longer find) it's a big sftp server and flat files.
Re:HSBC moves from 65 relational databases into one global M... by nobleach on Saturday June 13, 2020 @10:22AM (#23509528)
Working in the fintech has opened my eyes to how many shortcomings there really are in banking/ACH. What you describe above is both my nightmare, and my reality. Pipe-delimited flat files being SFTPed via cronjobs overnight. Getting the emails at 5am that balances are off/not reconciled because somehow an errant '|' got into the mix.

Additionally, the number of folks that ask for spreadsheets (not encrypted) with your SSN... and then proceed to email that data around (sometimes via Gmail!)

Re:HSBC moves from 65 relational databases into one global M... by tigershark on Saturday June 13, 2020 @01:18PM (#23510963)
The article is about HSBC, a British bank, where the transfers happen in a matter of seconds. What is the point of comparing it with US banks?
Re:HSBC moves from 65 relational databases into one global M... by attilakun on Saturday June 13, 2020 @09:18AM (#23509162)
I could be wrong but I think the following scenario is worth considering. Let's say a client wants to transact money from bank A to bank B. The following steps are taken:

1. Client initiates the transfer request.

2. Bank A decreases the client's balance.

3. Bank A sends the request to transfer money to bank B.

Now, I guess you would expect that steps 2 and 3 should form part of a DB transaction. This however does not really work because it is unclear what conclusion we should draw from step 3 failing. On one hand, it is possible that the request failed on its way to bank B, in which case step 2 should not be applied. On the other hand, it is possible that the request successfully reached bank B but the response got lost on its way back. In this case step 2 should be applied.

Therefore, not treating steps 2 and 3 as a single transaction makes sense if you want to take a conservative approach that does not allow for accidental transfer of infinite amounts of money to bank B in scenarios when the response fails to come back from an otherwise successful transfer.

Re:HSBC moves from 65 relational databases into one global M... by samus on Sunday June 14, 2020 @06:31AM (#23516566)
We have exactly the same problem at work. One possible way to solve it is by ensuring that the receiving system treats the request as idempotent. One could also poll first at the receiver whether the transaction exists, and then send it if it doesn't. But both measures require that there is a way to uniquely identify a request. Also, idempotency can be annoying to implement correctly. Thus, implementors might try to wiggle their way out of it, technically or politically.
Re:HSBC moves from 65 relational databases into one global M... by nurettin on Saturday June 13, 2020 @06:37AM (#23508486)
This is the only comment worth a thing here. Unless mongodb causes irrevocable data loss, eventual consistency is easily mitigated using an accounting service. I have seen one of them at work. Transaction amount comes in, it is compared with initial value and the session is kept open until the quantity is fulfilled. If there is a timeout, secondary systems try to recover or alert. Recovery can even deduct overfills or complete fills.
Re:HSBC moves from 65 relational databases into one global M... by zo1 on Saturday June 13, 2020 @07:44AM (#23508754)
This seems ridiculously complicated and unnecessary for something that should be as easy as having a proper RDMS that is ACID compliant. I guess now we have one additional reason why banking has stagnated for so long.
Re:HSBC moves from 65 relational databases into one global M... by kilburn on Saturday June 13, 2020 @08:37AM (#23508962)
Just in case you (or someone else) don't know why you are being downvoted, I'll give you a few reasons:

- Banks have to put these double-checking and reporting systems in place because the law mandates them to. No amount of ACID compliance in your database is freeing you from that.

- These requirements are not stupid either: assuming you had a perfect system with perfect ACID compliance and 0 bugs ever (which we all know is impossible), a random hardware failure (or cosmic ray) can flip a bit somewhere and you are screwed.

- Your comment reads as extremely condescending, which is never good to get your point across.

- Not only that, but you dismissed the work of some of the best people money can buy in two sentences with 0 rationale. Next time you think you know better than an entire extremely well funded industry, think again, and again, and again. If you are still convinced you know better, please open shop because if you are right you'll not just make yourself the next self-made billionaire, but also probably improve our lives in the process.

Re:HSBC moves from 65 relational databases into one global M... by matt_d_rat on Sunday June 14, 2020 @08:25PM (#23522659)
This comment gives me hope that there are at least some decent people on Hacker News.

Every time I read an article here I am put off from participating further because the comments are usually filled with toxic spew from peacock fan boys Who think they know better.

You have my up vote.

Re:HSBC moves from 65 relational databases into one global M... by nurettin on Saturday June 13, 2020 @08:29AM (#23508926)
It is complicated, but necessary. You will get to the ridiculous part once you realize that executing brokers don't care about your acid guarantees or whatever.
Re:HSBC moves from 65 relational databases into one global M... by zo1 on Saturday June 13, 2020 @09:09AM (#23509115)
Thanks for the info - I didn't realize we were discussing distributed transactions with external brokers/banks.
Re:HSBC moves from 65 relational databases into one global M... by KptMarchewa on Saturday June 13, 2020 @01:37PM (#23511108)
Banking is integrations with literally hundreds different external systems.
Re:HSBC moves from 65 relational databases into one global M... by DonHopkins on Saturday June 13, 2020 @02:40PM (#23511599)
Are we discussing HSBC bankers or Silk Road LSD dealers?
Re:HSBC moves from 65 relational databases into one global M... by nurettin on Sunday June 14, 2020 @06:50PM (#23522081)
I suspect ACID doesn't help either of them.
Re:HSBC moves from 65 relational databases into one global M... by lowwave on Saturday June 13, 2020 @05:13AM (#23508042)
Seems like the guys at HSBC tech department are still doing the whole fashion over merit.
Re:HSBC moves from 65 relational databases into one global M... by sohamsankaran on Saturday June 13, 2020 @05:15AM (#23508052)
What's wild about this is that Mongo isn't even in fashion anymore! NoSQL has been supplanted by NewSQL, and relational dbs are in season again. Even if they were trying to follow the trend, they'd be a half-decade behind.
Re:HSBC moves from 65 relational databases into one global M... by pydry on Saturday June 13, 2020 @06:45AM (#23508517)
I work at another big corp in London and mongo has been doing a major sales push on us in the last 18 months (which wasn't pleasant to push back on).

I'm fairly sure that this was driven by a similar sales push.

Mongo has always been a sales and marketing company first and technology company second.

I'd love to see a tear down of their sales and marketing strategy coz its clearly top notch.

Re:HSBC moves from 65 relational databases into one global M... by mathattack on Saturday June 13, 2020 @09:54AM (#23509364)
The strategy is called “Lie, Overwhelm, and Raise Rates on Renewal”
Re:HSBC moves from 65 relational databases into one global M... by rgoulter on Saturday June 13, 2020 @07:36AM (#23508720)
I've never heard the term "NewSQL" before.

Google Trends comparing "NewSQL" with "NoSQL" https://trends.google.com/trends/explore?date=all&geo=US&q=N... (Peaking with its introduction in 2011).

It doesn't seem like a more fashionable term than NoSQL.

Re:HSBC moves from 65 relational databases into one global M... by catmanjan on Saturday June 13, 2020 @05:33AM (#23508161)
Interesting, what is considered newsql? Postgres?
Re:HSBC moves from 65 relational databases into one global M... by sohamsankaran on Saturday June 13, 2020 @05:44AM (#23508227)
I am not a fan of this buzzword (and indeed buzzwords in general, the comment above was intending to make fun of HSBC IT for even failing at the buzzword game), but the notion of NewSQL was roughly to keep the relational model and consistency guarantees of traditional SQL databases, but also have horizontal scalability in line with NoSQL databases. DBs like VoltDB and Spanner come to mind as examples -- here are two relevant blog posts from those teams:

VoltDB: https://www.voltdb.com/blog/2016/09/nosql-vs-newsql-whats-di...

Spanner: https://cloud.google.com/blog/products/gcp/from-nosql-to-new...

Re:HSBC moves from 65 relational databases into one global M... by AsyncAwait on Saturday June 13, 2020 @06:16AM (#23508379)
No."Horizontally-scalable" SQL like CockroachDB, TiDB, Google's Spanner or YugabyteDB are examples of NewSQL, Postgres would be "OldSQL" if you will.
Re:HSBC moves from 65 relational databases into one global M... by jtms on Saturday June 13, 2020 @09:24AM (#23509192)
PostgreSQL still the best sql though :-)
Re:HSBC moves from 65 relational databases into one global M... by bob1029 on Saturday June 13, 2020 @05:40AM (#23508201)
SQLite is the hottest new thing on the block.
Re:HSBC moves from 65 relational databases into one global M... by mkl on Saturday June 13, 2020 @05:43AM (#23508221)
Huh? SQLite is nearly 20 years old, and is only intended for small scale use.
Re:HSBC moves from 65 relational databases into one global M... by bob1029 on Saturday June 13, 2020 @06:06AM (#23508335)
It was intended as a joke in context, but I believe SQLite is far more capable than most will give it credit for. This is especially true for applications which you only ever intend to run on a single logical machine. But, even for those applications requiring multiple nodes, it can still be a powerful tool if you assume clustering & replication duty in your application logic.

For any use case, SQLite is one of the best ways to persist structured data to local disk.

Re:HSBC moves from 65 relational databases into one global M... by waheoo on Saturday June 13, 2020 @08:06AM (#23508831)
I try to use sqlite for all projects until i cant.

Its a little scary how much it can actually handle, and how lazy and sub optimal it is to reach for a "real" sql server before you need it.

Having the database as a simple file right next to yoyr application is incredibly convenient not to mention how brain dead things like backups are to grok.

Re:HSBC moves from 65 relational databases into one global M... by sohamsankaran on Saturday June 13, 2020 @06:29AM (#23508445)
SQLite is incredible, especially for embedded applications. It's one of those perfectly-scoped tiny pieces of software that consistently makes my heart sing.
Re:HSBC moves from 65 relational databases into one global M... by mkl on Saturday June 13, 2020 @06:13AM (#23508364)
Oh, I agree about its utility, and use it myself. It seems like a different category of tool than the other DBs under discussion, though.
Re:HSBC moves from 65 relational databases into one global M... by geoah on Saturday June 13, 2020 @06:01AM (#23508308)
Tidb, cockroachdb maybe?
Re:HSBC moves from 65 relational databases into one global M... by oneplane on Saturday June 13, 2020 @12:59PM (#23510800)
While that is true, shoving that logic in to the database itself tends to indicate an anti pattern in the software that uses the database.

It used to be lots of fun and highly optimal to write all sorts of procedures and triggers because it was the only fast and reliable way to do things, especially when your in-database-code was essential the only gatekeeper against a multiple owner database schema.

The idea that you have one database schema that you are going to share with different applications seems bonkers to me at this point in time. Compute and storage resources are far cheaper than development, DBA and potential stagnation that a schema that doesn't have a single owner brings.

Re:HSBC moves from 65 relational databases into one global M... by murukesh_s on Saturday June 13, 2020 @05:22AM (#23508095)
From the article, it looks like they are replacing separate DBs used for each country.

"Local requirements for each country will be built into the application, but there's no need to maintain separate data models or separate databases anymore. We could easily design the global data model and database using the MongoDB JSON schema model. That brings data from all operating countries into one database and the application can run on just one database. Which is a lot of reduction in resource and maintenance cost. "

Are there any other schema-less databases out there that is better than MongoDB? If not I believe it's time for someone to build it.

Re:HSBC moves from 65 relational databases into one global M... by kogepathic on Saturday June 13, 2020 @05:40AM (#23508208)
> Are there any other schema-less databases out there that is better than MongoDB? If not I believe it's time for someone to build it.

Yes, PostgreSQL supports JSON and won't lose your data: https://www.postgresql.org/docs/current/datatype-json.html

Benchmarks:

* https://portavita.github.io/2018-10-31-blog_A_JSON_use_case_...

* https://www.postgresql.eu/events/fosdem2018/sessions/session...

Re:HSBC moves from 65 relational databases into one global M... by murukesh_s on Saturday June 13, 2020 @06:15AM (#23508373)
From the second link, summary:

Summary - PostgreSQL ● PostgreSQL has poor performance out of the box ○ Requires a decent amount of tuning to get good performance out of it ● Does not scale well with large number of connections ○ pgBouncer is a must ● Combines ACID compliance with schemaless JSON ● Queries not really intuitive

Summary - MongoDB ● MongoDB has decent performance out of the box. ● Unstable throughput and latency ● Scale well with large number of connections ● Strong horizontal scalability ● Throughput bug is annoying ● MongoDB rolling upgrades are ridiculously easy ● Developer friendly - easy to use!

Re:HSBC moves from 65 relational databases into one global M... by riku_iki on Saturday June 13, 2020 @11:39AM (#23510180)
> PostgreSQL has poor performance out of the box

This is actually a valid point. They should start distributing typical configs for typical AWS-alike machines, current default config is for some underpowered machine from 90s..

Re:HSBC moves from 65 relational databases into one global M... by isatty on Saturday June 13, 2020 @07:59AM (#23508806)
> Queries not really intuitive

ISHYGDDT

Re:HSBC moves from 65 relational databases into one global M... by sinni800 on Saturday June 13, 2020 @10:04AM (#23509411)
I would argue that MongoDB queries aren't intuitive but I've known SQL for at least 10 years
Re:HSBC moves from 65 relational databases into one global M... by willcipriano on Saturday June 13, 2020 @11:19AM (#23510029)
For MongoDB in Python I once had to construct a list of two dictionaries containing dictionaries themselves with various two and three character magical key and value names (eg. $gt) in order to query a collection by date. If that's intuitive I'd hate to use something unintuitive.

Oh and MongoDB Compass is a dumpster fire. Query takes too long? Too bad it will time out with no option to let it complete. Also I get to write my query in JSON in compass then I have to convert that to native Python objects if I want to use it from there. With SQL I copy my query from datagrip, inject my parameters and call it a day.

I forgot the best bit, if your query has a subtitle mistake most often you simply get no records back where a similar mistake in SQL throws a helpful exception.

Re:HSBC moves from 65 relational databases into one global M... by john_ghandi on Sunday June 14, 2020 @02:39PM (#23520085)
really? best of luck with that. single node, and no faiures - and it still messed its pants: http://jepsen.io/analyses/postgresql-12.3
Re:HSBC moves from 65 relational databases into one global M... by mathattack on Saturday June 13, 2020 @09:54AM (#23509367)
MSFT is trying with Cosmos.
Re:HSBC moves from 65 relational databases into one global M... by sdinsn on Saturday June 13, 2020 @10:18PM (#23514588)
And the question you should ask is, does HSBC actually need to preserve snapshot isolation when set at the highest consistency level? If the answer is no, then your comment is irrelevant.
Re:HSBC moves from 65 relational databases into one global M... by mathattack on Saturday June 13, 2020 @09:50AM (#23509339)
Based on the headline I thought the same. And just wait until the shady audit and renewal practices begin. In reality the total cost may be small for a bank that big. But messing even one trade or large account can cost them billions.
Re:HSBC moves from 65 relational databases into one global M... by john_ghandi on Sunday June 14, 2020 @02:35PM (#23520040)
or you could just use postgres to corrupt your data. latest jepsen analysis http://jepsen.io/analyses/postgresql-12.3
Re:HSBC moves from 65 relational databases into one global M... by joncrane on Saturday June 13, 2020 @10:48AM (#23509758)
Have you ever heard of Muddy Waters? The famous stock shorter?
Re:HSBC moves from 65 relational databases into one global M... by Thaxll on Saturday June 13, 2020 @10:36AM (#23509657)
There are Jepsen report and people that know how to read them right? Fortnite runs on MongoDB thay have 130M players worlwide and do $B a year without issues using it, so you think it was a mistake for them?
Re:HSBC moves from 65 relational databases into one global M... by teej on Saturday June 13, 2020 @10:45AM (#23509742)
“X uses Y therefore Y is good” in general is a terrible argument. But also, Fortnite is a game. It’s for fun. 99% of their read/write throughput is in the context of a match, and matches are ephemeral.
Re:HSBC moves from 65 relational databases into one global M... by sdinsn on Saturday June 13, 2020 @10:17PM (#23514580)
> “X uses Y therefore Y is good” in general is a terrible argument

Which is not his argument. His argument is "X uses Y, and X doesn't have problems with Y, so Y is good enough for X at least". Which is a completely valid thing to say.