This month’s Radius release is the most significant since we initially open-sourced Radius in late 2013. Why? Because v0.47 includes the new “Radius Resource Types” feature, which makes Radius fundamentally
extensible at the resource level and is the feature most requested by Platform Engineers using Radius. The feature is so significant that Mark Russinovich headlined the June Radius Community call to personally present and demo the feature. Mark pointed out
that Resource Types is something of a “reboot of Radius” given the level of flexibility it provides to Platform Engineers. Please check out
Mark’s ’s presentation and demo of Resource Types, which he refers to as “the killer feature,” and “a big break through driven by customers.”
Another major step forward in v0.47 is Radius application portability
across compute runtimes: That means Radius applications can now be deployed, not only to Kubernetes, but also to serverless container runtimes, starting with Azure Container Instances (ACI), with other runtime support in the Radius roadmap. The combination
of Radius application portability across clouds (on-premise, Azure and AWS today) and across runtimes (Kubernetes and now ACI) means Radius future proofs your applications, regardless of what cloud or runtime you choose to rely on in the future.
And there are lots of other great features in v0.47 as summarized below! This has been a great month for the Radius community and customers!