Building a bank from scratch in the Cloud - Hans Kristian Flaatten

We are building the next generation mobile bank in the cloud from scratch! This is how we build Bulder Bank from the ground up.
Early on it was decided that we had to be open for radical new ideas if we was to succeed. Important kriterias was speed, modern and automated processes and future-proofing. In addition we wanted to make something that was cool and motivated everyone on the team to work on.
The choice landed on Google Kubernetes Engine and Google Firebase and the possibilities this gives us are literally endless! And it gives us the opportunity to move fast while having a more or less fully managed environment that is always up and running!
We have decided to model payments entirely event based and asynchronously where multiple microservices written in Go each do their part before handing over the transaction to the next service over a message queue.
Check out more of our talks in the following links!
NDC Conferences
ndcoslo.com
ndcconferences...

[@sorcererstone3303]

@28:00 The presenter said the regulators did not accept data being stored somewhere in the cloud. To resolve this issue, the presenter's group went with NATS. Can someone please explain or give me a URL reference how NATS resolves this data storage location issue in the cloud mentioned by the speaker? I failed to see how NATS is the answer to this exact data storage location question from the regulators. How are these 2 topics (NATS & exact data locations) related?

[@guibirow]

I assume the regulators concerns were regarding data locality, some SaaS services does not allow you to chose where data are being replicated to in order to maintain scalability. Using NATS gives them the control were the data is located because is base on the cluster location.

He forgot to specify his blood group in the introduction.

[@richfuturebydsk2562]

Thanks a lot for the presentation about Bulder Bank.
Much support from ZAR - KwaMashu.
Rich Future by DSK.