API Governance (Api Days Mediterranea)

Canal público / definición

Se define los aspectos a tener en cuenta:
• Definición de recursos
• Políticas de versionado
• Seguridad
• Documentación de API
• Monitorización
• Testing
• Gestión de los entornos
• Developer Center

Compartir en redes sociales

Compartir enlace

Usar vinculo permanente para compartir en redes sociales

Compartir con un amigo

Por favor iniciar sesión para enviar esto presentation por correo!

Incrustar en tu sitio web

Seleccionar página de inicio

Publicar comentario con dirección de correo electrónico (se requiere confirmación de correo electrónico para publicar comentarios en el sitio web) o por favor iniciar sesión publicar comentario

20. Any questions?

6. Introduction And, all is more complicated if you expose information to other organizations

3. Introduction The vertical applications have the front end and the back end in the same location. The front end speaks with the back end using objects. What vertical application means?

4. Introduction In company there can be a lot of applications deployed into the organization. You can have applications for human resources, sellers, buyers... How many applications can be in the company ?

5. Introduction Sometimes it uses files, the other times it uses apis, soap ... this is a not efficient!!! How the communication between us work?

13. API Governance ➢ Documentation format ○ Doc ○ HTML ○ RAML / Swagger ➢ Where do we leave the documentation for developers? Present version / previous versions - who manages the update documentation? Documentation

12. API Governance ➢ frameworks? ➢ Spring data rest / hateoas (java) ➢ restify / express (node.js) ➢ SDK: For what languages? Development philosophy of SDK ➢ Should we start some code generator? Standard development http://www.slideshare.net/MarcoAntonioSanzMoli/taller-desarrollo-de-apis

17. API Governance ➢ Pre-production ○ Real data? ○ Generated data? ➢ Production ○ Support ➢ Sandbox? Environments http://www.slideshare.net/MarcoAntonioSanzMoli/las-apis-como-modelo-de-negocio

14. API Governance ➢ Statistics of use ○ Number of requests per app ○ Number of requests per user (if it’s possible) ○ Number of requests per resource Number of requests per developer ○ Number of requests per http code response ➢ Alerts Monitoring

9. API Governance Versioning ➢ Url versioning GET XXX/ejemplo/v1.0/users/ ➢ Header versioning Accept: application/vnd.company.myapp-v3+json Content-Type: application/vnd.company.myapp-v3+json ➢ When the version of api should be changed? ➢ How to deal with breaking backwards compatibility?

1. 20 meetups 716 api addicts 16.000 visualization s 9K 3K 2K Síguenos en @apiaddicts Patrocinador:

18. API Governance ➢ Steps ○ Definition ➢ Fake? ➢ Develope ➢ Testing / validation ➢ Implementation ➢ Obsolescence Methodology http://www.slideshare.net/MarcoAntonioSanzMoli/mada-metodologa-gil-de-desarrollo-de-ap-is-37095756

19. API Governance ➢ Create and manage consumer apis ➢ Get api access key ➢ Testing api tools ➢ Documentation / samples / SDKs ➢ Monitoring ➢ Payment ➢ Statistics Developer center There is an application for developers. Some features

8. API Governance Define objects and their attributes into organization: User data: { “ name ” : ” Manolo ” , ” edad ” : ” 12 ” } Define the resources

16. API Governance ➢ Payment methods ○ Api Managers can help me ➢ Billing model ○ Requests ○ Services ○ Data (Scopes?) ➢ Can you afford to pay a developer for using your Billing http://www.slideshare.net/MarcoAntonioSanzMoli/las-apis-como-modelo-de-negocio

7. API Governance ➢ Define resources ➢ Versioning policy ➢ Security policy ➢ Define the standard to define the apis ➢ Define the standard to deploy the apis ➢ Documentation ➢ Monitorization ➢ Testing ➢ Billing ➢ Environment General considerations

15. API Governance ➢ Integrations tests. ○ ¿ Do you develop your integration tests? ○ ¿ Do you use external tools to implement tests? ➢ ¿ Do you go to automatize tests? ○ Jenkins / jmeter / soapui / postman ➢ ¿ what can i test? ○ Data ○ Http code response Testing

10. API Governance ➢ Api Manager? ➢ Authentication 2 / 3 ○ 2 => applications ○ 3 => final users ➢ do you implemented a personal system authentication or do you use a standard? ➢ Security into the apis. ¿ do you control information? ○ scopes ○ Resources and methods Security http://www.slideshare.net/MarcoAntonioSanzMoli/seguridad-en-las-apis

11. ➢ Restful?? level of achievement? ➢ HTTP error codes ➢ Format of entry parameters ➢ Special entry parameters ➢ Input/Output format ➢ HTTP Verbs ➢ Paging ➢ URL levels ➢ Hypermedia ➢ Granularity of services Standard definition http://www.slideshare.net/MarcoAntonioSanzMoli/taller-definicin-de-apis API Governance

21. Email: ➢ contacta@apiaddicts.org Web: ➢ www.apiaddicts.org ➢ http://Apiaddicts.leadgods.com Follow us: Linkedin: ➢ https://www.linkedin.com/company/apiaddicts Twitter: @apiaddicts Facebook: ➢ https://www.facebook.com/pages/APIAddicts Meetup: ➢ http://www.meetup.com/es-ES/ApiAddicts Contact

2. /marcoantonio.sanz@apiaddicts.org { “ name ” : ” Marco Antonio Sanz ” , “ positions ” : [ “ CEO at CloudAppi ” , “ CEO at LeadGods ” , “ Api Envangelist at ApiAddicts ” , “ Teacher at ufv ” ] } Who am i? @MarAntonio82

Vistas

  • 546 Vistas totales
  • 521 Vistas del sitio web
  • 25 Vistas incrustadas

Acciones

  • 0 Acciones Sociales
  • 0 Me gusta
  • 0 No me gusta
  • 0 Comentarios

Veces compartido

  • 0 Facebook
  • 0 Twitter
  • 0 LinkedIn
  • 0 Google+

Incrusta 1

  • 8 www.apiaddicts.org