wisper
Hanami
wisper | Hanami | |
---|---|---|
6 | 23 | |
3,233 | 6,193 | |
- | 0.5% | |
1.5 | 7.8 | |
2 months ago | 6 days ago | |
Ruby | Ruby | |
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.
wisper
-
Publish/Subscribe with Sidekiq
Wisper: A Ruby gem providing a decoupled communication layer between different parts of an application -> I personally dislike wisper. I used it in the past and dislike the way of defining subscribers in a global way. I wanted topics to be arbitrary and each class to define what to subscribe for itself.
-
OOP vs. services for organizing business logic: is there a third way?
Wisper – the Publish-Subscribe design pattern
-
Event Store with Rails
I haven't used it, but we're also considering it in our app for quite some time. Our main issue is mostly that our codebase is super coupled, especially some older code, and using events as a means of communication between different modules of the app can be nice way of decoupling things. I think this is the most common usecase, and for this you don't necessarily even need to persist the events, and also something like wisper might be useful https://github.com/krisleech/wisper.
-
Rails Google Cloud PubSub options
Whisper (not updated since 2020)
-
How to avoid if/else with different ramifications
I would use events. Every services broadcast its results and everything that needs to listen for them. It also great to decouple dependencies between services. I like the Wisper gem : https://github.com/krisleech/wisper
-
"I'm the CTO of a Growing Rails Startup" Ask Me Anything
We follow the interactor pattern to store our business logic. So we mainly have skinny controllers, skinny models and then interactors. We also don't use ActiveRecord callbacks very much, we primarily use Wisper to broadcast events and then various domains can subscribe to the events they care about and respond accordingly.
Hanami
-
Should You Use Ruby on Rails or Hanami?
While Rails is very well-known in the Ruby community, Hanami is less so. It's a fairly new modern Ruby framework trying to take on Rails' dominance of the full-stack web framework space.
-
16 Best Ruby Frameworks For Web Development [2024]
With a clean architectural design and a primary object methodology, Hanami is counted among the best ruby frameworks that have gained popularity as an alternative to Rails. Hanami is “sorted” in design and provides small files that can be used independently to create a project stack. Hanami is lightweight and consumes fewer resources claiming 60% lesser memory than other big Ruby frameworks.
-
Is Ruby a dying language?
No, it's just no longer over-hyped. Ruby is settling into being a mature production language, similar to Python, Java, .NET, C++, etc. As you can see from the RedMonk 2023 data Ruby is very much still alive with tons of repositories on GitHub. Besides Shopify, GitHub is another big Ruby/Rails shop. Also, besides Rails, there are other new and upcoming projects like Hanami, DragonRuby, and Ronin.
-
Web Frameworks actively maintained in 2023?
Hanami 2 (hanamirb.org)
-
Enhancing development with REPLs - A practical guide
On all my application tutorials I start by setting up an application level REPL, it's basically a console script that loads all the files inside your project, if you're using a framework like Ruby on Rails or Hanami you already have a console by running the command console also.
-
Why are there so many Rails related posts here?
This is something that kind of annoys me; there's even a /r/rails sub-reddit specifically for Ruby on Rails stuff. Understandably Rails helped put Ruby on the map. Before Rails, Ruby was just another fringe language. Rails became massively popular, helped many startups quickly build their Web 2.0 sites, and become successful companies (ex: GitHub, LinkedIn, AirBnB, etc). Like others have said, "Rails is where the money is at". However, this posses a problem for the Ruby community: whenever Rails becomes less popular, so does Ruby. I wish the Ruby ecosystem wasn't so heavily centralized around Rails, and that we diversified our uses of Ruby a bit. There's of course Sinatra, dry-rb, Hanami, Dragon Ruby, SciRuby, and a dozen security tools written in Ruby such as Metasploit, BeFF, Arachni, and Ronin.
-
Two months into learning Ruby, it is the most beautiful language I ever learned
Welcome! Ruby isn't exactly "dying", but the hype/popularity is definitely fading. This is primarily because Ruby is no longer "new", most of Ruby's popularity came from Rails, and now Rails is no longer the "new hotness". However, Ruby still has lots of awesome features and lots of awesome other libraries and frameworks, such as the new fancy irb gem that uses reline, nokogiri, chunky_png, the async gems, Dragon Ruby, SciRuby, Ronin, and the new Hanami web framework.
-
OOP vs. services for organizing business logic: is there a third way?
Data Oriented Web Development with Ruby (upcoming book) by Peter Solnica, who is on the Hanami core team. Learning Hanami wouldn't be a bad idea either.
-
Understanding Clean Architecture with small Ruby libraries
After about 5 laps around Clean architecture since I came across hanami/hanami: The web, with simplicity., I'm finally getting it down in my gut, so I'll summarize.
-
Utilizando o padrão interactor no Ruby on Rails
View on GitHub
What are some alternatives?
Rails Event Store - A Ruby implementation of an Event Store based on Active Record
Sinatra - Classy web-development dressed in a DSL (official / canonical repo)
Interactor - Interactor provides a common interface for performing complex user interactions.
Roda - Routing Tree Web Toolkit
Rocketman - 🚀 Rocketman help build event-based/pub-sub code in Ruby
Ruby on Rails - Ruby on Rails
Cells - View components for Ruby and Rails.
Padrino - Padrino is a full-stack ruby framework built upon Sinatra.
Light Service - Series of Actions with an emphasis on simplicity.
Cuba - Rum based microframework for web development.
Waterfall - A slice of functional programming to chain ruby services and blocks, thus providing a new approach to flow control. Make them flow!
Volt - A Ruby web framework where your Ruby runs on both server and client