Module 1 Review Flashcards
What are the objectives of Module 1?
(Slide 2)
- Explain what application networks are and their benefits
- Describe how to build application networks using API-led connectivity
- Explain what web services and APIs are
- Make calls to secure and unsecured APIs
What are application networks?
(Slide 50)
It’s a network of applications, data, and devices connected with APIs to make them pluggable and to create reusable services
What are the benefits of application networks?
(Slide 24)
- Emerges bottom-up via self service
- Provides visibility, security and governability at every API node
- It’s reasonable: It bends, not breaks - built for change
Describe how to build application networks using API-led connectivity
(Slide 14, 15)
- You need to organize APIs into 3 categories
- Systems API
- Process API
- Experience API
What is systems API?
(Slide 14, 15)
- It connects directly to core systems of record (databases, ERP systems)
- They handle the complexity of the underlying systems and expose their data in a reusable way
What is process APIs?
(Slide 14, 15)
- Orchestrate data and functionality from one or more system APIs to create specific business processes
- They handle business logic and processes, ensuring data is combined or transformed as needed
What is experience APIs?
(Slide 14, 15)
- Designed to serve specific user experience
- They interact directly with the user interface or client applications
Explain what an API is
(Slide 26, 51)
- Application Programing Interface
- Provides information for how to communicate with a software component
- Defines:
- Operations (what to call)
- Inputs (what to send w/ a call)
- Outputs (what you get back from a call)
- Underlying data types
- Defines functionalities independent of implementation
Explain what a web service is
(Slide 29)
- A method of communication that allows 2 software systems to exchange data over the internet
What are the 2 main types of web services?
(Slide 31)
- SOAP web services
- Traditional, more complex
- The communication rules are defined in an XML-based WSDL file
- RESTful web services
- Recent, simpler type
- Use the existing HTTP communication protocol
What are the different parts of a web service?
(Slide 30)
- The web service API
- Describes how you interact with the web service
- It may or may not (though it should!) be explicitly defined in a file
- It could be any sort of text in any type of file but ideally should implement some standard API description language (or specification)
- The web service interface implementing the API
- Is the code providing the structure to the application so it implements the API
- This may be combined with the actual implementation code
- The web service implementation itself
- Is the actual code and application
To call web services, you need to?
(Slide 40)
- Write code to make the HTTP request
Or
- Have a tool to make the HTTP request
What needs to be specified to make API calls?
(Slide 40)
- HTTP method
- Request headers
- Request body
What are the tools for testing API calls?
- An API portal with an API console
- Advanced Rest Client
- Postman
- A cURL command-line utility
What are the types of APIs based on security features?
(Slide 41)
- Secure APIs:
- Require authentication - Unsecured APIs:
- May be public and do not require authentication
What’s the title of Module 1?
(Slide 1)
Introducing application networks and API-led connectivity
True or false, each project adds value to the application network?
(Slide 21)
True
What are some key characteristics or practices associated with secured APIs?
(Slide 41)
- You may need to provide credentials or a token
- Often a proxy is created to govern access to an API
- We will call and then later créate an API secured by credentials
- You can also secure an API with other authentication protocols
- OAuth, SAML, JWT, and more
What do RESTful web services return in response to a call?
(Slide 42)
An HTTP status code with the response
What does the HTTP status code provide to the client?
(Slide 42)
Feedback for the outcome of the operation (succeeded, failed, updated)
What should a good API return regarding HTTP status codes?
(Slide 42)
Status codes that align with the HTTP specification
Which API layers correspond to Central IT, LoB IT, and Developers? Describe the actions associated with each role.
(Slide 16)
- Central IT: Systems APIs
- Unlocking assets and decentralizing access
- LoB IT: Process APIs
- Discover, reuse assets and compose information
- Developers: Experience APIs
- Discover, self-service, reuse and consume
What is C4E and what are the key points involved?
(Slide 18, 50)
It’s a cross-functional team that ensures assets are…
- Productized & published
- Consumable
- Consumed broadly
- Fully leveraged
Success for C4E is measured on?
(Slide 18)
Asset consumption