[binocarlos]

The eth devs are busy working on sharding - the same idea as traditional databases like Mongo where a primary key decides which node the data will reside. The main problem here is that a contract residing on shard A might reference a contract on shard B (much like a join between 2 shards). They are approaching this by using "transaction receipts" that would be passed from shard to shard. https://github.com/ethereum/wiki/wiki/Sharding-FAQ

[TylerE]

> traditional databases like Mongo

Kids these days. I think my head just exploded.

[ttul]

Mongo: The unreliable partitioned database.

[binocarlos]

Ok - I meant non-blockchain databases

[abakker]

I think he meant the part where you called Mongo "traditional" as your example. (vs say, DB2)

[Klathmon]

Don't they have something roughly equivalent to the Lightning Network on ETH called the Raiden Network as well? Or am I misunderstanding that?

[binocarlos]

Indeed - Raiden is all about payment channels - funds are deposited on the main chain and then payments can be sent over channels with no fee. Only in the case of dispute or cashing out is the main chain used to resolve the conflict. This means you could make many transactions per second of very small amounts (useful for things like gambling sites or micro-payments for content). Micro-Raiden is already active which are one-to-one payment channels - the full Raiden network is not yet live but will facilitate one-to-many channels.

* https://raiden.network/faq.html

* https://raiden.network/micro.html

[thinkmassive]

You are correct, and the name Raiden is a reference to the Mortal Kombat character who shoots lightning from his fingertips.

µRaiden (two-party transfers only, no routing) is already live on Ethereum mainnet: https://raiden.network/micro.html