Tyk REST API vs. Advanced API


#1

Imported Google Group message. Original thread at: https://groups.google.com/forum/#!topic/tyk-community-support/zmpKkm-YVmw Import Date: 2016-01-19 21:44:12 +0000.
Sender:Joseph Violago.
Date:Monday, 18 January 2016 18:52:05 UTC.

I would like some clarity about the Tyk Stack Diagram. Specifically considering the use-case of API Creation.

(API --> REST API); Given how this doc is primarily geared towards a database-backed configuration, isn’t this section of workflow not valid?

From what I understand about the Tyk REST API, API Management does not work in database-configured setups. I don’t see any mechanism that automatically that migrates file definitions into MongoDB.

With all that said, is there any other way to import an API definition, while preserving api_ids? The only methods I’ve come across are database snapshots and the possibility of updating the definition in mongo and then issuing a group hot reload.


#2

Imported Google Group message.
Sender:Martin Buhr.
Date:Monday, 18 January 2016 19:28:35 UTC.

Hi Joseph,

The Tyk REST API is file based only as we understand that a lot of users do not want a MongoDB dependency.

The Advanced API that ships with the dashboard provides a full management API that can be used to manage API defs in the DB and have the gateway pull them.

So:

  1. Tyk Gateway REST API for low level control and node by node management and direct key manipulation
  2. Tyk Advanced (Dashboard) API for granular control that is DB backed

You make a choice when you install Tyk whether you want the dashboard or not. If you want the dashboard, you will need to opt into mongo and also managing Tyk via the advanced API.

You can migrate definitions by exporting and importing them, or by bridging the two APIs, API IDs are separate from DB IDs, so they can be transferred both ways.

ORG IDs can’t, but they are mainly a dashboard construct, because that’s where the advanced, granular, access control mechanisms are for Tyk Stack administration.

Martin


From: Joseph Violago [email protected]
Sent: Monday, January 18, 2016 18:52
Subject: Tyk REST API vs. Advanced API
To: Tyk Community Support [email protected]

  • show quoted text -


You received this message because you are subscribed to the Google Groups “Tyk Community Support” group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web, visit https://groups.google.com/d/msgid/tyk-community-support/de9199b1-0289-4446-8ec7-1340630b382e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


#3

Imported Google Group message.
Sender:Martin Buhr.
Date:Monday, 18 January 2016 19:34:16 UTC.

Forgot to mention:

The advanced API is documented here:

https://tyk.io/advanced-api-v0-9/about/

That whole section describes how the gap is bridged…

Thanks,
Martin

  • show quoted text -

  • show quoted text -


You received this message because you are subscribed to the Google Groups “Tyk Community Support” group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web, visit https://groups.google.com/d/msgid/tyk-community-support/de9199b1-0289-4446-8ec7-1340630b382e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.