Why we need reactive and functional approaches
1.Concurrency and Parallelism
a. Pain of native threads
b. Shared Mutable State
c. locks and race conditions
2. Context switch pain
a. How cores work
b. Core pipelines and virtual registers
c. Memory levels (caches) and memory barriers (fence instructions)
d. Pain -pain -pain
3. Functional approach
a. Lazy execution
b. Carrying and functional composition
c. Pattern matching
4. Java Reactive Revolution
a. How we can define execution flows
b. RxJava2 / Reactor (with some source code examples)
c. Recursive pipelining of data flows
d. Scheduling and Backpressure
e. Why I need that if I am not Netflix
3. Blocking vs NonBlocking execution
a. Execution on thread pools with classic blocking drivers with examples
b. Execution of reactive pipelines
c. Why so drasticall difference
4. Functional Architecture
a. Event Driven Architectures
b. Stream Processing
c. Could be seen as functions composition (microservices to serverless)
d. Pattern matching in messaging routing vs strict contracts
