Home » The Hyperlocal Web: Revolutionizing Web Development with WebAssembly and Serverless Edge Computing

The Hyperlocal Web: Revolutionizing Web Development with WebAssembly and Serverless Edge Computing

by Dragos Ruse
6 minutes read

As we propel into 2023, we’re focusing on two pivotal web development trends that are shaping the Hyperlocal Web: WebAssembly and service workers, in conjunction with serverless edge computing.

We’re attempting to lessen the amount of processing done on the client with edge computing and serverless functions. Instead, we rely on a sizable distributed network of servers to quickly provide their work to the customers. We’re enabling client applications to run server-like code natively and offline with WebAssembly and service workers. Note that there are some variances between web & service workers, but for the purposes of this article we’re going to use the term “service workers” to relate to both interchangeable terms as they both have a role to play.

These two developments appear to be at odds with one another at first glance, but we believe their junction is the key to the web’s hyperlocal future. So let’s examine each trend in more detail on its own.

Serverless Edge Computing: The Backbone of the Hyperlocal Web

Web page creation has completed a cycle. Servers rendered websites and sent us the HTML and CSS as a starting point. After that, JavaScript appeared, and the pendulum quickly swung the opposite way. What if we give merely a lot of HTML and JavaScript to the client and offload all the work to them?

We’re back to letting servers perform (most of) the work for us and sending (mainly) HTML and CSS thanks to edge computing and serverless functionalities.

The defining characteristic of the Hyperlocal Web is the use of geographically distributed ‘edge networks.’ By utilizing these networks, we’re able to deliver server-rendered data to our web apps with significantly reduced latency. ‘Serverless’ operations further streamline this process by drastically reducing our dependency on managed resources. Amazon (AWS) was once the sole dominator in this field, but the landscape has expanded. Now, we’re witnessing an influx of companies offering this Hyperlocal Web-friendly software delivery approach, including the likes of CloudFlare, Vercel, Render, and Deno Deploy among others.

See also
Custom AWS Nginx & PHP Elastic Beanstalk Platform for Enhanced Performance and Scalability

Frameworks for web applications are constantly changing to enable this new style of server-first development. To mention a few, there are NextJs, SvelteKit, Remix, and Qwik in addition to Deno’s Fresh. Moreover, React is creating a brand-new class of native Server Component. The days of using a single EC2 instance to provide megabytes of JavaScript to the browser and relying solely on the client application are undoubtedly coming to an end.

WebAssembly & Service Workers

Even while WebAssembly has only been a native feature of browsers for around three years, it has been around for six. Version 2.0 is still in the working draft stage. Essentially, WebAssembly enables compiled binaries of non-JavaScript languages, like the steadily growing Rust, to operate in the browser at rates close to native. It’s similar to installing a server in your browser. This makes it possible for web apps to perform pretty sophisticated tasks (such as 3D rendering) natively and more quickly than when JavaScript was the only option.

Service providers have been in existence for a little while longer. Although the version 1 candidate draft was released last year, the first W3C working draft was released in 2014. Web applications can effectively use parallel computing by offloading tasks off the main browser thread through the use of service workers. Also, they improve performance and offline caching when network access is poor. This enables your program to function “locally” until it can connect to the server and synchronize.

We can build strong and powerful web applications by combining WebAssembly & service workers, shifting the effort from the server to the client by providing the client with a ton of JavaScript. We’re attempting to prevent that with our server-first edge network applications, aren’t we?

See also
5 Essential Steps to Kickstart Your MedTech Project

Edge Computing & WebAssembly

Thankfully, it is simple to reconcile these two developments. WebAssembly support is already available from edge network & serverless compute providers on various platforms. This enables code packages that can actually be written once and run anywhere.

Service workers enable client programs to simultaneously retrieve and cache resources in the background. The downloading of these assets should be greatly accelerated by nearby edge nodes. A serverless function may handle the first app request in a typical app lifecycle, with future app requests running natively in the client.

The web app developer now has a lot of power as a result. By taking into account aspects like whether pertinent data is kept on the server or the client and whether the client has had a chance to cache huge code files, you can optimize where your app performs its heavy lifting. For improved performance, you may even set up your optimization to work simultaneously on the client and server.

What Comes Next for the Hyperlocal Web

We look forward to seeing how other app frameworks use this new paradigm. The trend is toward server-first programming. Yet, the concept of run-anywhere WebAssembly and having your program intelligently manage the server-client handoff with service workers is still in its early stages.

We’re curious about how edge networks spread. The provider rivalry is heating up, but I believe we’re only touching the surface of what’s possible. For example, we may see technologies emerge that make it simple to deploy your app over various edge networks, ensuring that your customers always communicate with the nearest possible data center.

See also
10 ChatGPT Web App Integrations for Your Business

Also, we would like to see investments in this kind of infrastructure from governments and municipalities. Imagine if you could pay local governments to host your app instead of paying a private company. The computing power of your users’ servers might be located right in their backyards.

At HyperSense, our global software development company, we love to see how technology trends shape the future of the apps built around the world and this inspires us to keep on moving forward, as the boundaries of software development can yet be crossed with creativity, innovation, and good work. If what we do inspires you too and have an idea of a web or mobile app for your business, don’t hesitate to reach us. Let’s work together for a brighter future!

How useful was this post?

Click on a star to rate it!

Average rating 5 / 5. Vote count: 200

No votes so far! Be the first to rate this post.

Related Posts