Les Hazlewood

Les Hazlewood
Co-Founder and CTO, Stormpath

Website | @lhazlewood

Les Hazlewood is Stormpath co-founder and CTO and the Apache Shiro PMC Chair.

Prior to forming Stormpath, Les held senior architectural positions at Bloomberg and Delta Airlines and he was former CTO of a software engineering firm supporting educational and government agencies. Les has been actively involved in Open Source for more than 10 years, committing or contributing to projects like the Spring Framework, JBoss, and Apache Shiro. Les has a BS in Computer Science from Georgia Tech, and practices Kendo and studies Japanese when he’s not coding.

Speaking Experience:

- DevNexus 2014
- ApacheCon NA 2014
- Cassandra Day Silicon Valley 2014

- JavaOne (awarded “Rock Star” presenter)
- GlueCon 2013
- JAXConf 2013
- ApacheCon NA
- DeveloperWeek 2013
- Silicon Valley Grails User Group

- JavaOne (awarded “Rock Star” presenter)
- Rich Web Experience
- Silicon Valley Web User Group @ Google
- East Bay Java User Group
- Silicon Valley Linux User Group

- OSCON 2011
- DevNexus 2011
- San Francisco Java User Group, etc.

Most Recent Speaking Videos:

Build A Killer Node.js Client for your REST + JSON API (https://www.youtube.com/watch?v=1FVAS7MdPXo) @ BayNode Meetup 2014
API Strategies for Developers (http://www.youtube.com/watch?v=bx4WQ0bjruY) @ DeveloperWeek 2013
Beautiful REST + JSON API Design (http://www.youtube.com/watch?v=hdSrT4yjS1g) @ Google, Silicon Valley Web User Group, August 2012
Securing Passwords Properly (http://www.youtube.com/watch?v=6bR110r-RfY) @ Rackspace, Linux User Group, September 2012


11:00am–12:30pm Monday, 04/20/2015
Server side technology
Location: Salon 8
Les Hazlewood (Stormpath)
Average rating: ****.
(4.69, 29 ratings)
Designing a really clean and intuitive REST + JSON API is no small feat. You have to worry about resources, collections of resources, pagination, query parameters, references to other resources, which HTTP Methods to use, HTTP Caching, security, and more! Further, while there are many references on creating REST APIs with XML, there are much fewer references for REST + JSON. Read more.