Job Role

Architect

Duration

In-Person: 3 Day(s)
Virtual: 3 Day(s)

Overview

Who should take this course?


This course is for senior solution and enterprise architects who have experience with common integration approaches (like SOA) and integration technologies/platforms, and have basic knowledge and experience with the components of Anypoint Platform. It prepares you to take the MuleSoft Certified Platform Architect - Level 1 exam and includes two exam attempts.

 

Prerequisites

 

A basic knowledge and experience with the components of Anypoint Platform from one of the following:

 

Prior architecture knowledge and experience:

  • A clear understanding of the concepts and steps involved in developing software for the JVM (usually from developing in some JVM-based programming language)
  • Recent experience as an architect for a cloud platform software development initiative using any technology stack
  • A full understanding of the fundamental ingredients of enterprise integration including interface definitions and contracts; data encoding using XML or JSON; REST APIs or SOAP web services; SQL or NoSQL database access; message-passing using JMS, AMQP or similar; network protocols like TCP/IP, HTTP and HTTPS; single-resource transactions
  • Familiarity with the purpose of common components of enterprise and cloud technology architectures including identity providers, load-balancers, and name servers
  • Familiarity with basic security concepts including certificates and encryption at rest and in transit

 


When you complete this course, you will be able to:


  • Break down functional requirements into business-aligned, versioned APIs with effective granularity and API data model.
  • Direct creation and publication of API-related assets using RAML and Anypoint Platform components.
  • Architect for non-functional requirements on the level of API invocations and API implementations using components of Anypoint Platform.
  • Architect for specific requirements by augmenting API-led connectivity with event-driven architecture.
  • Select Anypoint Platform deployment options.
  • Advise on effective use of the automation capabilities of Anypoint Platform for DevOps, CI/CD, and testing.
  • Advise on the establishment and operation of a Center for Enablement (C4E).

Class Registration

Lessons and Topics

Introducing the course

  • Define Catalyst
  • Describe how this course is aligned to parts of Catalyst
  • Use essential course terminology correctly
  • Recognize the ArchiMate 3 notation subset used in this course

Introducing MuleSoft, the application network vision, and Anypoint Platform

  • Articulate MuleSoft's mission
  • Explain MuleSoft's proposal for closing the increasing IT delivery gap
  • Describe the capabilities and high-level components of Anypoint Platform

Establishing organizational and platform foundations

  • Advise on establishing a C4E and identify KPIs to measure its success
  • Choose between options for hosting Anypoint Platform and provisioning Mule runtimes
  • Describe the set-up of organizational structure on Anypoint Platform
  • Compare and contrast Identity Management and Client Management on Anypoint Platform

Identifying, reusing, and publishing APIs

  • Utilize universal API management to deliver products and projects derived from initiatives
  • Identify APIs needed to implement these products
  • Assign each API to one of the three tiers of API-led connectivity
  • Reason about composition and collaboration of APIs
  • Reuse APIs wherever possible
  • Publish APIs and related assets for reuse
  • Understand how API Community Manager helps build developer communities around APIs in an application network

Enforcing NFRs on the level of API invocations using Anypoint API Manager

  • Explain how to control API invocations with API Manager
  • Use API policies to enforce non-functional constraints on API invocations
  • Choose between enforcement of API policies in an API implementation, an API proxy, or Anypoint Service Mesh
  • Register an API client for access to an API version
  • Describe when and how to pass client ID and secret to an API
  • Govern APIs as part of the API lifecycle
  • Describe how Anypoint Security enables de-tokenization and additional Edge policies in Anypoint Runtime Fabric deployments

Designing effective APIs

  • Appreciate the importance of contract-first API design and RAML fragments
  • Opt for semantic API versioning and where to expose what elements of an API’s version
  • Choose between Enterprise Data Model and Bounded Context Data Models
  • Consciously design System APIs to abstract from backend systems
  • Apply HTTP-based asynchronous execution of API invocations and caching to meet NFRs
  • Identify idempotent HTTP methods and HTTP-native support for optimistic concurrency

Architecting and deploying effective API implementations

  • Describe auto-discovery of API implementations implemented as Mule applications
  • Appreciate how Anypoint Connectors serve System APIs in particular
  • Describe CloudHub and CloudHub 2.0
  • Choose Object Store in a CloudHub setting
  • Apply strategies that help API clients guard against failures in API invocations
  • Describe the role of CQRS and the separation of commands and queries in API-led connectivity
  • Explain the role of event sourcing

Augmenting API-Led connectivity with elements from event-driven architecture

  • Selectively choose elements of event-driven architecture in addition to API-led connectivity
  • Make effective use of events and message destinations
  • Impose event exchange patterns in accordance with API-led connectivity
  • Describe Anypoint MQ and its features
  • Apply event-driven architecture with Anypoint MQ to address specific NFRs

Transitioning into production

  • Locate API-related activities on a development lifecycle
  • Interpret DevOps using Anypoint Platform tools and features
  • Design automated tests from the viewpoint of API-led connectivity and the application network
  • Identify the factors involved in scaling API performance
  • Use deprecation and deletion of API versions in Anypoint Platform
  • Identify single points of failure

Monitoring and analyzing the behavior of the application network

  • Recognize Anypoint Monitoring capabilities and metrics
  • Explain the origins of data used in monitoring, analyzing, and alerting on Anypoint Platform
  • Describe and classify metrics collected by Anypoint Platform on the API invocation level
  • Analyze the application network with Anypoint Visualizer
  • Implement API analytics within and outside of Anypoint Platform
  • Exemplify API invocation alerts based on key metrics for all tiers of the API-led connectivity
  • Critique the reliability of the application network utilizing metrics from Anypoint Monitoring
  • Organize documentation for operational excellence