Wasmer recently released version 1.0 of its server-side WebAssembly runtime, and it is now generally available. Wasmer enables super lightweight containers based on WebAssembly. Version 1.0 marks a significant milestone on a journey, which started more than two years ago with version 0.1.0. It is an indicator of the growing interest in WebAssembly on the server-side. (Read more on InfoQ)

Jennifer Cadence, a product marketing manager at Google, recently published an account of the state of no-code app development. In her post, Cadence breaks down why no-code platforms have become an essential part of digital transformation. She suggests that speed and agility, productivity and collaboration, and governance and security are the critical factors for these platforms’ importance. (Read more on InfoQ)

In a recent blog post, Medium describes how it built a recommendation service named “Rex.” The original recommendation service was part of the Node.js monolith, and it could only rank 150 stories. However, Medium wanted this service to rank hundreds of thousands of stories per user in under a second. So, they decided to build an entirely new, separate service using Go. (Read more on InfoQ)

In a recent blog post, Uber engineers highlight how they use a replication platform to implement disaster recovery at scale with a multi-region Kafka deployment. Uber has a large deployment of Apache Kafka, processing trillions of messages and multiple petabytes of data per day. Uber’s engineers provided business resilience and continuity in the face of natural and human-made disasters. (Read more on InfoQ)

AsyncAPI and Postman announced a partnership to support the AsyncAPI specification on the Postman platform. In their respective announcements, they detail how this partnership allows boosting the development of Asynchronous APIs. This will be done by building better tools to help engineers create and maintain Asynchronous APIs while using their favorite programming languages and frameworks. (Read more on InfoQ)

Netflix has successfully implemented a federated GraphQL API at scale. In a recent blog post series, engineers from Netflix describe their journey and the lessons learned in the process. With GraphQL federation, the API gateway implementation is distributed to backend teams owning the individual domain services they implement instead of centrally developed as part of the API gateway. (Read more on InfoQ)

Software engineers from LinkedIn recently published how they migrated away from a Lambda architecture. The Lambda architecture implementation caused their solution to have high operational overhead and added complexity, leading to slow product iteration times. As a result, the engineers chose to migrate to a Lambda-less architecture, resulting in significant development velocity improvements. (Read more on InfoQ)

During a no-slides presentation at .NET Conf 2020, software architects from the .NET runtime team presented several .NET 5 runtime improvements and how they achieved them, including ARM64 support, HTTP/3, and single-file applications. (Read more on InfoQ)

Engineers at Dropbox designed a distributed async task framework (ATF) that can handle tens of thousands of async tasks scheduled per second. ATF’s main feature is its ability to enable developers to define callbacks and schedule tasks that execute against these pre-defined callbacks. (Read more on InfoQ)

Netflix uses its homegrown API gateway, Zuul, to classify incoming requests into priorities. When the system comes under load or is otherwise unstable, Zuul throttles traffic, starting with the lowest priority. It then progressively adjusts to shed load according to the priorities calculated until the system is healthy again. (Read more on InfoQ)