e2core
IncludeOS
e2core | IncludeOS | |
---|---|---|
9 | 10 | |
718 | 4,821 | |
0.1% | 0.1% | |
6.6 | 0.0 | |
8 months ago | 7 days ago | |
Go | C++ | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
e2core
-
Are V8 isolates the future of computing?
> If one writes Go or Rust, there are much better ways to run them than targeting WASM
wasm has its place, especially for contained workloads that can be wrapped in its strict capability boundaries (think, file-encoding jobs that shouldn't access anything else but said files: https://news.ycombinator.com/item?id=29112713).
> Containers are still the defacto standard.
wasmedge [0], atmo [1], krustlet [2], blueboat [3] and numerous other projects are turning up the heat [4]!
[0] https://github.com/WasmEdge/WasmEdge
[1] https://github.com/suborbital/atmo
[2] https://github.com/krustlet/krustlet
[3] https://github.com/losfair/blueboat
[4] https://news.ycombinator.com/item?id=30155295
- OAuth with Cloudflare Workers on a Statically Generated Site
-
Show HN: Sat, the tiny WebAssembly compute module
One of the first things we've used it for internally is to run one-off isolated tests on WebAssembly modules instead of feeding them through a production Atmo[0] instance. It basically serves as a dumb pipe for feeding data in and out of a Wasm module.
0: https://github.com/suborbital/atmo
- Atmo: Serverless WebAssembly
-
WebAssembly Landscape 2020
Excited to see Atmo on there 🙂 https://github.com/suborbital/atmo
-
Choosing building blocks to move faster
My open source focus for this year is building Atmo, and there is one aspect of the process that I would like to highlight. Since early 2020 I knew roughly what I wanted to build. The specifics of that thing changed over time, but the core idea of a server-side WebAssembly platform was consistent all throughout the year. I didn't write a single line of code for Atmo until late October, even though that was what I wanted to build the entire time. I want to talk about why.
-
Building for a future based on WebAssembly
I am also open to any and all contributions from the community. I am more than happy to meet with anyone interested in working alongside me to build these capabilities so that I can help get you started developing Atmo, Vektor, Grav, Hive, and Subo. Developers with no experience working with WebAssembly, distributed systems, web services, or Go are encouraged to join and I will do whatever I can to help you learn what's needed to contribute. Open Source is not just about developing in the open, it's also about helping others learn.
-
Meshing a modern monolith
With SUFA systems, multiple ASGs are created, each designated as a capability group. Each capability group is given access to the resources required for the associated function namespace to operate (such as the datastore or secrets), and can then scale independently of one another. Since the application's functions are decoupled entirely from one another, it's possible for some functions to run on the host that receives the request, and functions from particular namespaces to be meshed into other capability groups. A SUFA framework such as Atmo is responsible for handling the meshed communication, completely absorbing the complexity.
-
Building a better monolith
The SUFA pattern was designed in concert with Atmo, which is an all-in-one framework upon which SUFA systems can be built. Atmo uses a file known as a 'Directive' to describe all aspects of your application, including how to chain functions to handle requests. You can write your functions using several languages to be run atop Atmo, as it is built to use WebAssembly modules as the unit of compute. Atmo will automatically scale out to handle your application load, and includes all sorts of tooling and built-in best practices to ensure you're getting the best performance and security without needing to write a single line of boilerplate ever again.
IncludeOS
-
Using Zig to Unit Test a C Application
So sad IncludeOS https://github.com/includeos/IncludeOS is no longer developed.
-
Hypervisor from Scratch (2022)
Nice! I wonder how well it will work with IncludeOS [0]?
[0]: https://github.com/includeos/IncludeOS
- IncludeOS: A minimal, resource efficient unikernel for cloud services
- Are V8 isolates the future of computing?
-
why is there software still in C like the linux kernel when you could use cpp?
Also includeOS is a thing https://github.com/includeos/IncludeOS
-
C or C++ as web app backend?
IncludeOS can be used for that as well
-
One Hundred
FreeRTOS, Redox, IncludeOS (https://www.includeos.org/),...
-
Hacker News top posts: May 23, 2021
IncludeOS – Run your application with zero overhead\ (7 comments)
- IncludeOS – Run your application with zero overhead
-
Operating System, Not Software Language HARVARD !!!
I mean hell in c++ you can use #include and your binary will contain the operating system.
What are some alternatives?
miniflare - 🔥 Fully-local simulator for Cloudflare Workers. For the latest version, see https://github.com/cloudflare/workers-sdk/tree/main/packages/miniflare.
app-nginx - Nginx on Unikraft
wasm-micro-runtime - WebAssembly Micro Runtime (WAMR)
serenity - The Serenity Operating System 🐞
krustlet - Kubernetes Rust Kubelet
websocketd - Turn any program that uses STDIN/STDOUT into a WebSocket server. Like inetd, but for WebSockets.
grav - Embedded decentralized message bus
Crow - A Fast and Easy to use microframework for the web.
sat - Tiny & fast WebAssembly edge compute server
Cutelyst - A C++ Web Framework built on top of Qt, using the simple approach of Catalyst (Perl) framework.
workers-sdk - ⛅️ Home to Wrangler, the CLI for Cloudflare Workers®
blueboat - All-in-one, multi-tenant serverless JavaScript runtime.