Bitcoin blockchain design has been done for a specific purpose, and this is a money (crypto currency) transfer. But what will we do, if we want to change or add some functions of the bitcoin blockchain? What if we want to transfer other assets rather than money, what if we want to do transactions automatically when pre-determined events occurred. Or what if we don't want other people see our transactions, or track our transactions' history. You can ask countless of what if questions and every answer to these questions drive you to a different blockchain or configurations
What Bitcoin’s development team is essentially doing through feature-creep is forcing everyone in the non-tech world to use Bitcoin through commercial proxies to avoid all this complexity (crypto-what? security? sidechain?), which effectively results in the loss of security, relative anonymity and decentralized properties that helped to make it interesting in the first place.

NPD said the next step for retailers is to develop their own cryptocurrency to prevent customers from having to use credit cards when shopping online. NPD said the practice makes sense for the retailer, because if the customer could send the payment transfer via blockchain, it would avoid third-party clearing house fees retailers pay for processing card payments.
Private and Public Blockchain occurs when the financial enterprises start to explore the various blocks of the Blockchain technology. These two Blockchains are coming up with business oriented models as to obtain the difference between the two. The private blockchain generates at a lower cost and faster speed than the public blockchain. In the previous years, the blockchain has grown to become an interesting subject globally. It is becoming an integrated part in the financial sectors all over the digital world.

Decentralization and distribution are seen by many to be a major benefit of public blockchains, but not everybody shares this ethos. But this is not the only benefit of public blockchains, of course. Perhaps most importantly, their transparency makes them very secure: because they can be audited by anybody, it is easy to detect fraud on the chain. Security-via-openness is a principle well known in the open source world, and this strategy is also popular among some in the digital currency community. For example, all of the tools and content produced by the Ethereum team is open source. This helps to make Ethereum widely accessible and more secure.
Fully private blockchains: a fully private blockchain is a blockchain where write permissions are kept centralized to one organization. Read permissions may be public or restricted to an arbitrary extent. Likely applications include database management, auditing, etc internal to a single company, and so public readability may not be necessary in many cases at all, though in other cases public auditability is desired.
Segregated Witnesses — The current Bitcoin transaction signature algorithm is complicated and flawed, leading to a problem known as transaction malleability. Segregated witnesses would eliminate that, improving the efficiency of much Bitcoin software considerably … and making much more significant innovations such as the Lightning Network (see below) possible.
Public blockchains are just that, public. Anyone that wants to read, write, or join a public blockchain can do so. Public chains are decentralized meaning no one body has control over the network, ensuring the data can’t be changed once validated on the blockchain. Simply meaning, anyone, anywhere, can use a public blockchain to input transactions and data as long as they are connected to the network.
The sidechains vision of the future is of a vast globe-spanning decentralized network of many blockchains, an intertwined cable rather than a single strand, each with its own protocol, rules, and features — but all of them backed by Bitcoin, and protected by the Bitcoin mining network, as the US dollar was once backed by gold. Sidechains can also be used to prototype changes to the fundamental Bitcoin blockchain. One catch, though: this will require a small tweak to the existing Bitcoin protocol.
In simple terms, public blockchains can receive and send transactions from anybody in the world. They can also be audited by anybody, and every node has as much transmission power as any other. Before a transaction is considered valid, it must be authorized by each of its constituent nodes via the chain’s consensus process. As long as each node abides by the specific stipulations of the protocol, their transactions can be validated, and thus add to the chain

It’s the IBM “blockchain”. Basically Apache Kafka queue service, where they have modified the partitions. Each partition is an ordered, immutable sequence of messages which are continuously appended. They added some “nodes” to clean the inputs and voila; blockchain! We should add that there are no blocks, but batches of transactions are renamed to fit the hype better. Since everything gets written in one queue at the end of the day, IBM offers the bluemix cloud server (priced at 120.000$ per year) to host the service. Smaller test packages with a couple of input cleaning nodes go reportedly for 30.000$.
In general, so far there has been little emphasis on the distinction between consortium blockchains and fully private blockchains, although it is important: the former provides a hybrid between the “low-trust” provided by public blockchains and the “single highly-trusted entity” model of private blockchains, whereas the latter can be more accurately described as a traditional centralized system with a degree of cryptographic auditability attached. However, to some degree there is good reason for the focus on consortium over private: the fundamental value of blockchains in a fully private context, aside from the replicated state machine functionality, is cryptographic authentication, and there is no reason to believe that the optimal format of such authentication provision should consist of a series of hash-linked data packets containing Merkle tree roots; generalized zero knowledge proof technology provides a much broader array of exciting possibilities about the kinds of cryptographic assurances that applications can provide their users. In general, I would even argue that generalized zero-knowledge-proofs are, in the corporate financial world, greatly underhyped compared to private blockchains.
The sole distinction between public and private blockchain is related to who is allowed to participate in the network, execute the consensus protocol and maintain the shared ledger. A public blockchain network is completely open and anyone can join and participate in the network. The network typically has an incentivizing mechanism to encourage more participants to join the network. Bitcoin is one of the largest public blockchain networks in production today.