Comment by Sudhanshu Shekhar on "Which framework/language to use for banking/insurance backend core system?"

~22 records per minute

around <10 seconds in total

Neither of these requirements are very stringent IMO. You can use any framework/language that you're comfortable with. Database design is generally the harder task in such cases.

That said, I would recommend using statically typed langauges (java/Go) and an ACID database like Postgres. Would strongly recommend staying away from NoSQL databases in such a use case.

I agree with this assessment.

There's really no language or framework that is the wrong choice for these requirements, as your throughput is quite slow and presumably small (although I don't know the amount of computation required by your validation process). So all languages out there will handle this just fine.

However, I am sure there are a bunch of other requirements, both functional and non-functional that you didn't mention or which simply haven't been clarified yet. The finance sector will be mostly interested in data security and integrity, plus auditability. Your auditors will look at your database access and the reliability and security of your data transfer mechanisms. I suspect this is the area where you will find the kind of requirements that make some frameworks more suitable than others.

@batjko @sudshekhar The validations include, validating client details against government databases, verify computation of front end again by calculating the same here with our own computation block. Check for data integrity of the user in some 3rd party vendor API etc and I need all that to be well under 10 seconds.

And, you are right, database access, read times and other parameters you mentioned are of paramount importance. So with all that in mind, I had Scala/Go/Java in my mind, but still wanted to se if there is any other framework which will be factory fit for such requirements.

Well, out of those validations, the database checks are in all likelihood going to be your primary bottlenecks. Reducing the cost of making those calls, e.g. by using caches, is going to be vital.

The cost of your computationally heavy validations may not be particularly high, since you only expect around 30 requests per minute, i.e. 1 every two seconds on average. Go is faster than Java or Java-derived languages, but any of the languages will do fine for you, performance-wise.

As I said above, your language choice here won't affect your performance much, but may be more around other requirements, incl. the ecosystem for libraries, ease of the learning curve or available expertise etc.

Search Hashnode