What is Apigee Edge | Introduction to Apigee Edge


Apigee Edge – Table of Content

What is Apigee Edge?

Apigee Edge is an API gateway management tool. It was originally founded in 2004  in Santa Clara, California with the name Sonoa Systems and later rebranded as Apigee in 2010. Google has acquired Apigee in the year 2016. Apigee Edge is used for developing and managing APIs. Many websites and applications are connected together with APIs to provide data feeds. The Apigee Edge provides an abstraction for backend service APIs. It mainly offers security, rate limiting, quotas, analytics, and other features for the APIs.

Apigee Edge provides a secure way of access to the backend services with a well-defined API. This API will be easy to consume by any type of application. Even if the backend is changed or data is changed, the API won’t get affected. When applications or app developers access the APIs, they access an API proxy that is created on the Edge. The API proxy acts as a mapping of the HTTP endpoint to the backend service. The Edge will handle the authorization and security to protect the backend services.

Features of Apigee Edge

  • Here are the features of Apigee Edge.
  • Apigee Edge provides a user-friendly platform through which users can design, secure, publish, analyze, monitor, monetize the APIs. 
  • It provides configurable security policies like OAuth, API key verification, JWT, Access control, etc.
  • Versions of APIs are supported at multiple levels. 
  • Message transformation, data parsing, and validation can be done through Edge mediation.
  • Java, JavaScript, Node.js, and Python are the supported languages that Apigee Edge provides for API management.
  • It is a multi-tenant platform for both on-premises and in the cloud. 
  • The updates and fixes can be rolled out quickly.
  • It offers analytics capabilities such as dashboards, custom reports, GeoMaps, etc.

Become a Apigee Certified professional  by learning this HKR Apigee Training!

Components of Apigee Edge

Apigee Edge consists of the below 3 components.

Edge API runtime

This is where APIs are created and consumed. It contains services such as API Gateway, Connectors, Programmability, API First, Security, and Federated runtime. Users can configure API proxies, set up API products, and manage app developers and client apps. It addresses the main concerns that are related to API management. It lets the users add security policies to the API proxies. The behavior of the API proxy can be customized using custom scripts. 

Edge monitoring & analytics

Apigee Edge provides tools to generate reports that show the usage trends of your APIs. When data is passed through the Edge, several types of default information such as URL, user ID, IP are collected. Users can customize this to collect information such as query parameters, headers, portions of a request or response, etc without affecting the API performance. This information will be useful to create reports for latency, error data, and more. All the metrics are presented in a browser-based dashboard. 

Apigee Training

  • Master Your Craft
  • Lifetime LMS & Faculty Access
  • 24/7 online expert support
  • Real-world & Project Based Learning
Edge developer ecosystem

The developer ecosystem provides developer services such as SmartDocs, Self-Service, Customizable portals. It lets the users formalize their relationships with internal and external developers. Users can manage the app developers that use the services. An Edge customer can create a developer portal either in the cloud or on-premises. The app developers can connect to the portal to access API documentation. Edge customers can create two types of portals.

  • Integrated portal – a quick and easy to use developer portal.
  • Drupal-based portal – a fully customizable developer portal.

Flavors of Apigee Edge

Apigee Edge is available in three flavors.

Public cloud

A completely Apigee hosted SAAS version of the environment. Users can build APIs without worrying about the infrastructure.

Apigee hybrid 

APIs can be managed on Google Cloud Platform (GCP), or on-premise, or a mix of both. It lets the users handle both the internal and external APIs with Google Cloud. Users will be able to leverage existing local compliance and governance policies.

Private cloud

Users have to configure their own environment and carry out administrative processes such as installation, upgrade, and maintenance. The private cloud won’t be able to provide all the features offered by the public cloud. 

Want to know more about Apigee, visit here Apigee Tutorial.

Basic terminology

Let’s look at some basic terms that are frequently used in API management.

API

An application programming interface (API) is used to consume data or services from one application to another. APIs make it easy for developers to access and reuse application logic that is built by another developer. For the web APIs, the data will be accessed over the network.

