A first look at ZF3

Zend Framework 3 is the framework that took the opportunity to learn from the previous 4 years of ZF2 and be even better than that! Today's PHP projects are built of components installed via Composer and ZF3's architecture reflects this approach; its core components have also been greatly improved in both usage and performance from older versions of the framework. If you're already running a ZF2 application, you'll be able to upgrade your existing application and there will be some excellent support for doing so - we love it when developers get to use new things. If you're a PHP developer with an interest in building excellent, modern applications, then this session is for you.

This presentation was given at PHPNW conference in October 2015.

Transcript

1. A first look at Zend Framework 3 Rob Allen ~ @akrabat ~ October 2015
2. What did ZF2 give us?
3. What’s wrong with ZF2?
4. The PHP world has changed since 2012
5. So what’s the ZF3 story?
6. The ZF3 story • Components • ZF2 => ZF3 means MVC improvements! • PSR-7, Interoperability & Middleware
7. PHP 5.5
8. Components
9. Components • Separate repositories
10. Components • Separate repositories • Separate evolution
11. Components • Separate repositories • Separate evolution • Documentation in repository
12. Components • Separate repositories • Separate evolution • Documentation in repository • All issues in the right place on GitHub
13. Components • Separate repositories • Separate evolution • Documentation in repository • All issues in the right place on GitHub • More maintainers
14. ZF MVC framework
15. MVC improvements • ZF2 is now a meta package
16. MVC improvements • ZF2 is now a meta package • Managed BC breaks
17. MVC improvements • ZF2 is now a meta package • Managed BC breaks • Key component changes • ServiceManager • EventManager • Hydrators
18. PSR-7, Interoperability & Middleware
19. It’s all about HTTP Request: {METHOD} {URI} HTTP/1.1 Header: value1,value2 Another-Header: value Message body Response: HTTP/1.1 {STATUS_CODE} {REASON_PHRASE} Header: value Message body
20. Current PHP Request: • $_SERVER, $_GET, $_POST, $_COOKIE, $_FILES • apache_request_headers() • php://input Response: • header() • echo (& ob_*() family)
21. PSR-7 It’s just some interfaces • RequestInterface (& ServerRequestInterface) • ResponseInterface • UriInterface • UploadedFileInterface
22. A quick aside
23. Key feature 1: Immutability Request, Response, Uri & UploadFile are immutable $uri = new Uri('https://api.joind.in/v2.1/events'); $uri2 = $uri->withQuery('?filter=upcoming'); $request = (new Request()) ->withMethod('GET') ->withUri($uri2) ->withHeader('Accept', 'application/json') ->withHeader('Authorization', 'Bearer 0873418d');
24. Key feature 2: Streams Message bodies are streams $body = new Stream(); $body->write('<p>Hello'); $body->write('World</p>'); $response = (new Response()) ->withStatus(200, 'OK') ->withHeader('Content-Type', 'application/header') ->withBody($body);
25. Diactoros ZF’s PSR-7 implementation
26. Diactoros • Complete PSR-7 implementation
27. Diactoros • Complete PSR-7 implementation • Specialised Responses: JSON, Empty & Redirect
28. Diactoros • Complete PSR-7 implementation • Specialised Responses: JSON, Empty & Redirect • Used by Symfony for their PSR-7 bridge
29. Diactoros • Complete PSR-7 implementation • Specialised Responses: JSON, Empty & Redirect • Used by Symfony for their PSR-7 bridge • zend-psr7bridge: ZF3’s PSR-7 to Zend\Http bridge
30. Middleware
31. Middleware
32. Middleware function ($request, $response, callable $next = null) { // do something before // call through to next middleware if ($next) { $response = $next($request, $response); } // do something with $response after return $response; }
33. Writing middleware Pattern: • Optionally modify the received request and response • Optionally invoke the next middleware • Optionally modify the returned response • Return the response to the previous middleware.
34. Stratigility ZF’s Middleware implementation
35. Stratigility • Dispatches a stack of middleware
36. Stratigility • Dispatches a stack of middleware • Middleware format: • Any callable • Zend\Stratigility\MiddlewareInterface public function __invoke( ServerRequestInterface $request, ResponseInterface $response, callable $out = null ) : ResponseInterface;
37. ErrorMiddleware Pass error as third parameter to $next: return $next($request, $response, $error);
38. ErrorMiddleware Pass error as third parameter to $next: return $next($request, $response, $error); Handle like this: function ($error, ServerRequestInterface $request, ResponseInterface $response, callable $out ); or Zend\Stratigility\ErrorMiddlewareInterface
39. Path segregation: use Zend\Stratigility\MiddlewarePipe(); $app = new MiddlewarePipe(); $app->pipe($mw1); // always evaluate $app->pipe('/blog', $blogMw); // only if path matches $app->pipe('/contact', $contactMw); $app->pipe($outputMw); $server = Server::createServer($app, …); $server->listen();
40. Nesting Middleware Compose middleware together based on path: $blog = new MiddlewarePipe(); $blog->pipe('/post', $postMw); $blog->pipe('/feed', $rssMw); $blog->pipe('/', $listMw); $app = new MiddlewarePipe(); $app->pipe('/blog', $blog);
41. Middleware wrappers $app->pipe('/', $homepage); // Static HTML $app->pipe('/customer', $zf2Middleware); // ZF2 $app->pipe('/products', $zf1Middleware); // ZF1 $app->pipe('/api', $apigility); // Apigility $app->pipe('/user', $userMiddleware); // 3rd party
42. What about routing? (& DI container, etc…)
43. Expressive ZF’s micro framework
44. Expressive • Builds on Diactoros & Stratigility - Middleware!
45. Expressive • Builds on Diactoros & Stratigility - Middleware! • Choose your own components • Router
46. Expressive • Builds on Diactoros & Stratigility - Middleware! • Choose your own components • Router • DI container
47. Expressive • Builds on Diactoros & Stratigility - Middleware! • Choose your own components • Router • DI container • Templating
48. Expressive • Builds on Diactoros & Stratigility - Middleware! • Choose your own components • Router • DI container • Templating • Error handling
49. Agnostic Router: • Aura.Router, FastRoute or Zend\Mvc\Router DI Container: • Pimple, Aura.Di, Zend\ServiceManager or container-interop Template: • Plates, Twig or Zend\View
50. Hello world use Zend\Expressive\AppFactory; $app = AppFactory::create(); $app->get( '/hello/{name}', function ($request, $response, $next) { $name = htmlentities($request->getAttribute('name')); $response->write("<p>Hello, $name!</p>"); return $next($request, $response); } ); $app->run();
51. Middleware pipes $app->pipe($sessionMiddleware); $app->pipe($authMiddleware); $app->get('/', $homepageMiddleware); $app->run();
52. Named routes 3rd parameter: $app->get('/books/{id}', $getBookAction, 'book'); Build URI: $url = $router->generateUri('edit', ['id' => 1]);
53. Views Templates are instances of Zend\Expressive\Template\TemplateInterface $html = $templates->render('book/detail', [ 'layout' => 'master', 'book' => $bookEntity, ]); return new HtmlResponse($html);
54. Why Expressive? • Performance
55. Why Expressive? • Performance • Developer experience
56. Why Expressive? • Performance • Developer experience • Reusable middleware
57. This is the ZF3 era
58. The ZF3 era • Separate components • ZF2 MVC with performance improvements • Stratigility PSR-7 middleware foundation • Expressive micro framework
59. Questions? https://joind.in/15429 Rob Allen - http://akrabat.com - @akrabat
60. Thank you! https://joind.in/15429 Rob Allen - http://akrabat.com - @akrabat