Retail Store en Google Cloud Platform

1

Lo que aprender谩s sobre GCP para ecommerce

2

Etapas clave y MLOps

3

Arquitectura de alto nivel

4

Tour de la aplicaci贸n de retail

5

Backend as a Service y modelo de seguridad

6

Introducci贸n al proyecto

7

Medici贸n de interacciones

8

Setup de Google Tag Manager

9

Etiquetando con Google Tag Manager

10

Etiquetas relevantes para CLV

11

Integraci贸n con servicios

Exposici贸n de servicios con Apigee

12

Servicios expuestos con APIs

13

驴Qu茅 son las APIs?

14

Apigee

15

Creaci贸n de tu primer API Proxy en Apigee

16

Administraci贸n de APIs con Apigee

17

Creando un portal de desarrolladores

18

Interactuando con el portal de desarrolladores

19

Insights to Actions

Generaci贸n de modelos AI/ML

20

Machine Learning con datos estructurados

21

BigQuery para modelos de Forecasting y LTV

22

Bigquery ML - Manos a la Obra

23

Auto ML vs. Bigquery ML

24

Consideraciones para entrenar un modelo en BigQueryML

25

Entrenamiento del modelo en BigQuery ML

26

C贸mo exportar modelos hechos en BQML

27

Exportando un modelo hecho con BQML

Consumo de servicios de AI/ML

28

C贸mputo Serverless y Contenedores

29

驴Qu茅 es Kubernetes?

30

Consumo de modelos ML mediante BigQuery API

31

Almacenamiento de predicciones

32

Ejecuci贸n de predicciones y persistencia

33

Despliegue continuo con Cloud Run

34

Ejecuci贸n de despliegue con Cloud Run

35

Escalamiento de servicios en Cloud Run

36

AuthN y AuthZ con Cloud Run

Google Marketing Platform

37

An谩lisis de las predicciones

38

Segmentamos nuestras Predicciones

39

Caso pr谩ctico para definir tu estrategia de activaci贸n

40

Generemos nuestros modelos en la plataforma

41

Segmentamos nuestras audiencias en BigQuery

42

Carga tus audiencias y conecta tu medio de activaci贸n

You don't have access to this class

Keep learning! Join and start boosting your career

Aprovecha el precio especial y haz tu profesi贸n a prueba de IA

Antes: $249

Currency
$209
Suscr铆bete

Termina en:

0 D铆as
11 Hrs
33 Min
26 Seg

Creaci贸n de tu primer API Proxy en Apigee

15/42
Resources

What is an API specification and why is it important?

API specifications are based on a standard known as Open API, formerly Swagger, which allows defining a standard interface for integrating APIs. This standard is crucial as it helps both humans and machines to understand the capabilities of a service without the need to access the source code. The specifications offer detailed, accessible and understandable documentation, providing descriptions of the operations and parameters that the API supports. This is especially useful for developers looking to integrate services without having to understand all the logic behind the backend.

For those who want to dive deeper into Open API, the Open API Initiative site is an excellent resource for more details, blogs and helpful resources to get started.

What is an API Proxy and what does it do?

A Proxy API is a developer-oriented interface that allows the use of backend services without directly interacting with them. Instead of consuming the services directly, you access a proxy that provides built-in functionality such as:

  • Security
  • Speed limiting
  • Quotas
  • Caching
  • Persistence
  • Data transformation

In addition, it enables data analysis and fault handling. In essence, a Proxy API acts as an intermediary layer that optimizes the integration and use of backend services.

How to create a Proxy API with APIG from a specification?

Creating a Proxy API with APIG is a simple and efficient process if you follow a series of basic steps:

  1. Importing the Specification: Access the develop and specs section, where you can import an existing specification. In this case, a YAML file that clearly defines the available operations, such as getting all products or a specific one by ID.

    paths: /products: get: summary: Get all products /products/{id}: get: summary: Get a product by ID
  2. Proxy Creation: After importing the specification, go to API proxy and create a proxy based on it. Select the name you previously defined for your specification and define a basepath.

  3. Configuration of the Service to Consume: Set the target service you want to consume. In this example, a product catalog is used that has properties such as ID, name, description, image, categories and price. The URL of the catalog is public and allows different operations to be performed.

  4. Validation and Configuration: Verify that the operations you want to perform are selected, check the Secure option to secure the service and enable a test environment.

  5. Deploy and Test: Once configured, select create and deploy to complete the proxy creation. Next, test your API in the Trace section to make sure it responds correctly, checking if you get correctly structured responses and the correct HTTP status (usually 200 for success).

At the end of these steps, you will have created your first API using APIG, allowing for a more robust and secure integration by using a Proxy API.

Now that you have mastered the creation of APIs with APIG, we encourage you to practice what you have learned to strengthen your skills and explore new possibilities in backend service management!

Contributions 7

Questions 1

Sort by:

Want to see more contributions, questions and answers from the community?

Specs ya no esta en el menu de Apigee, pueden actualizar el curso por favor?

Les comparto el repo donde se encuentra el recurso del archivo yaml

https://github.com/apigee/apijam/blob/master/Module-1/Resources/products-catalog-spec.yaml

Pueden descargar el archivo y importarlo

el sitio al que redirige no funciona

Tampoco se agrego la URL de la practica que menciona

el enlace de Open API Specificacion es

https://www.openapis.org/

No agrego el archivo yaml a los recursos