Moleculer Reviews

gRPC Reviews

Moleculer mentions (14)

• Make microservices look like monoliths

  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 / about 1 year ago

• How to Import/Reference a Microservice from another one

  If you’re using k8s, check out https://moleculer.services and this would likely solve what you’re looking for. Source: over 1 year ago

• Node JS Microservice Frameworks for Developing Scalable Web Apps.

  Molecular – Progressive Microservices Framework for Node.js. Source: over 1 year ago

• First time building microservice-based application

  While you’re delving into microservices, check out Moleculer https://moleculer.services. Source: over 1 year ago

• if Nodejs does not meant for CPU intensive tasks so I think it's better to avoid it from the beginning

  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: almost 2 years ago

gRPC mentions (92)

• Performance and Scalability for Database-Backed Applications

  We can take the previously mentioned idea of partitioning the database further by breaking up an application into multiple applications, each with its own database. In this case each application will communicate with the others via something like REST, RPC (e.g. gRPC), or a message queue (e.g. Redis, Kafka, or RabbitMQ). - Source: dev.to / 26 days ago

• Text-based language processing enhanced with AI/ML

  Aside from the obvious differences in client library nomenclature and use of different credentials, API usage is fairly similar. Not visually obvious is that the older platform client library calls the REST versions of the GCP APIs whereas the newer product client libraries call the gRPC versions which generally perform better... Yet another reason why the product client libraries are always recommended. - Source: dev.to / 10 days ago

• Fastly and the Linux kernel

  The open source projects Fastly uses and the foundations we partner with are vital to Fastly’s mission and success. Here's an unscientific list of projects and organizations supported by the Linux Foundation that we use and love include: The Linux Kernel, Kubernetes, containerd, eBPF, Falco, OpenAPI Initiative, ESLint, Express, Fastify, Lodash, Mocha, Node.js, Prometheus, Jenkins, OpenTelemetry, Envoy, etcd, Helm,... - Source: dev.to / 15 days ago

• Best Practices for Building Microservices with NestJS

  Choose a consistent communication protocol for inter-service communication. Common protocols include HTTP, gRPC, and message brokers like RabbitMQ or Kafka. NestJS supports various communication strategies, allowing you to choose the one that best fits your needs. - Source: dev.to / 28 days ago

• Why Did Google Choose To Implement gRPC Using HTTP/2?

  gRPC is an open-source high-performance RPC framework developed by Google. The design goal of gRPC is to run in any environment, supporting pluggable load balancing, tracing, health checking, and authentication. It not only supports service calls within and across data centers but is also suitable for the last mile of distributed computing, connecting devices, mobile applications, and browsers to backend services.... - Source: dev.to / about 1 month ago