Using PHP to Build a Mobile Internet Platform

Transcription

2 Overview 1. About Kargo 2. PHP beyond Hypertext Preprocessing 3. Kargo s Mobile Web Architecture 4. Conclusions 5. Ideas & Discussion 2

3 Who is Kargo? Kargo is a mobile media company that conceives, builds and manages leading mobile products for media properties. 1. Mobile Web 2. Web Applications with Mobile Integration 3. Messaging Applications 4. Native Applications (J2ME, iphone, Blackberry, etc.) 3

4 Mobile Web 4

5 Web/Messaging 5

6 Panoramic Applications Web Apps Mobile Content & Apps Widget Messaging Text BOB12 to to get content 6

7 Technical Challenges Many thousands of variations of devices from over 40 vendors to target Devices vary strongly in terms of capabilities (and bugs!) Network speeds very strongly Crippled technology standards (business-driven removal of features). Misleading specifications. Significant amount of engineering and operational time spent on compensating for the above. 7

8 How to address? Need for a flexible architecture Loosely coupled (web-) technology helps Single choice of technology PHP! 8

9 PHP beyond Hypertext Preprocessing building enterprise architectures with PHP5 and Zend Framework 9

10 Enterprise Architecture From Microsoft.com:...a methodology to encompass all of the various IT aspects and processes into a single practice. From MIT:... IT infrastructure reflecting the integration and standardization requirements of the firm s operating model. In simple words: A single practice to reflect what the company does 10

11 Qualitative Requirements flexibility - platform s potential to address new business requirements rapid development - reuse, simplicity, short learning curves performance - write efficient apps should be straight forward reliability - robust platforms, solid testing, security interoperability - offer simple ways to talk to interface with third-party systems simple deployment - application installation and update scalability - architectures must scale on demand high availability - be able to guarantee uptime manageable costs - ability to budget 11

12 Qualitative Requirements flexibility - platform s potential to address new business requirements rapid development - reuse, simplicity, short learning curves performance - write efficient apps should be straight forward reliability - robust platforms, solid testing, security interoperability - offer simple ways to talk to interface with third-party systems simple deployment - application installation and update scalability - architectures must scale on demand high availability - be able to guarantee uptime manageable costs - ability to budget How to address with PHP? 11

13 Motivation and Claim Scripting languages (e.g. Python, Ruby) continue to grow in popularity for many applications where PHP is usually not considered. PHP is ready to do the same 12

14 Legacy and Evolution <?php <?php if (!isset($_post[ item ])) include form.inc ; else {?> <html><body> <?php $quantity = $_POST['quantity']; $item = $_POST['item']; /** Kargo Smpp Client Copyright (c) 2008 Kargo Global, Inc. */ abstract class Kargo_Smpp_Client_Abstract extends Kargo_Event_Buffered_Client implements Kargo_Event_Buffered_Handler { /** * The smpp connection state * unknown_type */ protected $_state = KARGO_SMPP_STATE_CLOSED; echo "You ordered ". $quantity. " ". $item. ".<br / >"; echo "Thank you for ordering from <b>myshop</b>!";?> </body></html> <?php }?>... } /** * SMPP protocol flavor to use * string */ protected $_smsc_vendor = Kargo_Smpp::KARGO_SMPP_VENDOR_NONE; Two random code snippets. PHP looks quite different nowadays. But, is it ready for Enterprise environments? <?php $esmc = new Kargo_Smpp_Client_MBlox($options); $esmc->connect(): Kargo_Event::enable($esmc); Kargo_Event::dispatchLoop(); 13

15 Zend Framework Already offers several enterprise grade features, principles and practices for web development Has roadmap for much more. Highly active community that you can plan with. Could be foundation to take PHP on the market for general purpose application development à la Java,.Net, C++. Read more at: 14

16 How to address with PHP? Zend Framework Already offers several enterprise grade features, principles and practices for web development Has roadmap for much more. Highly active community that you can plan with. Could be foundation to take PHP on the market for general purpose application development à la Java,.Net, C++. Read more at: 14

17 Considerations for building your architecture using ZF/PHP 1. Identify architectural layers of your environment Use PHP traditionally on the front end Consider using PHP-CLI for back-end services 2. Maintain your own class framework Adapt from ZF: best practices, coding standards, testing standards, etc. Really solid - no need to re-invent Be ready to patch ZF components, without waiting for next release 3. Manage your PHP configuration choose your extensions carefully optionally write your own extensions when needed 15

18 More Considerations for building your architecture using ZF/PHP 4. Avoid using PEAR lack of consistency not as enterprise-friendly as ZF (license) 5. Avoid tying yourself to a particular system environment don t let the environment dictate your application design 6. Avoid using tightly-coupled PHP frameworks ( CMSs ) Often very restrictive and hard to extend or integrate with other systems 16

19 What s missing? Multi-threading A more concrete life-cycle model for long running processes However: not a huge sacrifice 17

20 Kargo s Mobile Application Platform 18

21 Kargo s Architecture: Logical Overview Application Layer Mobile Web Applications Web Applications Public Web Services Foundation Classes Messaging Service Billing Subsystem Device Management Reporting Engine Digital Asset Manager Service Layer Persistence Layer Database Nodes Shared FS 19

