Hey Sammis,

before giving any technical advise, or seeking technical advise, I would always recommend to lay out the requirements as precisely as possible.

You state that

Let me put it this way: maybe. But this is most certainly not your real concern right now. Every choice you can make will inavitably have its downsides.

So the real questions are:

1. Why is money a problem? If you’re going to do business for 20-30 years you need to make millions yourself with this enterprise. So if money is a problem now, developing from scratch is maybe not a smart option.
   (That beeing said: economically it makes sense to keep costs down. Just remember that licensing costs will almost always be lower than development costs if you can get the same system. This is true for almost any part of the world)
2. What are you up to? Are you a startup? Are you a development department or agency for a company that wants to expand or change its business? Is this a public government sector type of thing, where paying people is not a problem because they are “there anyway”?
   2b) How many people will be working on the project.

Pointing to any particular technology is not doing any good, without answering at least question 2). Because it massively depends on what to optimize for.

That beeing said: if you are sure (and I mean absolutely, rock solid, super dooper, “I have seen the contract” sure) that this project will be very long running you need to optimize for one thing: changeability / refactoring. Don’t hardwire stuff, keep everything as separated as possible. Create clean APIs that stabilize fast and don’t change. Keep the scope of every part of the system as small and focused as humanly possible.

This advice is, I think, universal for large systems and does not depend on any particular technology. Just like: try to introduce as little side effects as possible and only in well defined and understood places.

So, if you can, please give us a little more info about your project

(Not that I don’t enjoy a good technology discussion but I think this isn’t helping OP as much )

I know you mention no off the shelf solutions, but everything you mentioned is way bigger than you’d likely need initially. I’ll point out Shopify Pricing: Find the Right Plan for Your Business - Shopify and BigCommerce Pricing and Plan Information | BigCommerce as two things that don’t cost nearly as much and are likely cheaper than paying a team to build something equivalent.

From reading the requirements what jumps out at me if that it is required to last for 30 years, so I would think carefully about what technology is going to last that long.

The Java ecosystem has enough momentum for that, is currently very mature, and is not difficult to hire for, so I would be seriously Kotlin, Scala or Java.

I’ve not come across NuoDB before. It seems to be a niche proprietary database. Given proprietary databases have a habit of disappearing due to funding problems and niche databases have a problem of disappearing due to contributor shortages do you think it’ll be around in 10+ years? You may end up having to maintain an unfamiliar database by yourself, which is a scary idea. I would likely use Postgres or MySQL/MariaDB, both will still be around and supported for that long and both have been proven to usable at scale.