One of my new year’s resolutions was to write more often on this blog. I created my own hack day. I would dedicate an entire day to hack on a relatively small project, so I can learn a new technology or a new API. I decided that Thursday was a good day, and so far I’ve been able to write about building a telegram bot for weather using the WeatherUnlocked API and about the APIStrat API. Not as regular as I wanted, but getting there. For last week’s hack day I wanted to get my hands on a programming language I never touched before: Go. I’d heard a lot of good things about it – for one thing it’s supposed to be faster! People have been building more and more stuff in Go, and I’d seen lots of developers using it for their API projects. I had to give it a try. My ultimate goal was to build a package for 3scale in Go, so developers could…
Guest Post from 3scale collaboration partner Lorinda Brandon of SmartBear
In a recent post in our API Lifecycle series we discussed API best practices and highlighted the importance of tools. Specifically there are still some areas in the API lifecycle that aren’t well covered by tools.
We’re now plugging one such hole – easy API testing and refinement – through a collaboration with SmartBear.
SmartBear is provider of some of the most popular API, software testing and development tools in use on the planet. One of these tools is Ready! API which is a true API readiness platform with features like API testing, traffic simulation, virtualization to…
Create your 3scale account and see for yourself. We'll get you started with a free 30-day trial, which you can upgrade at any time.
There’s a nice article over at API Evangelist this morning on the battle for your API proxy. Lots of good things in the article and nice to see comparisons – while broadly the classification works we see things slightly differently though :).
The spirit is right but the label proxy is a little misleading – 3scale in fact doesn’t aim to be a proxy at all (we call it “proxyless” by design) and 3scale’s architecture works in such as way that it never has to see your API traffic at all or get in the way of calls (no proxies to be seen).
It’s better to think of it as a wholly different type of infrastructure: rather more like a …