API proxy

It is an abstraction or a facade for one or more APIs on the Edge. Implementing a set of configuration files, policies, and code to utilize some resources is referred to as an API proxy. The API proxies can even be created in a text editor or an IDE. It protects the backend services from code changes by developers. Users can customize the email signature by setting multiple interfaces to the same API.

API basepath and resources

An API consists of a base path and a set of API resources. The base path in an API proxy is compulsory, and the API resource paths are optional. An API management can simply be referred to as a set of URIs. Developers can attach policies and codes to these URIs. Several APIs of an application may share a common base path. 

, others, apigee-edge-description-0, , others, apigee-edge-description-1

Subscribe to our YouTube channel to get new updates..!

API product

API product is a collection of API resources (URIs) with a service plan published at design time. Developers can bundle multiple API products together for monetization to make an API package. One or more API products has an API key that permits an app to consume the API.

API package

It is a bundle of several API products generally associated with a rate plan.

App

An application built with any programming language, technology, or platform is referred to as an app. An app can either be mobile or web that consumes an API. To let the apps consume an API, they have to be registered in the API provider’s organization on Apigee Edge. Once the registration is done, the app will get an API key and secret. The API key should be embedded in the app to authorize API consumption.

Environment

It is the runtime execution for API proxies. To make an API proxy accessible, it should be deployed in an environment. Test and prod are the environments provisioned by default to an organization.

Organization

An organization acts as a container for objects in the Apigee Edge account, such as API proxies, API products, API packages, Apps, and developers. A user should have a user account to work in an organization. A user can have accounts in multiple organizations.

Policy

A policy is a reusable unit of logic that can be executed within an API proxy processing flow. A policy is generally used to transform message formats, masking sensitive data, calling remote services, access control, and more. A policy can be executed based on the context of a request, or content, or response message.

API resource path

The API resource path is a RESTful concept and a URI (uniform resource identifier) that locates the resource path to the resource available. 

Top 30 Frequently Asked Apigee Interview Questions !

Version

It is the term used to define the next edition of a developer-facing API interface. 

Revision

It is a numbered version-controlled package of API Proxies. The API interfaces have versions and the API proxies have revisions.

Tips for API proxy development

Here are some useful tips that will help you while deploying API proxies.

  • Configure a sequence of steps as an API proxy to execute in response to a request. An API proxy typically includes resource paths, an HTTP verb, body requirements, etc. Although it is called an API proxy, it is generally an API.
  • Define the path of processing logic in the flows in Apigee Edge. You can apply logic and behavior in stages of the processing path.
  • You can access the variables that represent the execution state of an API proxy. You can access them from the XML that configures API proxies and policies.
  • You can specify conditions on the API proxy state. Based on the state of the API proxy, you can execute the code conditionally to process the request.
  • You can arrange policies in a sequence of steps within a flow to execute them in order.
  • The errors of an API proxy can be customized by configuring a fault handler. 
  • You can examine the API proxy’s execution flow using a trace tool for debugging and testing. 

Apigee Training

Weekday / Weekend Batches

Conclusion

Organizations want to make the backend resources available on the web to make them accessible for mobile applications and web applications. Apigee Edge makes it easy to visually code, or configure API policies, and customize API behavior. It safeguards your data from threats and other attacks. Users can track live API calls, traffic surges, API traffic info with real-time insights. It also decreases the meantime to diagnosis (MTTD). Apigee Edge provides a seamless customer experience to partners, customers, and application developers. Major companies like Burberry, eBay, Walgreens, Shell, First Data, Live Nation, etc., use Apigee Edge. 

Related Articles: 



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


What are the controllers and their types?

Salesforce controllers, also known as Visualforce controllers, are used to execute a set of instructions. Controllers specify what happens when a user interacts with the Visualforce Markup components such as Visualforce tags, HTML, fields, etc. When a user clicks on a button or link on a Visualforce page, the associated controllers will display the data related to the user action or component. The controllers have the ability to modify component behavior. They work on an MVC(Model-View-Controller) approach. Salesforce provides the below types of controllers.

  • Standard controllers
  • Standard List Controllers 
  • Custom Controllers

