Moleculer
Nest.js
ExpressJS
KintoHub
Sails.js
Loopback by RogueAmoeba
hapi.js
Epsagon
goa
KintoHub
Istio
Epsagon
Interspect
ts-rest
Fern
gimbap
Moleculer goaBased on our record, goa should be more popular than Moleculer. It has been mentiond 27 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
My goto for this kind of task is moleculer: https://moleculer.services/ Fast, battle tested, vue2-like approach, great documentation, good community. The automatic indipendent-scalability as an option is usually the main selling point of these solutions, but honestly I think the real pro is the "composition" approach, which is essential if you want to keep a clean and well-organized codebase. On this regard, I... - Source: Hacker News / 11 months ago
If you’re using k8s, check out https://moleculer.services and this would likely solve what you’re looking for. Source: about 1 year ago
Molecular – Progressive Microservices Framework for Node.js. Source: about 1 year ago
While you’re delving into microservices, check out Moleculer https://moleculer.services. Source: over 1 year ago
I almost can’t believe I haven’t seen it mentioned here before, but adding Moleculer into your node project (if it’s clustered/k8s’d) will literally solve many single threaded problems, not to mention tons of other scalability issues. https://moleculer.services/. Source: over 1 year ago
My experience of Golang is that dependency injection doesn't really have much benefit. It felt like a square peg in a round hole exercise when my team considered it. The team was almost exclusively Java/Typescript Devs so it was something that we thought we needed but I don't believe we actually missed once we decided to not pursue it. If you are looking at OpenAPI in Golang I can recommend having a look at... - Source: Hacker News / 10 days ago
See https://goa.design/. It automates all the comms stuff, so you just write: 1) a design file showing your functions, 2) an implantation of those functions, and 3) a very generic "main.go" (basically the same for all your services) that decides "how is this exposed over gRPC or REST or other comms?". The rest of the code is generated. Source: 5 months ago
If you really need a framework, you can take a look at Echo or, for a contract-first approach, https://goa.design/. Source: 10 months ago
Few folks in here are (rightly) frustrated with the code generation story and broader tooling support around the OpenAPI standard. I've found a few alternative approaches quite nice to work with: - Use a DSL to describe your service and have it spit out the OpenAPI spec as well as server stubs. In other words, I wouldn't bother writing OpenAPI directly - it's an artifact that is generated at build time. As a Go... - Source: Hacker News / 11 months ago
One of the biggest issues I see is that you are using the same models for API as you are for the database. That wouldn’t fly in a real work system. And even though your doing simple CRUD I would introduce another layer for business logic. You should never have the Controller calling you database code directly. It never “stays” that simplistic. One of the easiest ways to deal with this is to use... Source: 12 months ago
Nest.js - A progressive Node.js framework for building efficient, reliable and scalable server-side applications.
KintoHub - A modern fullstack app platform
ExpressJS - Sinatra inspired web development framework for node.js -- insanely fast, flexible, and simple
Istio - Open platform to connect, manage, and secure microservices
Epsagon - Track costs and fix your serverless application.
Sails.js - Realtime MVC Framework for Node.js