Reactive Application Development
Douban
Duncan K. DeVore / Sean Walsh …
visão geral
Modern distributed applications run in environments that may include thousands of processors, web and mobile clients, hybrid cloud deployments, and petabytes of data. The traditional patterns and practices for enterprise application development simply can't deliver the millisecond response times and near-perfect reliability these systems require. Reactive applications meet these demands by employing a loosely-coupled system of independent, isolated components that communicate via asynchronous message passing. These systems are highly responsive to changes in load, extremely fault tolerant through self-healing, and designed to elastically scale. For developers working in JVM-based systems, the Typesafe stack, anchored by the Java and Scala programming languages and the Akka toolkit and runtime, gives developers the tools to build a production-ready reactive application platform.
conteúdo
PART 1 FUNDAMENTALS
1. WHAT IS A REACTIVE APPLICATION?
1.1. Why do I need a reactive application?
1.1.1. Distributed Computing
1.1.2. Cloud Computing
1.2. Web shopping cart: complexity beneath the surface
1.2.1. Monolithic architecture: difficult to distribute
1.2.2. Reactive architecture: distributable by default
1.2.3. Understanding the Reactive Architecture
1.2.4. Monolithic shopping cart: creating an order
1.2.5. Event Sourcing: A banking example
1.2.6. Reactive shopping cart: creating an order with event sourcing
1.3. What are reactive applications reacting to?
1.4. What You Will Learn
1.5. Summary
2. SELECTING A TOOLKIT
2.1. What is Akka?
2.2. Akka Today
2.2.1. Message Driven
2.2.2. Resilient and Elastic
2.2.3. Responsive
2.2.4. Big Data
2.3. Akka terminology
2.3.1. Concurrency and Parallelism
2.3.2. Asynchronous and Synchronous
2.3.3. Blocking, Registered Callback, Future, and Message Passing
2.3.4. Contention
2.3.5. Share Nothing
2.4. The Actor Model
2.4.1. State
2.4.2. Actor Reference
2.4.3. Asynchronous Message Passing
2.4.4. The Mailbox
2.4.5. Behavior and The Receive Loop
2.4.6. Supervision
2.5. The Actor System
2.5.1. Hierarchical Structure
2.5.2. Supervision
2.5.3. Actor Paths
2.5.4. Actor Lifecycle
2.5.5. Microkernel Container
2.6. Summary
3. THE AKKA BASIC TOOLKIT
3.1. Bookstore Analogy
3.2. Message Driven
3.2.1. Immutable Messages
3.2.2. Asynchronous Concurrency with Actors
3.2.3. Running the Application
3.3. Elasticity
3.3.1. Akka Routing
3.3.2. Librarian Router
3.3.3. Running the Application
3.4. Resilience
3.4.1. Faulty Librarian Actor
3.4.2. Running the Faulty Application
3.4.3. Librarian Supervision
3.4.4. Running the Application
3.5. Summary
4. DOMAIN DRIVEN DESIGN
4.1. What is domain-driven design?
4.1.1. The big ball of mud
4.1.2. Bounded Context
4.1.3. Ubiquitous language
4.1.4. Entities, Aggregates and Value Objects
4.1.5. Services, Repositories and Factories
4.1.6. Anti-corruption Layers
4.1.7. Layered Architecture
4.1.8. Sagas
4.1.9. Shared Kernel
4.2. An Actor-based domain
4.2.1. A Simple Akka Aircraft Domain
4.2.2. The actor
4.2.3. The Process Manager
4.3. Summary
5. THE AKKA ADVANCED TOOLKIT
PART 2 BUILDING A REACTIVE APPLICATION
6. THE "C" IN CQRS AND EVENT SOURCING
7. THE "Q" IN CQRS
8. A REACTIVE INTERFACE
9. MODULARITY AND MICROSERVICES
10. BIG DATA AND DATA REPLICATION
PART 3 SECURITY AND DEVELOPMENT
11. SECURITY
12. THE DEPLOYMENT ENVIRONMENT
13. THE IMPORTANCE OF TESTING
