EdgeChains VS hono

We build a WASM compiler to compile our prompts and chains into webassembly. Honojs was a critical part of it.

https://github.com/arakoodev/EdgeChains/

EdgeChains: github.com/arakoodev/EdgeChains

would love your thoughts on this as well - https://github.com/arakoodev/edgechains

got frustrated in the same way with "Black Box Prompting - every library hides prompts/chains in layers of libraries...while it should have been declarative.

EdgeChains - allows u to specify ur prompt and chain in jsonnet. This why i think Generative AI needs declarative orchestration and not previous generations. https://github.com/arakoodev/edgechains#why-do-you-need-decl...

when will you have pgvector as a destination ? we (https://github.com/arakoodev/edgechains) work with a lot of enterprises and they would not move away from using redis or pgvector even as their vector store. Is there a way where we can leverage that ?

Second, for a LOT of enterprises, they want to use non-openai embedding models (minilm, GTE, BGE), will you support that. For e.g. in Edgechains we natively support BGE and minilm. Would you be able to support that ?

oh really ? Thats awfully kind. I'll take that in for EdgeChains as well.

https://github.com/arakoodev/EdgeChains/issues/172

Promptfile is written in markdown, which is unsuited for templates and config management.

I have an attempt in the same domain, would love feedback

We didnt invent a new markup - we used jsonnet which is used in large scale kubernetes and has a grammar that has been well tested for config mgmt.

https://github.com/arakoodev/EdgeChains/blob/main/Examples/r...

Prompts live outside the code.

I used hono to implement worker.

Hono - Ultrafast web framework for the Edges

Hono is an ultrafast web framework for the edge and it's amazing. It's simple as express and the DX is mind-blowing. And now you can also serve JSX with it 🤯. Anyone in the industry for long enough knows that a setup like this can be quite tedious to manage and maintain. I might sound biased for Hono, and that's true, I love it ❤️.

Please could a fellow HNer who has experience using this explain in simple terms what Hono on a Cloudflare Worker enables that one cannot already do with a vanilla worker?

The docs[0] are not instructive on this point.

[0] https://hono.dev

Hono, a powerful framework, is our secret sauce for crafting high-performance APIs. With its intuitive syntax and seamless integration with Next.js, Hono simplifies the process of optimizing API performance.

Hono—a simple and fast framework for processing HTTP requests.

A good alternative of this can be - [Hono]https://hono.dev/

I agree that “fast, lightweight, web standards” isn’t much of a description but not too far down https://github.com/honojs/hono I did this:

> Hono … is a small, simple, and ultrafast web framework for the Edges. It works on any JavaScript runtime: Cloudflare Workers, Fastly Compute, Deno, Bun, Vercel, AWS Lambda, Lambda@Edge, and Node.js.

Hono offers good DX and a blazingly fast library to help you build your backend with native RPC embedded in its code. It has Zod support and it's written with TypeScript with very readable types so you can understand what's happening. It also supports Bun and a bunch of runtimes so you can run it everywhere. Check the documentation! It's also very helpful.

Initialize your hono project using bun: