Learning
Ctrlk
  • Software Engineering Golden Treasury
  • Trail Map
  • Caching
  • Career
  • Computer Science
  • devops
  • General Paradigms
    • CAP theorem
    • designing data-intensive applications summary
    • a-philosophy-of-software-design-notes
    • Aspect oriented Programming (AOP)
    • Best Practice
    • Cargo Cult
    • Clean Code
    • Coding reflections
    • Cognitive Complexity
    • Complexity
    • Conventions
    • Design discussions
    • Design
    • Edge Cases
    • Error Handling Checklist
    • Exceptions
    • Feature Flags/toggle
    • Functional requirements
    • Last Responsible Moment
    • Lock In
    • Named Arguments
    • Naming
    • Performance Fallacy
    • Quality
    • Redesign of a system
    • Resuse vs Decoupling
    • Rules for software designs
    • Sad Paths
    • Scaling Webservices
    • Scientific Method
    • stream-processing
    • Upstream and Downstream
    • Patterns
    • Architecture
    • Design architecture aims
    • README
    • Patterns of Enterprise Application Architecture
    • Principles
    • programming-types
      • Coding to Contract/Interface
      • Links
      • Declarative vs Imperative Programming Languages
      • defensive-programming
      • Design by contract
      • Domain Specific Languages (DSL)
      • Event Driven
      • file-transfers
      • Logical Programming
      • Mutability
      • Self Healing
      • Simplicity
      • Type Driven Design
      • Value objects
      • Aspect Oriented Programming
      • Concurrent and Parallel Programming
      • Functional Programming
      • oop-design
      • Reactive Programming
        • reactive-programming
    • Projects and Software types
    • State Machines
  • Other
  • Hardware
  • Integration
  • Languages
  • Management & Workflow
  • Networks
  • Operating Systems
  • Other Topics
  • persistance
  • Security
  • Testing, Maintainablity & Debugging
  • Version Control - Git
  • ai
Powered by GitBook
On this page
  • what
  • Manifesto
  • tutorials
  • Advantages

Was this helpful?

  1. General Paradigms
  2. programming-types

Reactive Programming

  • https://www.youtube.com/watch?v=nP-UeleMgE4&list=PLRsbF2sD7JVp8vBso4ysmj-X0u6uGx1rH&index=8

    • AVoid blocking threads, avoid switching threads

    • Reactive programming is programming with asynchronous data streams.

      • Event buses or your typical click events are really an asynchronous event stream, on which you can observe and do some side effects.

  • https://gist.github.com/staltz/868e7e9bc2a7b8c1f754

what

  • https://www.scnsoft.com/blog/java-reactive-programming

    -https://www.baeldung.com/rxjava-tutorial

  • http://reactivex.io/intro.html

  • https://www.reactiveprogramming.be/

Manifesto

  • https://www.reactivemanifesto.org/

tutorials

  • https://www.journaldev.com/18948/rxjava-tutorial

  • https://www.linkedin.com/learning/reactive-java-9/what-is-reactive-programming?u=2007908

  • http://reactivex.io/tutorials.html

  • https://blog.danlew.net/2014/09/15/grokking-rxjava-part-1/

Advantages

  • https://medium.com/corebuild-software/why-you-should-learn-reactive-programming-51b6ffc31425

  • https://stackoverflow.com/questions/42062199/reactive-programming-advantages-disadvantages

PreviousNonredundant codeNextreactive-programming

Last updated 5 years ago

Was this helpful?