Love the landing page design! I'm excited to give it a whirl this evening.
Initially, I started to compare PicoMQ to https://github.com/s2-streamstore/s2. If you're familiar with them, how would you compare PicoMQ to S2?
11 karma · joined February 20, 2020
Initially, I started to compare PicoMQ to https://github.com/s2-streamstore/s2. If you're familiar with them, how would you compare PicoMQ to S2?
The product seems great if you're familiar with the data and schemas, but for a product like this to appeal to teams and have impact for anyone on a team there needs to be (1) a way to provide system prompts and add business/product context to the underlying schema (2) a way to store historical queries that can be used as a starting point for other users, much like saving a query, model, or dashboard in a BI tool
I hope to see more news about CamelAI in the future. Good luck!
- The main use cases I can think of for nap are (a) blackbox integration tests [0] and (b) a trackable HTTP request library via git. At my previous job, we built a similar tool (not nearly as feature rich as nap) to compare stable and candidate API versions. We'd run the library of HTTP request against each version and report on any difference in assertions.
- Scripting makes sense in the form of hooks imo. As a user, I would want to execute Javascript pre-request, post-request, pre-response, post-response, etc.
- There's nothing REALLY BIG you're missing. I think the primary value here is that it's a light weight tool that can be re-used for all sorts of workflows and platforms.
[0] The blackbox integration test use case is an interesting one. There's a recent trend in Javascript-land where some tooling is being moved to Go or Rust for the sake of speed -- integration tests may benefit from improved speed and concurrency. I tend to write tons of integration tests using Jest and they add up to a noticeable amount of time when running in CI.