Geez, all the haters here. I would argue that as long as you don't actually lose any customer's money, its OK to screw up once in a while. My e-bank site its d

Geez, all the haters here. I would argue that as long as you don't actually lose any customer's money, its OK to screw up once in a while. My e-bank site its down once a week for deploys or so, my bank's mobile app didn't to certificate pinning, and they are still operating. Actually I believe CAP isn't actually that relevant, because most money is transferred and there are double ledgers for that, which for sure isn't fully consistent. As for the paid software and support, its a crap reason. The support guy isn't omnipotent, at best he's seen the issue you're having and will help you faster. If you have paid software and you have downtime because of them, good luck trying to get money from them. And there's nothing wrong with microservices, as long as you don't need to call a bunch of them to update my balance. I don't care if I try to change my address and the service is unavailable, or if I don't receive a weekly notification. Its much better than having e-bank site downtime because they want to deploy a new version of the webapp. As long as you maintain account balance integrity, I'm sure you guys will do just fine. All the best