0%

Book Description

Enterprises are busy transforming themselves by building applications capable of handling massive scale, enormous amounts of data, or both. The good news? There’s an unprecedented choice of open source technologies available to pursue these next-generation applications. In this report, enterprise architects and tech leads will examine the factors driving so many organizations to build reactive systems for cloud native development.

Grace Jansen and Peter Gollmar from IBM examine how the reactive architectural style enables microservices-driven applications to react better to their surroundings and to each other. You’ll learn the key patterns of reactive systems and draw distinctions between implementations offered by various toolkits and frameworks.

  • Learn how reactive systems handle web and mobile commerce and data-driven decisions
  • Understand what makes reactive systems reactive: Which tools or implementations do you need to attain reactivity?
  • Explore concurrency and parallelism with multithreading, the reactor pattern, the multireactor pattern, and the actor model
  • Learn how reactive works with your enterprise application and understand when a reactive system is the right choice

Table of Contents

  1. Foreword
  2. Preface
  3. 1. The Journey to Reactive Systems
    1. Microservices: So Many Choices
    2. When and Where Are Reactive Systems Applicable?
      1. Web/Mobile Commerce
      2. Data-Driven Decisions
  4. 2. Defining Reactive Systems
    1. The Need for a Manifesto
    2. Reactive Systems Must Be…
    3. Events Versus Messages
    4. Scale Matters
      1. Attempting to Program Your Way into the Reactive Trend
      2. Reactive Streaming
  5. 3. Your Toolbox to Reactive
    1. Getting Responsive: Concurrency and Parallelism 
    2. Multithreading
    3. The Reactor Pattern
    4. The Multireactor Pattern
      1. Vert.x (Verticals) 
    5. The Actor Model
    6. Akka 
      1. Summary
  6. 4. Putting Your Reactive Toolbox to Work
    1. Going from Services to Systems: Being Message Driven
    2. Distributed Infrastructure 
    3. Orchestrated Cloud Infrastructure
    4. Reactive Meets Machine Learning
    5. Conclusions
      1. When Is Reactive Systems the Right Choice?
      2. How to Get Started
3.237.189.116