Choosing Slim PHP for RESTful development.

Choosing Slim PHP for RESTful development.

Making the right choice of framework is non-trivial. Here's how I chose Slim for a Geo DNS performance demonstrator.
http://bgreenaway.com

983a9815b8f76cb27ff29af5562a8633?s=128

Ben Greenaway

January 24, 2013
Tweet

Transcript

  1. Choosing Slim for a RESTful PHP API Choosing Slim for

    a RESTful PHP API Hello :-) I'm Ben @blgreenaway blg@bgreenaway.com www.bgreenaway.com & I've been building a DNS performance measuring tool as a Client-Sever Web Application which is both Stateless and Cacheable presents a Layered Appearance and a Uniform Interface which will always * show resources in requests and * make representations both full and complete and * make media types explicit and complete and * use hypermedia as the engine of application state ..here it is... ..here it is...
  2. a RESTful DNS performance tester a RESTful DNS performance tester

    ...Greatest challenge was to describe it... ...Greatest challenge was to describe it... Public Public Endpoint Endpoint Test Agents Test Manager Results Store timer/cron * test Geographic variance * test DNS Provider variance * run both On-Demand and 'Stress' tests * must be independent of scale * accessible across the enterprise * robust, maintainable and useable
  3. Choosing Slim for a RESTful PHP API Choosing Slim for

    a RESTful PHP API Apify, Dave, Epiphany, FRAPI, Limonade, Recess, Restler, Slim, Tonic, Zend, Konstruct, Chinchilla, Symfony, Restler, Limonade, Fat Free (F3), at least... No particular lack of options,.. ..but why did I choose Slim..? ..but why did I choose Slim..? "Installing Zend [just] to set up a REST interface. That's like hunting squirrel with a bazooka." - ringo, Linden Lab SF' on stackoverflow.com/questions/3466179
  4. Choosing Slim for a RESTful PHP API Choosing Slim for

    a RESTful PHP API “REGEX route conditions” - route methods vary greatly “OOP Request helpers” - internally the API is mine “PHP 5.3+ name spaces”- please, always play nice “all the HTTP nouns” - or custom extension method(s) “good documentation” - clarity & common vocab plz “header|cache|mimetype control” - fully customizable * things everything should have, but not all do
  5. Choosing Slim for a RESTful PHP API Choosing Slim for

    a RESTful PHP API “middleware”- a great authentication example “exceptions” - stop|pass helpers * things I didn't know I'd get, but I'm very glad I did Slim microframework for PHP - Slim microframework for PHP - www.slimframework.com www.slimframework.com also go see : www.apievangelist.com for things API