tsoa
gRPC
tsoa | gRPC | |
---|---|---|
16 | 201 | |
3,136 | 40,775 | |
- | 0.6% | |
9.1 | 9.9 | |
4 days ago | 4 days ago | |
TypeScript | C++ | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tsoa
-
Create Production-Ready SDKs with Goa
Tsoa is a popular TypeScript framework similar to Goa that you may encounter in the OpenAPI ecosystem. Speakeasy has a tutorial for it, too.
- JavaScript Gom Jabbar
-
Choosing a backend API framework
Currently i am using TSOA and loving it, it gives you automatic Open API specs and data validation based on typescript interfaces. I have used Nest on previous projects but I personally don't like the decorators hell that comes with Nest, and raw express/fastify are ok and easy to use but a pain in the ass on big projects to keep swagger, validations, interfaces and DTOs all in sync.
-
Does anyone here have any experience with TSOA? (tool for OpenAPI-compliant REST APIs using TypeScript and Node)
I'm curious if anyone here has played around with or used TSOA (https://github.com/lukeautry/tsoa)?
-
Is Express.js a good idea for backend?
If you decide to go with Express/Typescript I would definitely check out TSOA. It's a nice way to build backend APIs with auto documentation.
-
Swagger without express or koa or etc
We are using TSOA to generate the docs from the code, works pretty well. https://github.com/lukeautry/tsoa
-
OpenAPI Generator allows generation of API client libraries from OpenAPI Specs
This is the best project I’ve found to that for that - https://github.com/lukeautry/tsoa. Uses decorators mainly.
If there are other such projects, please share.
-
TypeScript-based REST API template to quickly bootstrap your next project
Hello, In the last month I built a REST API template in Typescript to quickly bootstrap new projects, I tried to use the most updated modules available, I've also included a "todo" sample just to showcase how all the things work together, the main modules that I've used are: - expressjs + tsoa that allows to easily generate the OpenAPI spec without any additional steps (just declare your controllers via typescript) - class-validator to validate body requests (this is also useful as the OpenAPI will be automatically generated based on the classes that you define) - Jest for testing, I've included also unit and integrations test samples with an in-memory database
-
Automatic swagger ui for nodejs/express? (Info in comments)
Have a look at [TSOA[(https://github.com/lukeautry/tsoa). While far from perfect (I am on the lookout to find a better solution), gets the job done. And generating the entire routing is a pretty neat trick, so that's also that.
-
How popular is typescript in backend development?
tsoa Lighter weight, but also great.
gRPC
-
Golang: out-of-box backpressure handling with gRPC, proven by a Grafana dashboard
gRPC, built on HTTP/2, inherently supports flow control. The server can push updates, but it must also respect flow control signals from the client, ensuring that it doesn't send data faster than what the client can handle.
-
Reverse Engineering Protobuf Definitions from Compiled Binaries
Yes, grpc_cli tool uses essentially the same mechanism except implemented as a grpc service rather than as a stubby service. The basic principle of both is implementing the C++ proto library's DescriptorDatabase interface with cached recursive queries of (usually) the server's compiled in FileDescriptorProtos.
See also https://github.com/grpc/grpc/blob/master/doc/server-reflecti...
The primary difference between what grpc does and what stubby does is that grpc uses a stream to ensure that the reflection requests all go to the same server to avoid incompatible version skew and duplicate proto transmissions. With that said, in practice version skew is rarely a problem for grpc_cli style "issue a single RPC" usecases: even if requests do go to two or more different versions of a binary that might have incompatible proto graphs, it is very common for the request and response and RPC to all be in the same proto file so you only need to make one RPC in the first place unless you're using an extension mechanism like proto2 extensions or google.protobuf.Any.
-
Delving Deeper: Enriching Microservices with Golang with CloudWeGo
While gRPC and Apache Thrift have served the microservice architecture well, CloudWeGo's advanced features and performance metrics set it apart as a promising open source solution for the future.
-
gRPC Name Resolution & Load Balancing on Kubernetes: Everything you need to know (and probably a bit more)
The loadBalancingConfig is what we use in order to decide which policy to go for (round_robin in this case). This JSON representation is based on a protobuf message, then why does the name resolver returns it in the JSON format? The main reason is that loadBalancingConfig is a oneof field inside the proto message and so it can not contain values unknown to the gRPC if used in the proto format. The JSON representation does not have this requirement so we can use a custom loadBalancingConfig .
-
Dart on the Server: Exploring Server-Side Dart Technologies in 2024
The Dart implementation of gRPC which puts mobile and HTTP/2 first. It's built and maintained by the Dart team. gRPC is a high-performance RPC (remote procedure call) framework that is optimized for efficient data transfer.
- Usando Spring Boot RestClient
-
How to Build & Deploy Scalable Microservices with NodeJS, TypeScript and Docker || A Comprehesive Guide
gRPC is a high-performance, open-source RPC (Remote Procedure Call) framework initially developed by Google. It uses Protocol Buffers for serialization and supports bidirectional streaming.
-
Actual SSH over HTTPS
In general, tunneling through HTTP2 turns out to be a great choice. There is a RPC protocol built on top of HTTP2: gRPC[1].
This is because HTTP2 is great at exploiting a TCP connection to transmit and receive multiple data structures concurrently - multiplexing.
There may not be a reason to use HTTP3 however, as QUIC already provides multiplexing.
I expect that in the future most communications will be over encrypted HTTP2 and QUIC simply because middleware creators can not resist to discriminate.
[1] <https://grpc.io>
-
Why gRPC is not natively supported by Browsers
Even in the https://grpc.io blog says this
-
SGSG (Svelte + Go + SQLite + gRPC) - open source application
gRPC
What are some alternatives?
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript 🚀
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
Express - Fast, unopinionated, minimalist web framework for node.
Apache Thrift - Apache Thrift
fastify-openapi-glue - A plugin for the Fastify webserver to autogenerate a Fastify configuration based on a OpenApi(v2/v3) specification.
Cap'n Proto - Cap'n Proto serialization/RPC system - core tools and C++ library
Koa - Expressive middleware for node.js using ES2017 async functions
zeroRPC - zerorpc for python
routing-controllers - Create structured, declarative and beautifully organized class-based controllers with heavy decorators usage in Express / Koa using TypeScript and Routing Controllers Framework.
rpclib - rpclib is a modern C++ msgpack-RPC server and client library
Hapi - The Simple, Secure Framework Developers Trust
nanomsg - nanomsg library