component
Moleculer
Our great sponsors
component | Moleculer | |
---|---|---|
13 | 16 | |
2,068 | 6,016 | |
0.0% | 1.0% | |
0.0 | 7.5 | |
about 2 years ago | 6 days ago | |
Clojure | JavaScript | |
MIT License | MIT License |
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.
component
-
A History of Clojure (2020) [pdf]
* Lifecycle management: Mount, Integrant or Component (https://github.com/tolitius/mount https://github.com/weavejester/integrant and https://github.com/stuartsierra/component)
-
Generic functions, a newbie question
When you start to have multiple stateful components (the database, the HTTP server, your Redis connection, a page cache, etc.), then you'll want to use a library like component that manages their (inter-)dependencies and provides a consistent notion of lifecycle.
- What makes Clojure better than X for you?
- Clojure needs a Rails, but not for the reason you think
-
[ANN] Reveal Pro 1.3.308 — sticker windows for system libraries (component, integrant, mount)
Today I released a new version of Reveal Pro — dev.vlaaad/reveal-pro {:mvn/version "1.3.308"} — that adds sticker integration for system libraries such as mount, component and integrant!
-
Printf(“%s %s”, dependency, injection)
I agree with the main sentiment from the article. Although I do think they are discussing Inversion of control more-so than dependency injection.
One of my first languages was .net and I was never able to really understand DI in that context that well.
Actually using javascript and ducktyping made me understand what it actually was.
I remember a .net job interview where I had to write a micro-service and opted to construct the dependency graph in the main function initialising "all" the classes there. Instead of discussing the pro's and con's of that approach they berated me for not using a DI framework (No I did not land that job, but in hindsight it was the most expensive job interview I've ever had. The room was filled with 8 developers going over my code).
The main thing the article glosses over is state. something people with a functional background hide from. But if you look at something like the httpclient in .net. I think it took the .net world like 10 years to start using the httpclient properly. Scope and lifetime of those kind of objects are important. managing connection pools, retry state, throttling or the incoming http request. DI does make that kind of thing easieR (I'm not saying it makes it better)
Look at clojure's component(https://github.com/stuartsierra/component), I'm not a clojure expert by far. But it is kinda DI/IOC in a functional language.
In closing we can agree that it is underused in the right places and overused in the wrong ones.
- Forcing engineers to release by some arbitrary date results in shipping unfinished code - instead, ship when the code is ready and actually valuable
-
How to pass components across functions
https://github.com/stuartsierra/component#no-function-should-take-the-entire-system-as-an-argument
-
There are a *lot* of actor framework projects on Cargo.
Yeah like I mentioned I'm not like super sold on the everything-should-be-an-actor paradigm, but I find value in DDD + a light implementation of Components (similar to stuartsierra/component).
-
Essential libraries?
https://github.com/stuartsierra/component for managing components lifecycles in projects
Moleculer
-
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 found moleculer pretty great even for large teams.
-
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.
-
Node JS Microservice Frameworks for Developing Scalable Web Apps.
Molecular – Progressive Microservices Framework for Node.js
-
First time building microservice-based application
While you’re delving into microservices, check out Moleculer https://moleculer.services
-
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/
-
How to deal with singletons in a distributed system?
You could use a framework for this. Have a look at moleculer
-
Where can I learn to implement microservices?
I haven't used this, but it seems neat: https://moleculer.services/
-
Microservices using express js
Look into Moleculer.
-
Been playing with moleculerjs recently, and just finished my first package: a service that allows you to use any node API framework as a moleculer gateway.
Moleculer already provides an in-house http gateway, but what if you want to use an existing API, and how to maintain decoupled code when creating your gateway? This package solves both. You can create your API, passing in any services you require as dependencies. You can then bind your API to moleculer using the moleculer-universal-gateway.
-
Don’t start with microservices – monoliths are your friend
But there's more to the topic of microservices. Seems like all the conversation focuses on deployment pain. You can build a service with something like Akka or Moleculer where the modules act independently and have some message passing and resilience from each other, but they can still all live in one codebase, one process, and deployed as one unit. It works fine and isn't painful at all. And maybe down the line you decide to split the thing up into multiple processes and multiple deployment units, and that's an easy refactor because the modules are already somewhat separated.
What are some alternatives?
integrant - Micro-framework for data-driven architecture
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript 🚀
reitit - A fast data-driven routing library for Clojure/Script
Express - Fast, unopinionated, minimalist web framework for node.
mount - managing Clojure and ClojureScript app state since (reset)
AWS Lambda Router for NodeJS - AWS Lambda router for NodeJS
ultra - A Leiningen plugin for a superior development environment
seneca - A microservices toolkit for Node.js.
awesome-clojure - A curated list of awesome Clojure libraries and resources. Inspired by awesome-... stuff
AdonisJs Framework - AdonisJS is a TypeScript-first web framework for building web apps and API servers. It comes with support for testing, modern tooling, an ecosystem of official packages, and more.
Luxon - ⏱ A library for working with dates and times in JS
fastify - Fast and low overhead web framework, for Node.js