Tyk v1-8 Released - Connect Everything


#1

Imported Google Group message. Original thread at: https://groups.google.com/forum/#!topic/tyk-community-support/1jUu_15BJ1M Import Date: 2016-01-19 21:45:22 +0000.
Sender:Martin Buhr.
Date:Wednesday, 26 August 2015 10:52:10 UTC+1.

Hi Everyone,

To today we’re really hapy to announce the release of version 1.8 of Tyk and version 0.9.6 of the dashboard.

Tyk v1.8 is a major evolution in the Tyk API Platform; we’ve been hard at work and focussing on bringing you increased flexibility, new resilience patterns, improved performance and innovative new features unique to Tyk. It’s been a long road, and we’ve taken our time to integrate the many new features so they work well, together.

Check out or detailed blog post on new features here, or get started right now with our new tutorial.

Highlights of this new release:
API Sharding is a an advanced new feature that lets you split APIs across distinct Tyk clusters and manage them centrally.
Virtual Endpoints enable an easy way for you to create AWS-style lambda methods on your API endpoints with JavaScript.
Resilience Patterns enable load-balancing, enforced timeouts, and circuit breakers to enhance the reliability of your services.
Service Discovery support means that you can integrate Tyk with Consul, Etcd, Eureka or any configuration management tool that has a RESTFul endpoint for self-healing architectures.
Enhanced Analytics Tagging means you can track service usage through hardware source, cluster, policy group or keys with ease, instantly. Providing unique insights into API usage.
We’ve made major changes to improve performance and stability across the board as well as some great UI enhancements to the dashboard. The full change-log can be seen here. We’ve also made major changes to the documentation, covering off more features and plugins in both the regular Tyk docs as well as for our dashboard users.

As always, any feedback, updates, questions or bribes - you’ve got my email address, so let us know :slight_smile:

Cheers,
Martin


#2

Imported Google Group message.
Sender:[email protected].
Date:Sunday, 30 August 2015 00:02:54 UTC+1.

This sounds great. Is there a recommended method of upgrading? Are the new versions drop-in replacements that can be installed over previous versions?

Thanks

  • show quoted text -

#3

Imported Google Group message.
Sender:Martin Buhr.
Date:Sunday, 30 August 2015 08:40:18 UTC+1.

Hi Jeffrey,

1.8 should just work with your existing installation and configuration, so you can either just drop in the binary. Or keep a copy of your Tyk.conf file and install over it.

Same with the dashboard, I’d back up the config file and then just install the new one (we usually use sym linking to make it easy to switch).

Cheers,
M.

  • 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/d8890d9f-9382-4b95-be57-30508d896e43%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


#4

Imported Google Group message.
Sender:Christophe Eblé.
Date:Tuesday, 27 October 2015 11:53:55 UTC.

Hi Martin,

Just tested Virtual Endpoints, thought it was a pretty good solution to transform an XML Payload into JSON (Not implemented into Tyk)
I’ve looked at the code and it seems that you use Otto which is a pure Golang JS interpreter, Otto has JSON support but has no support for XML parsing (No DOMParser or E4X).

For our particular case, it makes Tyk pretty useless, is there any plan to improve that?

Cheers,
Chris

  • show quoted text -

#5

Imported Google Group message.
Sender:Martin Buhr.
Date:Tuesday, 27 October 2015 12:40:18 UTC.

Hi Christophe,

Not at the moment, though we would always appreciate help on something like this - Otto enables the plugging in of new functionality, so for example you could write a JS API interface that uses the golang XML libs and exposes them tot he JS interpreter, thereby extending the functionality of the interpreter with an XML parser.

There is also the possibility of using a pure JS solution, though this might be a little slow.

XML support overall is on our list, but not on the top of the priority queue unless it gets put there by exceptional demand :slight_smile:

Cheers,
Martin