Decide which messages are posted to Kafka, based on entity property values or some other business logic. #5689

5 Answer(s)

• 

  0

  liangshiwei created 2 years ago

  Support Team Fullstack Developer

  Hi,

  I have enabled ABP framework to post message to Kafka using the builtin mechanism (not PublishAsync()).

  So are you manually using the Kafka API to post messages instead of EventBus?

  I may want to publish the message only if say the status = "ACTIVE" or IsExpired = false

  Can you explain in detail? thanks.

  Save Cancel
• 

  0

  tushar_ww created 2 years ago

  Hi,

  So are you manually using the Kafka API to post messages instead of EventBus?

  Sorry, I was too short in my context. We have enabled Kafka using AbpEventBusKafkaModule and *Etos and use the SaveChanges() to trigger the messages. We do not (want to) use _distributedEventBus.PublishAsync(...) to explicitly fire the message.

  I may want to publish the message only if say the status = "ACTIVE" or IsExpired = false

  Can you explain in detail? thanks.

  So, in the implementation so far, when a new entity is created a message is published immediately. But maybe I do not want the message published because an entity property IsActive = false. Later sometime, IsActive = true will happen. That time the message should be published. It doesn't matter to me if the publish of the entity happens using UpdatedEvent or CreatedEvent.

  Basically, I am looking for a mechanism to filter which messages should be posted.

  Save Cancel
• 

  0

  liangshiwei created 2 years ago

  Support Team Fullstack Developer

  Hi,

  Sorry, but there is no such filter.

  You can do something like this: https://docs.abp.io/en/abp/latest/Distributed-Event-Bus#publishing-events-inside-entity-aggregate-root-classes

  public class MyEntity : AggregateRoot<Guid>
  {
      public bool IsActive { get; private set; }
      
      public void ChangeIsActive(bool isActive)
      {
          IsActive = isActive;
          
          AddDistributedEvent(....);
      }
  }
  

  Save Cancel
• 

  0

  tushar_ww created 2 years ago

  The approach in the link seems promising, we will get it a try.

  Save Cancel
• 

  0

  liangshiwei created 2 years ago

  Support Team Fullstack Developer

  ok

  Save Cancel