Module 1 Flashcards
What’s the title of Module 1? (Slide 1)
Introduction to application network & API - led connectivity
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 a web service and APIs are
-Make calls to secure & unsecured API’s
What are application networks? (Slide 50)
- It’s a network of applications, data, and devices connected with API’s to make them pluggable, and to create reusable services
What are benefits or characteristics 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 API into 3 categories
System APIs:
• connect directly to core systems of record (databases, ERP systems)
• they handle the complexity of the underlying systems & exposes their data in a reusable way
Process APIs:
• Orchestrate data & functionality from one or more system APIs to create specific business processes
Experience APIs:
• Designed to service specific user experience
• They interact directly with the user interface or client applications
Explain what web services & APIs are. (Slide 26, 29, 30, 31, 51)
APIs
• Application program interface
• provides information for how to communicate with a software component
• Defines
• Operations (what to call)
• inputs (what to send with a call)
• Outputs (what you get back from a call)
• Underlying data types
Web services
• a method of communication that allows 2 software systems to exchange data over the internet
What are the different parts and components of a web service
The web service API
The web service interface implementing the API
The web service implementation itself
What does the web service API do?
Describes how you interact with the web service
It may or may not (although 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)
What does the web service interface implementing the API do?
• is the code providing the structure to the application so it implements the API
• this may be combined with the actual implementation code
What does the web service implementation itself do?
Is the actual code and application
How many types of web services are there & what are they
There 2 main types of web services
• SOAP web services
• RESTful web services
What is a SOAP web services
• traditional, more complex type
• the communication rules are defined in an XML - based WSDL file
What is a RESTful web services
• Recent, simpler type
• uses the existing HTTP communication protocol
True or false, each project adds value to the application networks?
True
True or false, each project adds value to the application networks?
True
What are 3 layers of API in the API - led connectivity approach & put them in order
Systems API
Processed APIs
Experienced APIs
What are 3 layers of API in the API - led connectivity approach & put them in order
Systems API
Processed APIs
Experienced APIs
Which API layer corresponds to central IT, Line of Business (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- serve, reuse and consume
Which API layer corresponds to central IT, Line of Business (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- serve, reuse and consume
Exmplain what a web services & APIs are (slide 26,27,29,30,31,40,51)
APIs
-application programming interface
Provides information for how to communicate with a software component (slide 26)
It defines functionalities independent of implementations (slide 26)
Defines (slide 26)
•operations (what to call)
•inputs (what to send with a call)
•outputs (what you get back from a call)
•underlying data types
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
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
I’m web services, what factors influence the data exchange between software systems? (Slide 29)
• Bridging protocols: (HTTP,SOAP, Rest)
• Platforms: (windows, Linux)
• Programming languages (Java,python, C#)
• hardware architecture
What do people mean when they say API (slide 27)
•an API interface definition file (API SPECIFICATION)
• a web service
- the actual API implementation you make calls to or the interface of that API implementation
• an API proxy
- an application that restores access to a web service, restricting access and usage through the use of an API gateway
Make calls to secured & unsecured APIs (slide 40,41,42,43)
What needs to be specific to make API calls? (Slide 40)
• HTTP METHOD
• REQUEST HEADERS
• REQUEST BODY
What are the tools for testing API calls? (Slide 40)
• 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: Secure & require authorization
• Unsecured APIs: may be public and require no authorization
What do RESTful web services return in response to request/ call? (Slide 42)
• An HTTP statues code, with the response
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 create an API secured by credentials
• you can also secure an APi with other authorization protocols
• OAuth, SAML, JWT, and more
What does you use to make calls to an unsecured API (an implementation) (slide 44)
• ARC
(Advance rest client
What does the HTTp statues code provide? (Slide 42)
• client feedback for the outcome of the operation (succeeded, failed, updated)
What should a good API return? (Slide 42)
• statues codes that align with the HTTp spec (specification)
What is C4 & what are the key points involved? (Slide 18)
- it’s a cross - functional team that ensures assets are….
• Productized and published
• Consumable
• Consumed broadly
• Fully leveraged
Success for C4E is measured on? (Slide 18)
Asset consumption
