I would like to know what is the recommended version of Hyperledger Fabric (1.4 or 2.x) or if it is 100% recommended to implement the most recent version, in this case 2.x.
This is because for obvious reasons 1.4 has more downloads and implementations for having more time published.
Greetings and thanks
Hyperledger fabric 1.4 community support will finish in April 2021 (Service providers may provide support for longer). The recommendation is that you should start with Hyperledger fabric 2.2 which is the current LTS version or 2.3 if you want to try some of the newer capabilities
Related
Currently I am using Ubuntu 22.04 LTS version on Oracle virtual machine. When I try to install all the prerequisite of hyperledger composer it's showing an error Ubuntu jammy is not supported.
I am unable to run ./prereqs.sh command. Please help me
Unfortunately Hyperledger Composer has been unmaintained since August 2019 so I'm not surprised that you have hit problems with prereqs.
I would strongly recommend using Hyperledger Fabric directly, which is what Composer was based on. Although it is still not as straightforward as Composer, there have been quite a few improvements to Fabric over the last few years which should hopefully make getting started a bit easier. For example, have a look at the full-stack-asset-transfer-guide repository, which was used in a workshop at the Hyperledger Global Forum last week.
[Question posted by a user on YugabyteDB Community Slack]
The YugabyteDB core documentation for upgrades doesn't seem to address compatibility between versions. Can you upgrade from 2.8 to 2.13? Or is there a less direct path available?
The last upgrade attempted from 2.7 to 2.8 only worked for us building a 2.8 cluster and doing a snapshot restore with replication and then an application cutover. Is that the best method for moving from 2.8 to 2.13?
https://docs.yugabyte.com/latest/manage/upgrade-deployment/
In v2.8 we announced 'Seamlessly upgrade to major releases without stopping the database' see this release blog.
Also, just one upgrade could work, but we don’t officially support going from stable to latest releases or the reverse (latest to stable). There could be subtle issues because of backports status. So 2.8 to 2.12 is fine, the same 2.8 to 2.14(in future), or 2.9 to 2.13 — but 2.8 to 2.13 could face issues.
We do not officially support downgrades though.
I wanna build a blockchain on hyperledger fabric. So I found some good repos in version 1 but not in hyperledger fabric version 2.
Would you recommend to use the old version instead of the latest version (2.0)?
Thanks for any recommendation/suggestion.
Hyperledger Fabric 2.2 LTS was released July 2020, this means that Hyperledger Fabric 1.4 LTS will go out of support in April 2021 (ie do not expect any updates or releases to the 1.4 version such as bug/security fixes).
Any new project should start with the latest LTS version which is currently 2.2
I've build a Hyperledger Fabric network (v2.0.0) and I want to know if Hyperledger Explorer tool is compatible with this version of network.
Can anyone help me?
As of now regarding Hyperledger, Hyperledger Explorer can support up to Hyperledger Fabric 1.4.8
Ref:- https://github.com/hyperledger/blockchain-explorer#10-release-notes----
You are in luck. As of July 1st 2020 they support v2.0 and above.
Just download the latest docker image build of version: v1.1.1 (Jul 17, 2020) and you are good to go.
I'm trying to understand restrictions of upgrade from/to different versions of cassandra.
On the one hand, Cassandra docs
http://docs.datastax.com/en/upgrade/doc/upgrade/cassandra/upgradeC_c.html
are saying "Cassandra 3.0.x restrictions: Upgrade from Cassandra 2.1 versions greater or equal to 2.1.9...", and I understand that as 'you couldn't upgrade to 3.0 from 2.1.8 and prior 2.1.* versions'.
On the other hand, there are no any restrictions on upgrading from, say, 2.1.8 (version prior to 2.1.9) to 2.1.11 (version grater then 2.1.9), in particular, 2.1.8->2.1.11 upgrade don't require upgrade of sstables.
So, could someone explain, why it's possible to upgrade from 2.1.9 to 3.0 but not from 2.1.8 to 3.0?
The docs restrict you from upgrading from early 2.1 versions to 3.0 because there are bug fixes and stability improvements in the later 2.1 releases that affect upgrades.
The best practice is to go to the latest patch on your branch before upgrading a major release. I.E. go to the latest 2.1.x and then go to 3.0.
Note: 3.0.0 dropped last night and it is very early in its release cycle. Make sure you test thoroughly in a qa environment before upgrading your production instance and follow the upgrade docs carefully.