API Management Fundamentals for Architects

PI Management Fundamentals for Architects

With two intensive days of learning that combine theoretical concepts and hands-on labs, we will cover the fundamentals of the multifaceted process of API management. We also include MuleSoft, Apigee, analytics, security, microservices, and much more in this comprehensive course.

This course targets Business Analysts, IT Architects, Technical Managers and Developers

Benefits

• Understanding Google's Geocoding API
• Comparing API Management Platforms
• Working with Mule Soft Anypoint Studio
• Understanding Monolith vs Microservices Design
• Data Availability and Consistency
• Using AWS API Gateway
• Using API Management on Azure

Outline

1. API Management Introduction
2. Data is King
3. Data Exchange Payloads
4. API Management Defined
5. The Driving Forces
6. APIs to Monetize on Your Information Assets and Services
7. The Traditional Point-to-point Integration Example
8. It Raises Some Questions …
9. The Facade Design Pattern
10. API Management Conceptual Architecture
11. Other "Complimentary" Services
12. What Else is Needed?
13. The Digital Transformation Strategies
14. Gartner's Magic Quadrant for Full Life Cycle API Management
15. Apigee
16. MuleSoft
17. Amazon Web Services (AWS)
18. WSO2
19. IBM API Connect
20. KONG
21. Summary
22. Mulesoft & WSO2 Overview
23. What is MuleSoft?
24. MuleSoft AnyPoint Platform
25. MuleSoft Cloud Community Manager
26. Anypoint Studio
27. Advanced REST Client (ARC)
28. What is WSO2?
29. User Roles in WSO2 Workflows
30. The Main Client-Facing Web Applications and Capabilities
31. WSO2 Main Features
32. The API Gateway
33. Workflow for Invoking an API
34. Workflow for Creating an API
35. Access Control and Security
36. User Authentication via Access Token
37. Manage and Scale API Traffic
38. Monitor and Monetize
39. WSO2 Cloud
40. Summary
41. Apigee Overview
42. What is Apigee?
43. The Big Picture
44. API Consumers
45. Apigee Main Components
46. Apigee Edge API Management Platform Functional Diagram
47. Apigee Capabilities and Actors
48. Apigee Policies for Traffic Management and Data Transformation
49. Apigee Sense
50. Developer Portal
51. Apigee Monetization
52. Core Monetization Components
53. API Runtime
54. API Proxies
55. API Proxy Virtual Hosts
56. Flows
57. OAuth 2.0 Integration
58. API Beauty (an API Runtime's Capability)
59. API Edge Caching
60. Service Composition
61. Apigee Edge Monitoring and Analytics
62. Samples of Monitoring Charts
63. Edge Microgateway
64. Edge Microgateway Integration with Apigee Edge Analytics
65. Examples of Edge Microgateway Deployments (1 of 3)
66. Examples of Edge Microgateway Deployments (2 of 3)
67. Examples of Edge Microgateway Deployments (3 of 3)
68. Pricing: Standard Plan
69. Apigee Hybrid
70. Apigee Hybrid Capabilities
71. Apigee Hybrid Collaboration Diagram
72. Summary
73. API Management Analytics
74. API Metrics
75. API Proxy (API Gateway) Performance
76. The Apigee Proxy (API Service Gateway) Performance Chart
77. The Apigee Target Service Performance Chart
78. The Apigee Cache Performance Chart
79. The Apigee Error Code Chart
80. Geolocation Metric
81. The Apigee GeoMap Chart
82. Developer Engagement
83. The Apigee Developer Engagement Chart
84. Reports
85. Summary
86. RESTful Services Overview
87. Many Flavors of Services
88. SOAP or REST?
89. Understanding REST
90. Manipulation of Resources through Representations
91. Principles of RESTful Services
92. HTTP Methods
93. HTTP Status Codes
94. Related Standards: MIME
95. Anatomy of a URL
96. GET
97. The GET Method
98. Passing Parameters
99. HTTP Methods That Modify/Create Resources
100. POST
101. POST Request Example
102. POST Response Example
103. PUT
104. PUT Example - Update
105. PUT Example - Create
106. PATCH
107. Patch Example - Update
108. To PUT or POST?
109. SOAP Examples
110. A RESTful API for Tracking Video Games
111. What is gRPC?
112. How It Works
113. gRPC Request - Response Diagram
114. REST vs. gRPC
115. So, REST or gRPC?
116. Summary
117. Describing RESTful APIs
118. Describing RESTful APIs
119. History
120. Ad-hoc Interface definitions
121. Modern Choices
122. Stacking Up Open API vs RAML
123. Open API vs RAML: Advantages and Disadvantages
124. RAML
125. Build A RAML API Description
126. ROOT
127. List Resources
128. Define Methods
129. Define Query Parameters
130. Enter Responses
131. Open API (Swagger)
132. Swagger Versions
133. Swagger Editor
134. Swagger Codegen
135. Swagger UI
136. OpenAPI Service Description
137. Pretty Printed OpenAPI Service Definition
138. Summary
139. Securing APIs
140. What are the Security Domains?
141. How to Secure an API?
142. DDoS Protection
143. Authentication
144. OAuth2 Overview
145. OAuth Components
146. OAuth Authentication and Authorization Overview
147. OAuth Collaboration Diagram
148. Example: OAuth Client Credentials Grant with Apigee Edge
149. Getting Authorization Code Through a Federated External Directory (Facebook or Google)
150. What is Security Assertion Markup Language (SAML)?
151. SAML 2.0 Web SSO Authentication
152. SAML vs. OAuth2
153. Identity mediation
154. Encryption of Data in Transit with TLS
155. Key and Certificate Management
156. Threat Detection
157. Apigee Content-based Security
158. JSON Web Tokens (JWT)
159. How JWT Works
160. OAuth vs JWT
161. Data-masking
162. Last-mile security
163. Summary
164. Microservices Architecture Overview
165. What is a "Microservice"?
166. Principles of Microservices
167. Properties and Attributes of Microservices
168. Benefits of Using Microservices
169. The Microservices Architecture
170. Microservices Architecture vs SOA
171. The ESB Connection
172. Microservices Architecture Benefits
173. Microservices Architecture Choices and Attributes
174. Example: On-Line Banking Solution Based on MsA
175. Distributed Computing Challenges
176. Replaceable Component Architecture
177. What Can Make a Microservices Architecture Brittle?
178. Summary
179. Designing and Implementing Microservices
180. Two Types of IT Projects
181. What is In Scope for a Robust Microservices Design?
182. Scoping Your Microservice via the Bounded Context
183. Scoping Your Solution's Microservices Architecture
184. External / Shared and Internal Service Models
185. General Architectural and Software Process Organizational Principles
186. Loose Coupling, the OOD Perspective
187. Crossing Process Boundary is Expensive!
188. Cross Cutting Concerns
189. More Cross Cutting Concerns
190. To Centralize or Decentralize Client Access?
191. Decentralized Client Access
192. Centralized Client Access
193. The Facade Pattern
194. The Facade Service Conceptual Diagram
195. The Service Mesh Integration Pattern
196. Istio
197. Mesh Pros and Cons
198. Service-to-Service Communication with Mesh
199. The Naked Objects Architectural Pattern
200. When to Use Naked Objects Pattern
201. Dealing with the State
202. How Can I Maintain State?
203. Micro Front-ends (a.k.a. MicroUI)
204. How can MicroUI Help Me?
205. Your Clients Are Diverse
206. The "Rich Client" - "Thin Server" Paradigm
207. The "Rich Client" - "Thin Server" Architecture
208. RIA as a Driving Force to Turn the "Thin Server" into a Set of Microservices
209. Design for Failure
210. Resilience-Related Design Patterns
211. The Immutable Infrastructure Principle
212. Implementing Microservices
213. Microservice-Oriented Application Frameworks and Platforms
214. Embedding Databases
215. Embedded Java Databases
216. Summary
217. Lab Exercises
218. Understanding Google's Geocoding API (Research Project)
219. Comparing API Management Platforms (Research Project)
220. Working with MuleSoft Anypoint Studio
221. Qwiklabs
222. Monolith vs Microservices Design
223. Data Availability and Consistency
224. Using AWS API Gateway (Optional)
225. Using API Management on Azure (Optional)

Required Prerequisites

Participants should have the understanding of software design principles and modern choices for application deployment.

‍