sinzone

> 30% decline in bay area real estate values.

that won't happen. During the 2008 big burst everywhere in USA was felling apart but in SF real-estate was just down 5%-10%.

SF can't expand easily since it's water 3/4 all around. Demand still high and supply very low.

That won't change dramatically, with or without a collapse in the public market.

We use it a lot at Mashape, since Kong (https://github.com/Mashape/kong) is entirely powered by OpenResty and probably by now, Kong is the most used and adopted OpenResty software.

Without OpenResty we couldn't have built Kong or make it freely available to everyone.

That's the difference from being just a tool, or a platform. The former is easy to copy and replace, the latter goes in monopoly position once you have an ecosystem around you (see Salesforce, Facebook).

$80M is the price they have to pay to go in monopoly position as soon as possible and become a platform.

Lua support in nginx is phenomenal, especially when combined with LuaJIT. It basically allows to transform nginx into an application server and run arbitrary code that can pretty much do anything.

I would like to mention agentzh and his team that did an amazing job in releasing OpenResty[1] which makes it easy to extend nginx with custom Lua functionality, which also happens to be the backbone of CloudFlare architecture, and the core technology being used by projects like Kong[2] when it comes to microservices management.

[1] http://openresty.org/

[2] https://github.com/Mashape/kong

No mention of swagger?

Garry gave me one of the best advice over 6 years ago.

http://cl.ly/image/1e3o2W450h3w

One of the folks behind OauthBible.

Have you looked into Kong [1]? We built it as Open-Source proxy (based on NGINX) that has many out-of-the-box plugins for Authentication: including JWT [2], HMAC and the tedious OAuth2 [3]. For example, Kong reduces the complexity of adding OAuth2 to your services in just a restful POST request, similar to this:

$ curl -X POST http://kong:8001/apis/{api}/plugins \

    --data "name=oauth2" \

    --data "config.scopes=email,phone,address" \

    --data "config.mandatory_scope=true"

Another alternative is Auth0.com but it's cloud based and Kong is obviously a fully featured API Gateway that does many other things so it might be too heavy if all you need is authentication.

[1] https://github.com/Mashape/kong

[2] https://getkong.org/plugins/jwt/

[3] https://getkong.org/plugins/oauth2-authentication/

docs GUI + RESTful

I see you use different machines for NGINX and auth. Do you plan to combine all of them under one API gateway like Kong?

Same problems in SF. City booming, high cost of living, not enough houses for everyone.

The purpose is to give the power of LUA scripting (via OpenResty, used by companies like Cloudflare) in the hands of more people, since Lua is a small community (even tho, it's great, easy to learn and fast). Thus, adopting JS is the solution for them.

Disclaimer: we built one of the biggest Lua+Nginx project [1]

[1] https://github.com/Mashape/kong

Joe is a rockstar! Great addition.

Order of mainstream adoption for API description languages:

1) Swagger (by far)

2) API Blueprint

3) RAML

Travis bought his house after selling RedSwoosh and being for 4 years without salary. He deserves every penny of it.

I was part of the jampad era and slept there several nights and even tho the article mentioned good facts I think I will have to write some more interesting ones on a blog post. He also helped our startup many times and we closed our angel round at his house.

Travis deserves all the success.

Awesome service! We use it a lot in conjunction with other tools. Didn't know it's actually 4 years old already [1].

[1] https://news.ycombinator.com/item?id=2649326

With output in JSON/YAML/XML: http://mockbin.com/ip

Curious.. which tools you used for managing the backend of all these APIs? (authentication, rate limiting, etc)

We plan to write a great guide, similar to DO model, once Kong (https://github.com/mashape/kong) will support Postgres (https://github.com/Mashape/kong/issues/331)

PostgreSQL is loved by the developer community and is growing in adoption very fast. When we decided to open-source KONG [1], we went with the only supported db at that time which was Cassandra. Mainly we use Cassandra to handle rate-limiting across multi region and because it's also easy to scale horizontally. But even though is battle tested at FB or Netflix, we were surprised to see how the community immediately pushed [2] for supporting PostgreSQL as well.

It's definitely a good fit, especially for the powerful features around JSONB datatypes.

[1] https://github.com/Mashape/kong

[2] https://github.com/Mashape/kong/issues/331

Before the end of the year Kong will support Postgres.

You don't. Kong (gateway) + AWS/DigitalOcean (the servers).

I suggest to check the open source API gateway: https://github.com/mashape/kong

This is a great addition for real-time/streaming APIs

aghi@mashape.com

Also tak a look at the open source API gateway http://getkong.org and https://apianalytics.com for Visualization and Monitoring of API traffic.

out of curiosity. what do you guys use for API management?

why you think it's easier to understand than kong?

We're honored to be partner [1] of Nginx with the OSS Microservice Management layer KONG [2]. Kong is built on top of Nginx and uses Cassandra for storing the config.

[1] https://www.nginx.com/blog/nginx-powers-kong-api-management-...

[2] https://github.com/mashape/kong

If you guys want to learn more live and are based in SF, we're hosting our 2nd KongSF meetup [1] next week, along with the announcement of the v 0.4.

[1] http://www.meetup.com/The-Mashape-API-Developer-Community/ev...

we use the same technology with KONG [1]

[1] https://github.com/mashape/kong