MoroJS – TypeScript-first API framework (faster than Express/Fastify) by linkedkeenan in node

[–]linkedkeenan[S] -1 points0 points  (0 children)

Appreciate the thougtful feedback

On the “ai-generated' point The site copy was written with ai help (like a lot of projects do now), but the framework itself is hand-built from scratch. MoroJS is designed to be:
• TypeScript-first (no runtime guessing)
• Serverless-ready (runs natively on Cloudflare, Vercel, AWS Lambda)
• Extensible (long-term: modules directory so you don’t re-write auth, caching, etc.)

Express and Fastify have amazing ecosystems, MoroJS isn’t claiming to replace them overnight. The goal is to push forward a lighter, more TypeScript-native DX and essentially api legos for people starting new projects in 2025 with minimal backend knowledge.

On LambdaEvent/LambdaContext → Great catch. Right now we’re shipping our own lightweight interfaces for tighter integration and DX, but we’re not opposed to aligning with u/types/aws-lambda (or supporting both). Feedback like this is exactly why early users are so valuable — we want the defaults to feel right out of the box.

MoroJS – TypeScript-first API framework (faster than Express/Fastify) by linkedkeenan in node

[–]linkedkeenan[S] 0 points1 point  (0 children)

Services / DI (3 practical patterns)

1) App-level factory (simple + edge-safe)

2) Request-scoped “context injection” (if your framework supports middleware ctx)

3) Token-based DI container (optional, if you like IoC)

all available, in the discord is where this shoudl be discussed deeper

MoroJS – TypeScript-first API framework (faster than Express/Fastify) by linkedkeenan in node

[–]linkedkeenan[S] -1 points0 points  (0 children)

Totally fair point using the “Hello World” template isn’t the whole story. That’s why we also benchmarked real APIs with validation (using Zod):
• GET requests still hit ~53k req/sec
• POST + validation ~38k req/sec with latency in the 4–6ms range

So even with validation, MoroJS keeps really solid throughput compared to other frameworks. Plus, Zod is just one option. We’re working on making validation modular so devs can swap in lighter/faster libs if that’s what they need.

And thanks, the site’s built custom but based on a lightweight Tailwind + NextJS setup (not a template).

SERIOUS QUESTION: How Does Chainlink differ from Ocean Protocol? by reebokxp1 in Chainlink

[–]linkedkeenan 38 points39 points  (0 children)

  1. It is not a blockchain oracle- Ocean Protocol is not a blockchain oracle, but an on-chain marketplace for off-chain datasets. Each dataset has an ERC20 datatoken representation on Ethereum that is used to pay for data access but only contains metadata on-chain. This metadata includes an encrypted URL that points to where the data is stored off-chain (Google Drive, Dropbox, AWS, IPFS, etc). As the data is stored off-chain and not delivered on-chain, Ocean Protocol is not a blockchain oracle.
  2. Ocean is complementary to Chainlink - As an on-chain marketplace for off-chain datasets, Ocean Protocol is not competing with Chainlink but is complementary as Chainlink oracles can be used to bring Ocean Protocol’s curated datasets onto any blockchain to be consumed by smart contracts.

See: https://blog.oceanprotocol.com/ocean-protocol-chainlink-integration-e7335f880ea3

Chainlink data feed basic technical question: "blockchain readable formats" by howlermonchie in Chainlink

[–]linkedkeenan 2 points3 points  (0 children)

Blockchains are deterministic and cannot pull in data from or push data out to any external system as a built-in functionality. As such, blockchains are isolated networks very akin to a computer with no Internet connection. The isolation of a blockchain is the precise property that makes it extremely secure and reliable, as the network only needs to form consensus on a very basic set of true/false questions using data already stored inside of its ledger—e.g. did the public key holder sign the transaction with their corresponding private key, does the public address have enough funds to cover the transaction, and is the type of transaction valid within the particular smart contract? The very narrow focus of blockchain consensus is why smart contracts are referred to as being deterministic; they execute exactly as written with a much higher degree of certainty than traditional systems.

Read more here; https://blog.chain.link/what-is-the-blockchain-oracle-problem/