All geek questions in one place

Is Async Messaging (in particular pub / sub style messaging) viable as a domain service architecture or only in an SOA-oriented environment?

I study asynchronous messaging, and I like how it elegantly deals with some problems in certain domains and how it makes domain concepts clearer. But whether it is a viable template for generic domain-based development (at least at the service / application / controller level), or is it design overhead, so it should be limited to SOA-based scenarios such as remote services and distributed treatment?

+3
source share
3 answers

:). , , - , , , . - , - ..:).

, -; SEDA .

, ; 10 , , . , SEDA, 10 .

+5

, "".

, , . :

  • . , .
  • - , , .
  • . - .

, , . JMS-, . , . , .

+2

@BradS BTW

BTW is a way to hide middleware from your business logic , while still gaining the benefits of free communications and SEDA - with the ability to easily switch between different middleware technologies - from SEDA to JMS to AMQP to JavaSpaces to database, files or FTP etc.

+1
source

Source: https://habr.com/ru/post/1696962/

More articles:


All Articles