Telefónica to host Hyperledger Fabric network for Alastria blockchain consortium

Spain’s Alastria consortium, which boasts more than 500 member organizations, has partnered with Telefónica to build an enterprise blockchain network based on Hyperledger Fabric. The consortium prefers to be blockchain agnostic. However, to date, it has built two networks on different versions of enterprise Ethereum – Quorum and Hyperledger Besu.

There will be two versions of the Fabric network provided by Telefónica. One will be an open shared network available at no cost to Alastria members and is intended for proofs of concept and low demand solutions. The other is a closed platform for heavier load applications where Telefónica will commit to service levels such as availability, scalability and performance.

Telefónica is a founding member of Alastria and also a member of the Hyperledger alliance, part of the Linux Foundation.

“The new network is an alternative for some partners who need to deploy their decentralized applications with demanding and personalized service levels that until now could not be guaranteed with collaborative operating models,” said José Luis Núñez, head of the Blockchain unit at Telefónica Tech.

“What we seek in collaboration with Alastria is to add more value to the ecosystem by offering them options both to explore and develop their solutions in a collaborative environment and to later industrialize them with guarantees.”

One of the more interesting aspects of the announcement relates to interoperability. Telefónica will provide native interoperability with the exiting Ethereum networks on Alastria as well as the European Blockchain Service Infrastructure (EBSI) being built by the EU. Additionally, it will incorporate Alasria ID.

“Innovation, inclusion and collaboration between the partners are reinforced with this agreement,” said Montse Guardia, General Manager of Alastria.

To date, Telefónica’s blockchain activities might be divided into two areas. First is providing blockchain hosting services and its own TrustOS, which is a combination of middleware and blockchain as a service. An important part of TrustOS came from partnering with startup Ocyan. Middleware, by definition, adds a layer between external applications or data and the blockchain. And blockchain middleware usually integrates with multiple blockchain flavors. Hence, this is likely the explanation for the interoperability promised.

The second Telefónica activity area is the use of blockchain by telecoms firms for roaming agreements and payments.


Image Copyright: Telefonica

Related:

  • No Related Posts

Does an IIB fix pack has to be installed over an existing version of IIB, or can I use it for a fresh installation?

Does an IIB fix pack has to be installed over an existing version of IIB, or can I use it for a fresh installation?

For example, does IIB 10.0.0.11 has to be installed over an existing IIB 10.0.0.x installation, or can I just directly fresh install 10.0.0.11?

Regards
Charles

This dW Answers question is about an IBM document with the Title:
IBM Integration Bus V10.0 – Fix Pack 10.0.0.11

Related:

  • No Related Posts

Putting/Getting non-persistent messages out of syncpoint – performance

Please confirm if my understanding of the following is correct:

Scenario:
A distributed application puts a high volume (200-800 per second) of request messages onto ten shared mainframe queues (MQ v8.0) via SVRCONN channels . Each of these non-triggered queues have multiple CICS transactions processing these requests and putting responses onto another set of ten shared queues then read by distributed processes. All the requests are processed by MSGID and all the queues are non-persistent. CICS syncpoints are issued every 200 messages.

Goal:
Improve throughput by eliminating as much of the MQ wait time as possible.

Proposal:
Have the application issue all puts and gets outside of syncpoint. The messages are non-persistent, the data is stale after a few seconds and the application/business is not concerned for message rollback. My understanding is that putting/getting within syncpoint will lock the message until a commit/syncpoint is issued. By modifying the application to put/get outside of syncpoint this delay will be avoided. Is this correct?

Note that these transactions are long running (with built in delays), therefore all SMF statistics are aggregate so we cannot accurately state the value of MQ wait times.

My question is really is just to ensure that my understanding of the syncpoint process in the above regard is correct.

Thanks.
Allen

Related:

Why does LLA get abend 878 and multiple CICS regions fail to initialize?

When initializing multiple CICS regions about the same time, the LLA service fails with abend S878 and many (but not all) of the CICS region fail to initialize. The reasons for the CICS failures can be quite different. For instance, some of the CICS failures have been:

DFHLD0001 An abend (code 0C4/AKEX) has occurred at offset X’FFFF’ in module DFHLDLD1.

DFHLD0001 An abend (code 0D5/AKEX) has occurred at offset X’FFFF’ in module DFHLDLD1.

DFHPC0401 Abend AEXZ issued by III task.

DFHLD0001 An abend (code 878/AKEX) has occurred at offset X’FFFF’ in module DFHLDDMI

DFHLD0002 A severe error (code X’6929′) has occurred in module DFHLDDM.

Related:

BAQR7062E: z/OS Connect service install failed. The provider property CICS-1.0 in the service archive file does not match any of the install service providers

I am trying to deploy a service to an embedded zCEE server running in
CICS using the new feature available in V3.0.3 of the Toolkit. When I
try try to deploy I receive message “BAQR7062E: z/OS Connect service
install failed. The provider property CICS-1.0 in the service archive
file does not match any of the install service providers”. But if
first export the SAR and the FTP it to the services directory the
service installs with no issues.

Related:

Is the traffice between rule engine and CICS/batch job encrypted?

The documentation shows that we can configure a zRule Execution Server for z/OS running in CONSOLE, TEST, or HTDS mode to use SSL for data encryption, and optionally authenticate with the server by using a client certificate.

How about the traffic between ODM rule engine and CICS/batch job, is it encrypted?

Related: