Using JAVA potentially gets you into intellectual property problems since Oracle claims that APIs (and, particularly JAVA APIs) are copyright and has been asser

Using JAVA potentially gets you into intellectual property problems since Oracle claims that APIs (and, particularly JAVA APIs) are copyright and has been asserting ownership. It is a risk that is hard to quantify especially since it is up for a decision by the SCOTUS. Personally, I think Go is clean, tight, and elegant whereas Java always seems a bit clunky and verbose. For 100,000 feet, it seems to me that the particular programming language used to construct a banking system should not be a primary design choice issue. What is important are the features and use cases the banking system is to support, what the operating environment is to be, what the security environment is to be, how the system is going to be kept non-fragile, what APIs are going to be exposed to users, what scaling is going to be expected, what performance is required, and so forth.