Category Archives: Microservices

And the Good News Keeps on Coming

Well, the first major enterprise project for Baseline has been announced. It’s good to see any kind of progress and hope, especially in the face of a world that’s gone to hell!

After talking with the Baseline guys (especially Kyle):

I’m excited about the next iteration of the Radish34 server, especially since there might be an Azure template available at some point. That would be an excellent development, since not all of us have the hardware just to run the damn thing. Anything resembling ZKP would probably make my current laptop spew smoke, so I’m happy to offload that gear-melting work onto Azure. And then I can finally play with Baseline for real!

So I couldn’t be happier…Well, except for one last thing: I wish that there was more of a call for some transparency with Baseline. In general, I think that it’d be great for Baseline users to have the option of submitting information to a registry, where basic information about the logic of their transactions could be made public. In fact, I might have already submitted an idea or two to the Baseline repo, with the hopes that somebody will agree with that viewpoint.

But all in all, the Baseline team is making some good progress. I hope that it doesn’t stop anytime soon!

Product Review: Azure Blockchain Workbench

So, until there’s a Kubernetes Operator for an Ethereum test chain (or something comparable where you click a button to get everything running and perfect), it seems like you’ll have to do things a little more manually when it comes to setting up an Ethereum development environment in the cloud. Why’s that? Because with a nascent tech like Ethereum, everything keeps changing rapidly, and a Docker image with an embedded Ethereum testchain and dev tools will be outdated in just a few months. So, in the end, you’d have to do the same thing anyway with just a basic Docker image: download the latest packages, make any needed adjustments to get a testchain working, and then refactor your code (Solidity, etc.) so that it’ll now compile without warnings or errors.


So, when I heard that Microsoft had created a service that would wrap around Ethereum, my eyes started to sparkle. Finally, I wouldn’t have to worry about playing the role of admin or devops, so that I can just develop…

…but then I promptly stopped and thought “Wait a minute? Microsoft? Creating a PaaS with Ethereum? Hmmmm…I don’t know about that…” Still, though, I’m willing to try anything once, so I decided to give Blockchain Workbench a chance.

So, I tried out Workbench to get a quick impression, and after a few hours, I think that I have a fair assessment of it. Now, if you’re a beginner, I’d recommend it: it’s a good place for an Ethereum beginner with an Azure account. But (and I’m trying not to be too harsh here), I would say that’s where its potential would be maxed out. Beyond being interactive teaching software for enterprise officers to learn about blockchain, I doubt that it’s something Ethereum developers or proponents would ever use. Not only is the Ethereum node completely hidden and inaccessible, the Workbench is an abstract wrapper around the node, so abstract that it becomes an hindrance to even communicate with the node. In the end, it’s completely unfriendly to a developer, an opinion which seems to be shared by others.

However, I will agree with Dimitrios on a second point: Microsoft’s template for Ethereum PoA could be useful. After experimenting with that one for an hour, I could totally see a consortium opting to try it out as a shared Ethereum solution.