Mule API - deploy to a Mule Runtime -


i experimenting mule api management these days. come know can deploy our api 1 of these:

  1. a mule runtime
  2. an api gateway

in documentation, said should go option 1 when want to separate out implementation of api orchestration. mean?

can 1 please explain in detail?

not sure mean there, because on page: https://developer.mulesoft.com/docs/display/current/api+gateway mention this:

note api gateway, because acts orchestration layer services , apis implemented elsewhere, technology-agnostic. can proxy non-mule services or apis of kind, long expose http/https, vm, jetty, or apikit router endpoints. you can proxy apis design , build api designer , apikit api gateway separate orchestration implementation of apis.

so both methods technically allow separate api orchestration, api gateway application proxy mule application elsewhere performs orchestration. understanding of 2 options are:

the api gateway limited offering allows use subset of mule's connectors, transports , modules such apikit , http, allows expose , api use http connect whatever backend systems want proxy , perform orchestration in api layer.

by using mule runtime operation, gives more flexibility , allows compose many applications want using full range of connectors etc. , separate out different aspects of applications many layers want separately deployable entities can deploy on-premise standalone instances or cloudhub etc.


Comments

Popular posts from this blog

javascript - Using jquery append to add option values into a select element not working -

Android soft keyboard reverts to default keyboard on orientation change -

jquery - javascript onscroll fade same class but with different div -