stepci VS myria

Location: EU, Germany

Remote: Yes

Willing to relocate: Yes

Technologies: HTML, CSS, TailwindCSS, JavaScript, TypeScript, Node.js, React/Next.js, Vue/Nuxt, GraphQL, REST, Postgres, Git, AWS, Docker + K8s

GitHub: https://github.com/mishushakov

LinkedIn: https://linkedin.com/in/mishushakov

Email: hey at mish.co

Most recently, I worked at Step CI a Technical Founder and authored the API-Testing Framework (https://stepci.com) and Garph (https://garph.dev), a full-stack API-Framework, which brings the developer-experience of tRPC to GraphQL.

My passion is in making tools developers love using and make them more productive.

For automated testing, you should give Step CI (https://github.com/stepci/stepci) a try

Ps. I helped build it

The problem is that you can import commonjs modules in ESM but not the other way around. For stepci (https://stepci.com) we have chosen to not support ESM for this very reason. We want that the library “just works” for all our users

Hopscotch is not a Postman fork as far as I know.

You can also do request chaining with Step CI (https://stepci.com) and Hurl (https://hurl.dev)

There’s also Step CI: https://stepci.com

Disclaimer: I’m one of the authors

It's a config driven uptime monitoring service powered by Step CI, an open source API testing framework.

You might try DiY-ing it with this open-source framework - https://stepci.com/

Location: Seattle area

Remote: Yes

Willing to relocate: No

Technologies: C/C++, Python, Java, SQL, Linux, DB engines, systems programming

Résumé/CV: https://www.linkedin.com/in/tobinbaker/, https://www.dropbox.com/scl/fi/0ai2g6loja08p90hwj6zq/TobinBa..., https://github.com/senderista/, https://senderista.github.io/atomik-website/

Email: [email protected]

I've been working for the last 3 years on an in-memory MVCC DB engine in C++, built from scratch. The engine incorporates several innovative design features. It has completely nonblocking transaction open and commit; incremental, concurrent, and nonblocking GC; and direct shared-memory access to data from client processes with zero-copy reads. All critical paths are lock-free and some are wait-free (e.g., transaction validation). Scalability is a work in progress but single-thread update throughput is ~5M TPS. I've also designed and partially implemented a high-level API over this database to expose transactional programming to C++ developers who would never normally use a database: https://senderista.github.io/atomik-website/.

Before starting this project, I worked on a distributed analytical database, supporting multiple scientific users:

https://myria.cs.washington.edu/