jively

12 ms·

61.
by jively 11y ago
API Managmeent market is quite big, makes sense for Amazon to get on board. Imagine this: You are BigCorp USA Inc. and have a bunch of internal SOAP-based web services that are 10 years old and cost a fortune to maintain. You hear someone w
62.
by jively 11y ago
Hah! Indeed :-)
63.
by jively 11y ago
You could always use an open source gateway like Tyk ( https://tyk.io ) or API Umbrella (full disclosure: I run Tyk.io, and this news is... disheartening).
64.
AWS T2 Burstable instances – a performance experiment(lonelycode.com)
3 points by jively 11y ago|0 comments
65.
[ANN] Tyk v1.7 Released(tyk.io)
1 points by jively 11y ago|0 comments
66.
by jively 11y ago
Done and updated - thank #TheRealLukeB! :-)
67.
by jively 11y ago
Tyk (self-hosted) offers a dashboard and analytics for free out of the box. :-) Tyk Cloud was very much built to make the open source and free versions better (and sustainable), so I think there's probably some differences in motivati
68.
by jively 11y ago
You would need to upgrade to the next tier - we're working on adding "soft maximums", currently they are hard cut-offs. We would, most likely allow a certain % overage, then notify the user, with some kind fo three strikes ru
69.
by jively 11y ago
Amazing, thanks! :-D
70.
by jively 11y ago
Will do! We atually started as an open source / licensed hybrid model. Then moved to offer all of our software for free and charge for support. Moving to a cloud platform was a natural next step - not only is it a great way to demo the
71.
by jively 11y ago
Cheers, spelling has improved :-/ damned sausage fingers! Our servers are currently in the US as that's where the market is (from what we've found, so far). It's something we've thought about and we will be looking
72.
by jively 11y ago
Ah, good point - legacy assets in the template, they'll need updating.
73.
by jively 11y ago
Thanks so much! :-D
74.
by jively 11y ago
Ah yes, noted!
75.
Show HN: Tyk Cloud – Open Source API Management in The Cloud(cloud.tyk.io)
36 points by jively 11y ago|20 comments
76.
Tyk 1.6 Released – Now with an API portal and docker support(tyk.io)
1 points by jively 11y ago|0 comments
77.
Tyk is now completely free(tyk.io)
2 points by jively 12y ago|0 comments
78.
[ANN] Tyk v1.3 released – API mocks,blueprints and analytics in golang(tyk.io)
2 points by jively 12y ago|0 comments
79.
by jively 12y ago
London Black cabs are overpriced, and there's no market check that stabilises price, as much as I respect the institution of "The Knowledge", you are still bound by the need to trust your driver, and many are just opportunist
80.
by jively 12y ago
Got it, yes that would indeed be very useful for heavy-use APIs, and shouldn't be too much of a problem to implement. However it would essentially add a default batch endpoint to an API which isn't defined by the owner. Also, cer
81.
by jively 12y ago
Not at the moment, but it can certainly be added. I assume you mean some kind of pipelining so that if multiple requests that have the same signature come through then only one gets executed and the response is shared amongst all the reques
82.
by jively 12y ago
Took a closer look at this today, it really does look incredibly flexible, interesting to see how easy it is to add middleware to an endpoint stack. This might be an approach for us if Tyk functionality expands beyond an API Gateway and add
83.
by jively 12y ago
Fixed, thanks for the spot!
84.
by jively 12y ago
Nope - they are pretty raw, we leave that up to the person installing the kit - Tyk isn't a service, it's a piece of software to run on your own infrastructure so that your sysops can lock it down however they see fit, like NGinX.
85.
by jively 12y ago
I haven't, we'll check it out. Though Tyk is not a SAAS, it's meant to be self hosted :-) (though it could be a SAAS if you configure it right. In fact it has design implementations for just such a purpose...
86.
by jively 12y ago
I am, it's me and my business partner - she takes care of the financials / legals, and is the voice of common sense and reason. I handle the dev (with a bit of help from bootstrap).
87.
by jively 12y ago
Solid advice. There's an argument for going after large customers and in this market that seems to be the way things have gone. Everything is big enterprise, if not now it is somewhere we are looking to enter once we are ready.
88.
by jively 12y ago
We ran the site for two years, it wasn't competitive to keep running.
89.
by jively 12y ago
Thanks - it's not a weekend project and has taken quite some time to build - part of the reason for making the core app open source was to ensure that it could be easily supported long term and empower end users. With regards to price
90.
by jively 12y ago
Keyboard fail...

More ›