22 Kargo s Architecture: Product Overview Kargo Framework Zend Framework plus mobile specific Kargo class library. Basis for all other products Karpet Fever Kamp Kellner Kargo DAM Kargo Platform Feed-based mobile magazine application with community features. Abstracts mobile specifics. Mobile downloadable content and application storefront application, with cross-carrier billing Web-based mobile messaging application. Allows for editorial content and costumer interaction. Mobile Messaging Application Server. Unified programming model, across all messaging protocols. Digital Asset Management System. Offers a document-oriented database concept for content. The core business logic application server. Handles subscriber management, device detection, reporting, ad serving, etc. All front-end applications use this as their back-end. 20

23 The Kargo Framework Zend Framework offers a lot already, but here is what we had to do ourselves: Kargo_Daemon - toolkit for forking, shared objects, IPC, etc. Kargo_Dam - wrapper classes for our digital asset management system Kargo_Db - additions to Zend_Db_Adapter, supporting fail-over and load-balancing. Kargo_Event - wrappers for our libevent extension for asynchronous socket programming. Kargo_Mime - a full and flexible MIME implementation to use beyond Mail. Kargo_Mm7 - a full MM protocol implementation. Kargo_Platform - controller plug-ins for interaction with platform services Kargo_Service - a set of Zend_Service style third-party web-service wrappers for our partners. Kargo_Smpp - implementation for OpenMarket, SinglePoint, mblox and Standard SMPP v3.4. Kargo_WebDav - a webdav implementation 21

24 Example: Approach for the Mobile Web Architecture Problem: Classical web server models are sub-optimal for a lot of new applications. Usually solved with lots of workarounds, mostly incorporating caching techniques on many levels. Solution: Cleanly decouple front-end logic from core services and let the back-end be a stateful application. This is common is Java-based architectures, but never seen in pure PHP. 22

25 Example: Mobile Web Architecture Apache/PHP5 node 1 Apache/PHP5 node 2 Karpet Instance Karpet Instance... Zend_XmlRpc Backend Node 1 Backend Node 2 Backend Node 3 Platform Server PHP-CLI Platform Server PHP-CLI Platform Server PHP-CLI... ext/libevent ext/libevent ext/libevent Platform server is a stateful application using asynchronous http handling 23

26 What s going on (simplified) Karpet Instance Platform Server PHP-CLI Message Server PHP-CLI 1: first request 2: start session (headers) return: device, user, carrier, etc. 3: write session 4: another request... 5: sign up [sends text message to user] 6: sendsms()... 24

27 How it works 1. Setup Db, logger, etc. only on startup 2. Start Http server with it s socket being monitored by the underlying event notification system 3. On an incoming http request, the handlerequest callback is triggered, serving the xml rpc request Platform Server (simplified) PHP-CLI class PlatformServer implements Kargo_Event_Http_Handler { private $_rpc_server;... public function construct() { // 1) setup db connection // 2) setup instance of Zend_XmlRpc_Server and add the service classes } public function handlerequest(kargo_event_http_request $r) { $request = new Kargo_XmlRpc_Request_Event($r); $this->_rpc_server->setrequest($request); return $this->server->handle(); } } Kargo_Event::init(); Now we can keep our back-end services running stateful $server = new Kargo_Event_Http_Server($options, new PlatformServer); $server->enable(); Kargo_Event::dispatch(); Kargo s libevent PHP extension OS Kernel notification layer (KQueue, epoll, etc) 25

28 Performance Baseline: Apache/mod_php5, pre-fork, no opcode cache Setup: PHP on Macbook Pro/OS X (KQueue) with libevent and Zend Framework 1.5 Concurrency level: 50 requests Apache: Mean requests per second: 8.76 Kargo (one process): Mean requests per second:

29 Pros Incredible speedup Low CPU and memory utilization Surprisingly stable (runs for months now under heavy loads) No need for memcached, opcode cache, db connections pooling, or similar techniques. Back-end applications are now stateful. Allows for lazy loading, better task scheduling, etc. Lot s of database queries can be kept in memory. 27

30 Cons Developers have to be more aware of memory management Some people call it abuse of PHP, since it ignores the request based PHP execution cycle. Garbage collection a request tear-down is not called. Doesn t work well with Zend_Controller_Front, because of extensive cyclic referencing (memory leaks) 28

31 However Current server does not leak memory. Near Future: PHP 5.3 adds control over the garbage collector, which adds additional support for this scenario. 29

32 Conclusions Use of Zend Framework and it s principles opens paths into solid software architectures. Using PHP as a general purpose programming language has shown to be surprisingly fast and robust in a production environment. Kargo has successfully replaced Java-typical application servers with PHP, leaving a pure single choice of technology across all tiers. Kargo has build an enterprise-grade architecture, simple and flexible enough to react to the complex requirement in the mobile domain. 30

33 /dev/random How about building an app server which passes Zend_Controller_Request objects to a pool of worked? How about a restricted ZF app server similar to Google App Engine, running on Amazon EC2? 31

34 Thank You! text FH to