The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
Wisper Alternatives
Similar projects and alternatives to wisper
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
govuk-puppet
Discontinued Decommissioned: Puppet manifests that used to provision the legacy GOV.UK stack.
-
-
-
-
MeiliSearch
A lightning-fast search API that fits effortlessly into your apps, websites, and workflow
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
-
-
-
-
-
-
-
-
-
Waterfall
A slice of functional programming to chain ruby services and blocks, thus providing a new approach to flow control. Make them flow! (by apneadiving)
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better wisper alternative or higher similarity.
wisper reviews and mentions
Posts with mentions or reviews of wisper.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-02-21.
-
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.
-
A note from our sponsor - WorkOS
workos.com | 28 Apr 2024
Stats
Basic wisper repo stats
6
3,229
1.5
about 2 months ago
krisleech/wisper is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of wisper is Ruby.
Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com