Wish to make a career in the world of salesforce? Start with HKR’S  salesforce online training !

1.Standard controllers

The standard controllers are the default controllers provided by Salesforce. They contain the same logic and functionality that are used for standard Salesforce pages. Every Salesforce object contains a standard controller that can be queried using the Salesforce Lightning Platform API. When a user interacts with a component on the page, the controller interacts with the database, fetches the relevant data, and displays it on the page. To display the relevant data on the Visualforce page, we need a record ID. So, we need to send an ID as a query string parameter in the page URL. The standard controller has a getter method that returns the record related to the query ID. If a user doesn’t have access to a certain object (or component) on the page, which is associated with a standard controller, it will display an insufficient privileges error message to the user. 

Associating a standard controller with a Visualforce page

To associate a standard controller to a Visualforce page, we have to use the “standardController” attribute on the tag. We should specify the name of any Salesforce object, which can be queried using the Lightning Platform API. Here is the syntax to associate a standard controller to a standard object on a page,

Salesforce Training

  • Master Your Craft
  • Lifetime LMS & Faculty Access
  • 24/7 online expert support
  • Real-world & Project Based Learning

2.Standard List Controllers

Standard list controllers are used for displaying or act on a set of records on the Visualforce pages. Related lists, list pages, and mass action pages are some of the examples of Salesforce pages that work with a set of records. The following are the objects that can be used with standard list controllers.

  • Account
  • Contract
  • Idea
  • Order
  • Product2
  • Solution
  • User
  • Lead
  • Opportunity
  • Asset
  • Campaign
  • Case
  • Contact
  • Custom objects

Associating a standard list controller with a Visualforce page

Associating a standard list controller is very much similar to associating a standard controller. In the standard list controller, we can set an object through the “standardController” attribute on the tag and then set the recordSetVar attribute on the same component. Here is the syntax to associate a standard list controller with an object on a page,

Once the standard list controller is associated, we can act on a set of records using expression language syntax. We can use a standard list controller to add pagination to a page with the help of the next and previous actions.

Cloud Technologies, salesforce-controllers-description-0, Cloud Technologies, salesforce-controllers-description-1

Subscribe to our YouTube channel to get new updates..!

3.Custom Controllers

Custom controllers are used to implementing custom logic and data manipulation for a Visualforce page. If we want to perform things like calling an external web service, validate and insert data, we can use a custom controller. The custom controllers override the existing functionality and implement customized navigation through an application. They execute entirely in system mode and users will have full control over the app’s logic. 

Create a Visualforce page that uses a custom controller

To add a custom controller to a Visualforce page, we have to set the “controller” attribute in the tag. When we use a custom controller, we cannot use a standard controller. Here is the syntax to associate a custom controller to a Visualforce page,

Controller Extensions

A controller extension overrides behavior in a standard or custom controller. Any Apex class with a constructor that takes a single argument of type “ApexPages” is referred to as a controller extension. We can implement the functionality of another controller to an apex tag while adding custom logic. Here is an example class for controller extension.


public class myControllerExtension {

//custom code

}

We can extend this controller extension on a Visualforce page like below.
Both the controller extension and custom controller use the action, getter, and setter methods. The custom controllers and controller extension classes ignore user permissions and field-level security as they execute in system mode. So, the custom controllers and controller extensions are mainly used to set organization-wide defaults. Based on the user profile, we can even define whether a user can execute methods in a custom controller or controller extension class. 

Salesforce Training

Weekday / Weekend Batches

Conclusion

Apex is a complete programming language that we can use to implement effective Visualforce pages. We can use Apex properties, which are a combination of a variable with getter and setter methods. We can implement anything on a Visualforce page with the help of controllers in Apex code. Using controllers, we can implement features like dropdown on a Visual page. They allow you to filter the records displayed on the page. While working with controllers, you should have an eye out for validation rules. You should be able to handle the validation rule exceptions. 

Related Articles:



Source link