Web assembly, when coupled with products like wasmCloud and NATS, is creating a new paradigm for cloud native, which should eliminate entire classes of problems that we struggle with today in building distributed applications.
Red Badger Presentation and Demonstration at Cloud-Native North America WasmDay 2021
Presenters: Stuart Harris, founder and chief scientist and Aayush Attri, senior software engineer, of Red Badger
Red Badger is obsessed with helping organizations streamline their ability to deliver digital products and services. As a consultancy, the company has experienced the pain of building microservices using today's architectures. Stuart Harris notes, “It's not straightforward by any stretch of the imagination. And there's a lot to think about.”
Stuart’s keynote takes viewers through Red Badger’s engagement with one of Europe's largest banks to describe what a future state platform architecture would look like. This was all in preparation for a world where the bank could easily deploy workloads securely and reliably across on premise and any cloud without having to constantly adjust network topology to suit.
Harris recognizes, “This is really refreshing that large enterprises are thinking ahead like this, driven by the pain of working with today's development environments.” Red Badger built a proof of concept to show what such a platform might look like and
The Context
The next decade will be characterized by rushing out of the cloud – enough to be independent of any one provider. And that's enough to make good use of the edge, on premise, Internet of Things, etc. For companies in regulated industries, like financial services or healthcare, regulators will insist that organizations have a ‘get out’ plan. Realistically these plans aren't yet real and organizations wouldn't be able to execute them, at least not quickly. They are in place to satisfy the regulations. The reality is that the cost of moving everything to another cloud provider is prohibitive.
Kubernetes is the first time that there has been a standard, consistent and uniform way to deploy its innovations regardless of which cloud provider they want to use. However, according to Stuart, they are still locked into cloud provider specific services.
While Kubernetes was the first step on this ladder, what's the next step? Whatever it is it needs to be multi-cloud or multi-location. And to do that requires a higher level abstraction that sits above the HTTP and TCP IP network that dominates microservices today. “But multicloud is not really a thing yet,” says Harris.