21.04
topics · Web API 300

Web API 300: topics

The Goal of Independent Deployability Fulfilled

In the previous classes, we covered patterns that will lead your team and project to the goal of “independent deployability”. Briefly, this means that you and your team can take advantage of techniques like Continuous Integration and Continuous Deployment (or Delivery) to be responsive to the business needs of your service.

We will review and extend the patterns from previous classes to help us reach this goal.

  • Designing APIs for Quick Pipeline Throughput and Optimal Developer Feedback
  • Resiliency Patterns for Integrations
  • How to Move To Practices and Patterns that Don’t Require Services To Share Databases

Reducing Coupling from Backing Services

  • Understand and Implement Event Streaming and Messaging (Kafka, Azure Service Bus, Amazon SNS/SQS, etc.) For Resilient Integration
  • The Limits of Transactional Consistency Outside of Service Boundaries
  • Understand Eventual Consistency Patterns
  • Designing Inter-Service Messages For Integration
  • Securing Inter-Service Messaging
  • Messaging Delivery Patterns (Exactly Once, At Least Once, etc.)
  • Idempotent Message Handling and Design
  • “Dead Letters”, “Outboxes”, “Inboxes”, and other Resiliency Patterns
  • Validating Messages from a Message Broker
  • Using a Transformer/Adapter To Lessen Coupling (Anti-Corruption Layer)

Service Design Patterns For Maximum Velocity

  • Using “Event-Driven Architecture” Inside Your Service
  • Event Sourcing (vs. Event Streaming)
  • Designing Events, Commands, and Read Models (Command/Query Responsibility Segregation, or CQRS)
  • Implementing Policies For Commands
  • Command Processing: Decider Pattern
  • Creating Read Model Projections and Exposing Them From Your API

Developer Testing

  • Testing Integration Scenarios with Event Streaming