Connect and consume Azure services and third party services Flashcards
What is Azure API Management? What are the key systems?
A cloud offering for helping organizations publish APIs to external, partner, and internal developers.
The API Gateway
The Azure Portal
The Developer Portal
Products
What is the API gateway?
It is the endpoint that:
- Accepts API calls and routes them to your backends
- Verifies API keys, JWT tokens, certificates, and other credentials
- Enforces usage quotas and rate limits
- Transforms your API on the fly without code modifications
- Logs call metadata
What is the Azure portal?
The administrative interface where you set up your API program:
- Define or import API schema
- Package APis into products
- Setup policies
- Manage users
What is the developer portal?
A place were developers can:
- Read api documentation
- Try out an API via the interactive console
- Get an account and subscribe to get API keys
- Access analytics on their usage
What are products in API management?
Groupings of APIs that developers subscribe to in order to access those APIs. They can be Open or Protected
Discuss Groups in Product management
Groups come in three forms:
- Administrators - Azure subscription administrators.
- Developers - Authenticated developer portals that build applications using the APIs.
- Guests - Unauthenticated developer portal users, such as prospective customers. View don’t call.
What are policies for APIm?
Policies allow the azure portal to change the behavior of the API through configuration. Generally XML / JSON formating.
How are policies configured?
They have four parts - inboud, backend, outbound, and on-error
Generally:
What is an Advanced Policy?
Advance policies can:
- Control flow
- Forward requests
- Limit concurrency
- Log to Event Hub
- Mock response
- Retry
Show examples of the various advanced policies:
Control flow:
Forward request:
Limit concurrency:
What is a subscription key?
A way to secure the APIs to only those that have a validly generated key. They are auto-generated anc can be passed through in the headers of a client request.
What are the two types of queue mechanisms in Azure? What are the differences?
Service Bus queues - Part of broader messaging infrastructure. Integrate with applications or components. Span lots of protocols, contracts, domains, networks.
Storage queues - Part of Azure Storage infrastructure - allow you to store large number of messages.
When would you consider using service bus queues?
- You solution needs to receive messages without having to poll the queue
- You solution requires to provide a guaranteed FIFO
- You solution needs to support automatic duplicate detection
- You want your application to process messages as parallel long-running streams
- Your solution requires transactional behavior
- Your application handles messages that can exceed 64 KB but won’t approach 256KB limit
When would you consider using storage queues?
- Your application must store over 80 GB of messages
- Your application wants to track progress for processing a message in the Queue
- You require server side logs of all the transactions executed against your queues.
What are some advanced features of Service buses?
- Message sessions
- Autoforwarding
- Dead-letter queue
- Scheduled delivery
- Message deferral
- Batching
- Transactions
- Filtering and actions
- Autodelete on idle
- Duplicate detection
- Geo-disaster recovery