In October of 2018, the very beginnings of the autom(8) concept started to take shape. We didn’t start building in earnest until late December of 2018 and by April 2019 we launched a fully functional alpha version of the product. We went from our first line of code to alpha in just over five months. Here’s how we did it…
libp2p — Our Rocket
When we first told one of our friends and de facto advisor, Raul Jordan, about what we were building he immediately told us to look into libp2p, developed by Protocol Labs. He and the Prysmatic Labs team were using libp2p as their P2P technology to build Prysm (also my wife’s name ), a sharding client for Ethereum 2.0. Based on his high regard for this tool, we knew we had to check it out.
And boy were we glad we did! Because of libp2p, we were able to skip a lot of the difficult work that, quite frankly, was scaring the shit out of us. With libp2p, here’s what we get out of the box:
· P2P connectivity – libp2p handles peer-to-peer streaming out of the box. It’s super easy to get bootstrap nodes up and running to provide connectivity to the broader network. Read the complete article here.
For regular information become a member in the Developer Partner Community please register here.
Blog
Twitter
LinkedIn
Facebook
Meetups
Technorati Tags: PaaS,Cloud,Middleware Update,WebLogic, WebLogic Community,Oracle,OPN,Jürgen Kress