> I will assume the last part is just a generic statement and is not directed towards me.
It's most definitely directed at you.
> You are a Java dev I presume?
C#/C++. Though I've worked with java before amongst others.
> As for app-level locking, I am talking about sacrificing performance, not safety.
You are sacrificing both. Only idiots truly depend on app-level locking.
> We just make sure that some piece of code runs exactly once.
Amateur hour...
> Since the need for this is very rare and the places are not performance critical, we can live with that. So no, we have no need for additional transactional guarantees on DB level.
So it's a useless pointless trivial application...
> If this is not possible, we have app-level locking to avoid conflicts.
app-level locking is a recipe for disaster if data matters and more than 1 process/user/client/etc can access your data. if the data doesn't matter then I guess you can do whatever you want.
web "developers" have a bad reputation for a reason. so many amateurs amongst web developers...
> If you truly believe in Bitcoin, you believe that a) there is a good chance that in the future USD, JPY, EU, UKP et al. will be worthless relics
"believe"? You sound like a cult member. There is 0% chance that the world currencies will disappear anytime soon. If it did, bitcoins would be worth nothing anyways.
> will be worthless relics, ornaments in a history museum that schoolchildren laugh and joke
I think you are describing bitcoins...
The pathetic desperation of bitcoin fanatics like you is laughable. It's like listening to a retarded islamist.
> and that's not even counting costs of converting back to $ etc.
Even worse, it's not counting the loss of the value of bitcoins. Lots of people dumped bitcoins on overstock when it was worth much more than $200. They need to convert those bitcoins into cash to pay taxes, rent, etc.
Overstock lucked out by not doing more business in bitcoins because they would have lost even more due to the drop in bitcoin price...
It's most definitely directed at you.
> You are a Java dev I presume?
C#/C++. Though I've worked with java before amongst others.
> As for app-level locking, I am talking about sacrificing performance, not safety.
You are sacrificing both. Only idiots truly depend on app-level locking.
> We just make sure that some piece of code runs exactly once.
Amateur hour...
> Since the need for this is very rare and the places are not performance critical, we can live with that. So no, we have no need for additional transactional guarantees on DB level.
So it's a useless pointless trivial application...