NortheastPHP 2017 has ended
Sign Up for our Mailing List

The Northeast PHP Conference is a community conference intended for networking and collaboration in the developer community. While grounded in PHP, the conference is not just about PHP. Talks on web technology, user experience, and IT management help PHP developers broaden their skill sets. We are entirely non-profit. Our organizers and and speakers volunteer their time to create a community event experience on par with the big technology conferences. We value the participation of each member of the PHP community, so follow @NEPHP on Twitter for updates and don’t miss out!

Sign up or log in to bookmark your favorites and sync them to your phone or calendar.

api [clear filter]
Thursday, August 10

14:30 ADT

What Rails Can Teach PHP About Building APIs
As somebody who's built APIs with PHP since 2009, and built APIs with Rails for the last two years, the contrast in some of the tooling available is mind-blowing. When it comes to factories for generating test data, spec-driven testing with tools like RSpec, mutation testing, simplistic state machines, serialization and deserialization in JSON-API, REPL debugging with breakpoints, file upload handlers, etc., Ruby (and Rails) very often has a strong lead in maturity of the tooling.

PHP does have a few of these tools, but due to years of fractured development as people build framework-specific alternatives, they are not as mature as they could be. Other tools are just entirely missing in PHP land. Now that PHP has got past building framework-specific SF Bundles, Laravel Bundles, CI Sparks, ZF2 Modules, etc, and is moving to Composer-based framework agnostic code, these tools are starting to crop up and mature.

While PHP is learning how to work together on powerful, agnostic, shared code, let's look at some of the tooling available in Ruby, to see what inspiration we can draw from their experiences. There is a lot of great Ruby code built for developing and testing APIs, which PHP-land can learn a lot from!

Thursday August 10, 2017 14:30 - 15:20 ADT
Grafton Room
Friday, August 11

09:00 ADT

A No Nonsense GraphQL and REST Comparison
GraphQL is incorrectly considered by some to be a "replacement" to REST. GraphQL is a newer concept, being released by Facebook publicly in 2015, whereas REST was a dissertation published by Roy Fielding in 2000, popularized by companies like Twitter (quite inaccurately) in 2006.
This article aims to cover a few notable differences, and make the following points:

1. REST and GraphQL are totally different
2. GraphQL isn't a magic bullet, nor is it "better"
3. You can definitely use both at the same time
4. GraphQL is dope if used for the right thing

Friday August 11, 2017 09:00 - 09:50 ADT
Grafton Room