There is an argument that block propagation and orphan rates acts as natural barrier to the blocksize.
With a very large blocksize limit, miners who produce blocks which are very big, run the risk of a smaller block from a competing miner winning the race, as it is faster to validate and propagate over the network.
This limiting factor should mean the blocksize converges to a size that the network can comfortably handle.
~12k thousand years ago is when it appears we first started to form together into large communities, Göbekli Tepe is a good example. More here https://en.m.wikipedia.org/wiki/Göbekli_Tepe
From the link :
> This corresponds well with an ancient Sumerian belief that agriculture, animal husbandry, and weaving were brought to mankind from the sacred mountain Ekur, which was inhabited by Annuna deities, very ancient gods without individual names
We find the first evidence of cultivation around 11.5k years ago not so far away in the Levant. Aggrecuture appears to have been the major change which kickstarted civilisation as we know it off.
Thank you. After reading their website, the GitHub page and all the comments down to this point, your comment is first thing which explains what Parse is/was.
Getting rid of the zookeeper requirement is a huge plus. Adds complication to the stack when trying to automate the deployment process. Maybe you could achieve a similar thing with the Scala version however.
For the Kafka deployment itself, you wouldn't need to install scala or java. Just download the go executable compiled for your architecture and away you go.
Yep, if you ever want a good nights sleep, go somewhere you haven't been before and spend a few hours walking around. Gets the mind working overtime, in a good subconscious way.
Only because he was an early adopter of his own product. He released it to the world and kept on mining to keep the project going. He didn't pre-mine and then release it. There is a big difference there.
It just happened that it took time for people to catch on and join his mining efforts.
He could have cashed out a long time ago for a large profit but those early coins attributed to him have never moved.
Absolutely, there is a nice in built feedback loop as well.
Bitcoin increases in value which makes it more desirable, which drives miners to mine more, which increases the security of the network ( harder to attack ).
This drives the value of Bitcoin higher, repeat.
Anyone can have a blockchain, having a secure blockchain is not so easy. Miners secure the network and their reward is Bitcoin.
Yes the trade balance at the moment is negative, which is why we need the £ to fall in value, so we can export more and reduce the trade deficit.
Germany loves the Euro for the same reason, it artificially lowers its exchange rate helping it's exports. With the Deutschmark they would be at a significant disadvantage. Remember they were the "sick man of Europe" prior to joining the Euro.
This is at the expense of countries on the periphery of the EU, Greece, Italy etc. They cannot devalue and complete with Germany. Despite this look how Germany treated Greece when it needed help.
This might be daft question but I'll ask it anyway, how were they able to do this? Is the official version opensource or did they have have to reverse engineer the whole thing?
Ah the memories. From memory, and obviously we are going back a long time here, there was a program in there which you could write to make it sound like a baby was crying ( it kind of did), and another where you could design a sprite ( a hot air balloon ? ) and move it around the screen.
It all seemed rather complicated to me at the time and couldn't imagine how people were writing whole games using it. Years later you realise it was even more complicated as most games were written in assembly.
Remember waiting for the C64 port to come out, right at the end of it's life. It eventually game out and I played it on a demo cassette from a c64 magazine. It wasn't great after having experienced the Amiga version. Maybe around 1993.
Use configuration management such as chef to allow you to quickly build new nodes and to roll out changes accross the cluster. You will need to make tweaks. The chef Kafka cookbook which is the top result on Google has means of coordinating restarts of brokers accross the cluster. Use consul as a locking mechanism for this. You could use zookeeper, but consul works well for auto DNS registration and auto discovery.
Use the yahoo Kafka-manager app to manage the cluster and to see what is going on.
Don't use the Kafka default of storing data in /tmp/. Your OS will periodically clean it.
I agree, but when I say kids I was thinking more of young kids. Say up until 7 or 8. You don't tend to see much bullying at that age, maybe teasing a bit but they don't seem to be nasty in the way older kids can be when they bully other kids ( like an on going campaign to isolate and intimidate a person).
https://aws.amazon.com/kms/
You can limit access to the keys based on IAM instance profiles. So that only certain instances can access specific credentials.