• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Zend Platform

Zend Platform






Total Views
Views on SlideShare
Embed Views



3 Embeds 45

http://pointbeing.net 34
http://www.pointbeing.net 9
http://www-dev.pointbeing.net 2



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    Zend Platform Zend Platform Presentation Transcript

    • Zend Platform
    • Zend Platform
      • We have it
      • It's not cheap
      • We're using it, but to nowhere near its full potential
    • What is Zend Platform?
      • It's a piece of software which sits between PHP and the server; a managed environment in which our PHP code runs
      • It gives us visibility on what our code is doing in production (event log, profiling)‏
      • And a lot of other cool tools
    • What are we Using?
      • Event Log
      • Accelerator
      • The tip of the iceberg
    • Even Actions: proactive monitoring
      • Post XML to a URL
      • Send email – without cluttering up the application code
      • Send SNMP trap, which can be caught by Nagios
    • Session Clustering
      • PHP Sessions can be troublesome in a multi-server environment
      • Need for NFS server/database/Session Server
      • Works like JBoss session clustering
      • Sessions can live in memory
      • Simply a case of “switching it on”
    • Caching
      • Platform can act as a “back-end” for caching
      • Zend Framework provides a simple API
    • Caching - example
    • Caching - benefits
      • Cache shared between servers
      • Cache could be shared between and applications e.g. Content API calls
      • No fuss with cache files/directories/permissions/sysadmins
      • No need to clean up expired cached objects
    • Job Queue
      • Ability to “offline” processing and have it done asynchronously
      • Asynchronous processes run within Platform, the same as “normal” code
    • Java Bridge
      • Our page-generation times are relatively slow
      • Most of that is SOAP calls to Java services
      • Java Bridge allows us to import Java objects and treat them as if they were native PHP objects
      • So we could write an e.g. SessionServer client in Java, which talks to SessionServer over RMI. Performance increase could be impressive (requires benchmarking)‏
    • Going Forward
      • This is only a few of the features, let’s get thinking about how we can use some of this stuff
      • Work out which issues are critical enough to escalate to Nagios
      • Try to reduce the number of errors/notices we are creating in production