It's also `Bitcoin - all_the_hard_problems_bitcoin_solves`. Still nice but you can't compare it with Bitcoin. This is more the sort of service banks could use to track loans.
Stellar is indeed decentralized but not distributed [1].
What I like about Stellar is the concept of gateways and trust. It adds a whole new dimension for transactions.
I'm using upserts... The reason I'm using upserts is basically just lazyness because I didn't feel like refactoring the source code to work around requiring upserts. Also, I'm not very confident in C++ so I did not want to take on that task.
In PostgreSQL, you can set the SERIALIZABLE isolation level for the whole database, put a retry loop around all database transactions and completely stop worrying about concurrency issues.
I think all database applications should be written like this at least until performance starts being an issue.
Entirely depends on the the type of workload / application architecture. In some cases the rollback ratios will be massive (I've seen 70%). In other cases adding such a retry loop is unattractive because the latency jitter. Or retaining all involved data for a retry is unattrictive.
Yet Another problem is that you need to enforce all sessions potentially involved in a data race need to use serializable; that can be easy or hard, depending on the scenario.
How would this prevent a flood attack ? What I mean is in Bitcoin and presumably Stellar, you need coins to create transactions. There is therefore a cost to spamming the system.
Needs a brief documentation "how it works" or something... I really don't understand the concept, I'm very familiar with bitcoin and somewhat familiar with ripple/stellar. How is the ledger maintained? How do we form the consensus on the valid ledger? What are the incentives for running nodes? etc.
> Distributed Spam Proof Mail! Uncensorable, inherently spam proof and transparently encrypted and sender authenticated messaging! Secure enough for Edward Snowden! Easy and fool-proof enough for a child!
43 exclamation points on the front page. He has the hype cranked up pretty high. Still, it's nice to see all of these P2P efforts.
27 comments
[ 4.8 ms ] story [ 67.9 ms ] thread[1] http://web.cs.ucla.edu/classes/cs217/Baran64.pdf
Which PostgreSQL features new in 9.5 are being used that cause that? Or are earlier versions somehow buggy?
IF record EXISTS then UPDATE else INSERT
I think all database applications should be written like this at least until performance starts being an issue.
Yet Another problem is that you need to enforce all sessions potentially involved in a data race need to use serializable; that can be easy or hard, depending on the scenario.
Increasing the transaction isolation level shouldn't be done out of laziness.
How would you deal with DDoS attacks? Taking down a ledger like this could be easy...
That's the open question.
43 exclamation points on the front page. He has the hype cranked up pretty high. Still, it's nice to see all of these P2P efforts.