Disclaimer: I work at Nubank, nice to see it posted here. This video is now one year old and it's nice to see how the technology choices at the start are still paying dividends.
Datomic in particular is a pretty smart product backed by solid concepts (RDFs/triplestores, event sourcing, immutability, querying engine on the client side, datalog), something companies end up re-inventing in-house further down the line, so it's nice to be aware of the architecture even if not intending to use it.
I'm brazilian and have been working with Clojure for a few years and used Datomic on a project earlier this year. Are you planning on hiring? Sorry for the thread hijack.
"Datomic’s support for multiple storage backends has also been useful to
Nubank, as personally identifying information (PII) must be encrypted at
rest, something that is easily achieved using Amazon’s PostgreSQL (RDS)
with EBS volume encryption for some services, while using DynamoDB
to back other, non-PII services."
Been using NuBank for about 8 months and I must say, it is the best bank experience I've ever had. They put great effort into every aspect of their business. From the mobile app to the customer experience, it's perfect!
(Now that I've promoted you please raise my limit amount - haha jk)
* Isn't reinventing the engineering wheel; in terms of Datomic and a not popular language like Clojure a potential huge distraction to the ultimate goal of building a bank? The problem space is big and hard enough without rolling/maintaining/testing your own database engine and obscure language framework.
* Perhaps surprising, but Brazil is an interesting market. We have a connected young generation and most industries' current players are bad.
* I would argue it's about avoiding reinventing the wheel. Datomic gives you easy scale-out and auditing, and Clojure gives you a flexible, pragmatic functional language with good async/threading primitives running on stablished platforms (JVM and web browsers). I guess going off the beaten path is not necessarily more work if you're taking a shortcut.
I'm not aware of any, although I'm not sure Datomic qualifies as a traditional DBMS. It's more like a querying API + a master process (transactor) backed by a traditional store/DB (Postgres, Dynamo, etc), so you can achieve the same by putting some existing solutions together, but it's implementing a bit more than a DBMS alone.
Datomic in particular is a pretty smart product backed by solid concepts (RDFs/triplestores, event sourcing, immutability, querying engine on the client side, datalog), something companies end up re-inventing in-house further down the line, so it's nice to be aware of the architecture even if not intending to use it.