Ceryx - San Francisco API Meetup

Talk about Ceryx; a dynamic web server, programmable through an HTTP API

Transcript

1. Ceryx Dynamic, API-based reverse proxy.
2. Million dollar question
3. How often do you need to handle 1000s of NGINX vhosts? (Most probably never)
4. Hello My name is Paris Kasidiaris on Twitter @pariskasid
5. I work for sourcelair.com A website that lets people write code in their browsers.
6. How often do we need to handle 1000s of NGINX vhosts? Daily!
7. Background-story We let our users code web applications on our service We provide each of these projects with a public URL r a n d o m i d . a p p s . l a i r . i o
8. Request flow * . a p p s . l a i r . i o resolves to proxy server's IP Ceryx on proxy server listens to * : 8 0 and * : 4 4 3 Ceryx proxies according to H o s t header
9. The setup NGINX for proxying Flask for serving the API Lua scripting in NGINX for routing Redis for storing routes
10. The API List routes G E T / a p i / r o u t e s Add a new route P O S T / a p i / r o u t e s { " s o u r c e " : " r a n d o m t h i n g . a p p s . l a i r . i o " , " t a r g e t " : " u p s t r e a m _ h o s t : u p s t r e a m _ p o r t } Delete a route D E L E T E / a p i / r o u t e s / : s o u r c e
11. Benefits from API-based web server? We kept our app's logic clean We changed Ceryx' back-end 4 times with no change in the main app Easier to monitor and manage
12. Use cases Managing thousands of virtual hosts and upstreams Pro-level deployments
13. The future! Store metrics to StatsD Handle load balanced upstreams Handle TCP proxying
14. Check it out! github.com/sourcelair/ceryx
15. Thank you.