This week's book giveaway is in the JavaScript forum.
We're giving away four copies of Cross-Platform Desktop Applications: Using Node, Electron, and NW.js and have Paul Jensen on-line!
See this thread for details.
Win a copy of Cross-Platform Desktop Applications: Using Node, Electron, and NW.js this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Reactive Design Patterns: what is reactive design?  RSS feed

 
praveen kumaar
Ranch Hand
Posts: 456
22
Android Chrome Eclipse IDE Google App Engine Java Notepad Oracle Ubuntu Windows
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
First of All,A warm Welcome to CodeRanch!
My question is what is the meaning of REACTIVE DESIGN.You call it a Pattern so are they for solving some type of problems?if yes what kind of problems,i doesn't mean any specific problem but may be those problems belongs to some family(or topic).
Where did you focus more in your book(concept).for whom is your book written?
Can a beginner read your book?

Kind Regards,
Praveen.
 
Brian Hanafee
Author
Greenhorn
Posts: 11
5
Mac Scala
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The core principles of reactive design are described in the Reactive Manifesto. Reactive design itself is too broad to call a pattern, in the same way that object-oriented is too broad to call a pattern. It's an approach. Within the approach, there are many patterns. The book describes what we consider the most important of the Reactive patterns.

The general category of problems that are addressed by Reactive patterns are those of distributed systems. At the scales of modern systems, the possibility of failure of one or more of the parts is quite high. Trying to maintain the illusion that remote interactions are simple synchronous calls just like a local function call leads to brittle systems that are hard to scale and that do not handle failure at all well. Asynchronous programming is hard. Reactive design provides a layer of abstraction so that the hardest parts of asynchronous programming are hidden. Developers can focus on the domain models.

An experienced developer who is beginning to learn about Reactive design would be comfortable reading the book. A beginning developer would be better served building a solid foundation in programming, then approaching Reactive as part of learning to handle distributed systems in general.
 
praveen kumaar
Ranch Hand
Posts: 456
22
Android Chrome Eclipse IDE Google App Engine Java Notepad Oracle Ubuntu Windows
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for your answer Brian.

Kind Regards,
Praveen.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!