The Web is still fundamentally a platform for content not applications. And it's even less an AI-native application platform.
Qworum is a new Web variant that was built for application use cases. It's the only application platform (or OS) that is AI-ready, in the sense that applications are structured the right way for full AI enablement.
This article seems to suggest that atomic application updates at the server side is by itself a solution to application versioning, which it isn’t. As long as client-side asset caching is enabled, which it is by default for all web applications, then the neatly separated application versions will get all mixed up in the browser. One solution would be to serve each application version under a different path prefix.
Supply-chain attacks are big problem for the JavaScript ecosystem. In this short post I will outline a straightforward security measure that can be implemented by all JavaScript runtimes, both in-browser and off-browser. This will prevent most of the supply-chain attacks that are plaguing the JavaScript ecosystem today.
One thing this blog does not question is whether package managers are needed at all. Look at how Deno does it: packages are imported from URLs and downloaded to a local cache at run-time. This allows CDN-based package distribution, but you still need a package search engine.
The world’s most unfalsifiable digital certificate counts for nothing if the data in it isn’t authoritative. A person can’t be identified by his/her name. It can change, and so can the name of the birthplace, not to mention people having the same name.
I'm with you that RPC is better suited for action-oriented APIs - but flask-restx gets the job done well and I know more about it, which is enough for me to simply stick with it. I also like swagger. I'll consider RPC for my next project though
Hi, I have recently launched a B2B software startup (qworum.net) and I am looking for salespersons. Compensation is commission-based: 20% recurring commission on realised sales. If you want a $80K revenue, selling 80 Qworum Alloy subscriptions will get you there. Your recurring commission will keep coming in as long as the subscription is live. Feel free to drop me an email at [email protected]. Best.
Qworum is a front-end PaaS that brings all the benefits of microservices to the UI layer, and makes web UIs fully compatible with microservices architectures.
Qworum is positioned as an alternative to micro front-ends. As you may know, the rate of adoption for micro front-ends have been tepid so far, and as a result monolithic front-ends remain a significant impediment for microservices architectures. Qworum is a solution to this issue which plagues large-scale software systems.
Qworum is pioneering several industry-firsts:
▶ a new type of microservice (the interactive microservice),
▶ a new type of web API (the multi-phase web API),
▶ a platform for distributed web applications,
▶ a new type of web (Qworum’s Service Web is about interlinked microservices, whereas the World Wide Web and the Semantic Web are about interlinked content).
Presenting Qworum’s service web, the first web conceived for applications and the 3rd web after Tim Berners-Lee’s document web and W3C’s semantic web, both content webs.
Microservices architectures are all the rage these days amongst enterprise devops teams, but
web frontends have largely remained monolithic (micro frontends have found little adoption so far), so the UI layer isn’t really compatible with microservices architectures.
Enter Qworum, a Platform-as-a-Service that fully supports microservices architectures by making web UIs modular and distributed.
Qworum is a new Web variant that was built for application use cases. It's the only application platform (or OS) that is AI-ready, in the sense that applications are structured the right way for full AI enablement.