transferred-stepzen-schemas VS swc

Go to stepzen.com and click on the start for free button.

Either way, I'm not too familiar with RxDB but looking at the docs you can also use StepZen to create the GraphQL layer that you use for replication. With StepZen you can build and deploy a GraphQL API based on multiple datasources (including MSSQL) in minutes. That way you only have to worry about building the logic that pulls and push replicates data to and from GraphQL. How you structure the MSSQL database would become the most important part of this project, to ensure a smooth replication.

There are multiple ways to get a GraphQL API on top off a Postgres database. If you want to have a GraphQL abstraction layer that runs as a hosted service and needs almost no code, have a look at StepZen. You can build a GraphQL API for the Postgres database by following the docs here. StepZen introspects the database (using stepzen import postgresql) and let it create the schema for you based on all the tables and columns of your database. Including a set of queries to get started with.

If you’re looking for a managed service, have a look atStepZen. You can combine multiple GraphQL schemas into one cloud GraphQL API. Instead of writing a gateway yourself, you can use SDL to merge different schemas. Besides GraphQL APIs you can also “federate” other data sources like SQL or REST

There are many of them, including StepZen which is language/framework agnostic and let you create a GraphQL server with GraphQL SDL only - in a declarative way

I’ve seen more products letting you join/merge GraphQL schemas independent of schema stitching or federation. Have a look at GraphQL Mesh or StepZen.

You can save yourself the hassle of having to build a GraphQL server, resolvers and database connections with StepZen (https://stepzen.com). It’s a product that is based solely on GraphQL SDL and you set the database connections with directives. Also, you can use it to connect other APIs

There is one thing I can say for sure: I love the spirit of open source. I've had a wonderful time working with open source communities of different sizes (e.g. Seneca-CDOT, StepZen, Appwrite, and Zulip). Fortunately, all of them are fantastic and patient with beginners.

If the only thing you're trying to do is converting a REST API to GraphQL, you should have a look at https://stepzen.com/

StepZen filed an issue about writing a GraphQL schema to integrate SpaceX REST API into their React application. I found this as an excellent opportunity for me to learn GraphQL.

First, we switched the default compiler for new projects from Babel to SWC (Speedy Web Compiler). SWC is dramatically faster than Babel and requires zero configuration. We’ll continue to support Babel in any project currently using it.

SWC

As the reference explains “**SWC** (Speedy Web Compiler) is an extensible Rust-based platform that can be used for both compilation and bundling. Using SWC with Nest CLI is a great and simple way to significantly speed up your development process.”

This is specifically about breaking the myth that performing expensive self-contained operations (e.g, parsing GraphQL) in a native extension (C, Rust, etc.) is always faster than the interpreted language.

The JS ecosystem has the same problem, people think rewriting everything in Rust will be a magic fix. In practice, there's always the problem highlighted in the post (transitioning is expensive, causes optimization bailouts), as well as the cost of actually getting the results back into Node-land. This is why SWC abandoned the JS API for writing plugins - constantly bouncing back and forth while traversing AST nodes was even slower than Babel (e.g https://github.com/swc-project/swc/issues/1392#issuecomment-...)

Why Speedy Web Compiler ?

FTA is a TypeScript static analysis tool built on the speedy foundations of swc. FTA is fast; capable of analyzing more than 150 files per second on typical hardware, it offers a powerful addition to your code quality toolkit.

Very cool! I'm curious, is this intended for dev tooling?

For example, I could see this (or something similar) being useful as the engine for a typescript language server that would be faster than the standard one

But if it's not aimed at 1:1 with tsc, would it be intended more for something like swc[1]?

Or what would you expect people to use this for, besides just being a cool project to learn from?

[1] https://github.com/swc-project/swc

This is... good news, but I still cannot fathom using the default Typescript compiler for regular development. Seriously, leave the type-checking to your IDE and CICD chain, and switch to using tsx (https://www.npmjs.com/package/tsx) or swc (https://swc.rs/) and you will _immediately_ notice the difference in speed and productivity.