This article was first published on null
Building decentralized applications can be easy. In the next paragraphs you will find out how we simplified a previously cumbersome process by launching our latest meta-use case, gWASM.
When your application or service work load hits limits, you think of changing machines, enlarging cluster or moving to a cloud. Instead of that you can integrate with gWASM and delegate your computations to Golem Network infrastructure.
gWASM stands for WebAssembly on Golem. It is intended to be a bridge between applications and extensible infrastructure. It gives your applications or services easy access to external and decentralized computational power. This access happens in anelastic manner, meaning that you rent as much infrastructure as you need and when you need.
gWASM being decentralized means that you are not bound to a single provider. Switching between providers and making new contracts is automated and quick. The cherry on top? This competitive marketplace offers good prices.
The language’s popularity is growing at a fast pace. It has been supported supported by all the major web browsers for some time lately, other use cases have been emerging - including Golem, Ethereum’s migration from EVM to eWASM, as Substrate’s runtime architecture, and more.
WebAssembly binaries are executed in the same way on various OSes: meaning it is almost deterministic. It allows better control so we can handle randomness and temporal operations and therefore make it truly deterministic. WASM brings of these benefits, without sacrificing performance, whilst the speed is comparable to native execution.
Cross-compilation of Rust, C, C++, js programs is a convenient way to create the WebAssembly code you need to create the gWASM task. In the gWASM setup, we use WebAssembly for remote computations, which is a different approach than the usually known - for web browsers. It has its specific requirements but ...
To keep reading, please go to the original article at: