Component Alternatives

component reviews and mentions

• A History of Clojure (2020) [pdf]
  22 projects | news.ycombinator.com | 10 Aug 2023

  * 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
  2 projects | /r/Clojure | 8 Apr 2023

  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?
  4 projects | /r/Clojure | 9 Jan 2023
• Clojure needs a Rails, but not for the reason you think
  24 projects | news.ycombinator.com | 30 Jul 2022
• [ANN] Reveal Pro 1.3.308 — sticker windows for system libraries (component, integrant, mount)
  3 projects | /r/Clojure | 14 Dec 2021

  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)
  3 projects | news.ycombinator.com | 19 Oct 2021

  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
  4 projects | /r/programming | 16 Sep 2021
• How to pass components across functions
  1 project | /r/Clojure | 19 May 2021

  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.
  17 projects | /r/rust | 1 May 2021

  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?
  13 projects | /r/Clojure | 16 Jan 2021

  https://github.com/stuartsierra/component for managing components lifecycles in projects

• A note from our sponsor - SaaSHub
  www.saashub.com | 14 Jan 2025

  SaaSHub helps you find the best software and product alternatives Learn more →