Stefan Priebsch (16.Nov.2009)
Talk at International PHP Conference 2009 (English - UK)
Architecture, like art, creates controversy. What some perceive as beautiful, others consider ugly. Since the architecture of a web application is far less "visible", it is important to make the right design decisions when creating a web application. Which architecture makes an application scalable and maintainable? How can we plan for extensibility, without over-engineering the application?
Quicklink: https://joind.in/1045
Slides: Web Application Architecture
By clicking this button you are declaring that you are the speaker responsible for it and a claim request will be sent to the administrator of the event.
If the claim is approved you will be able to edit the information for this talk.
Are you sure?
16.Nov.2009 at 11:40 by Georg Gradwohl
The keynote provided a good overview about the state-of-the-art architecture and touched also a wide range of common pitfalls and misstakes. As Surfrdan mentioned a concrete example or a short case-study would have helped us to get more out of it. But all in all, a great prelude to the architecture day, which gave me some good approaches to get off from. Looking forward to your next session.
16.Nov.2009 at 11:45 by Stefan Priebsch
I would have loved to get more into details, but it was not possible to squeeze more content into one hour. I had originally (also) proposed a half-day architecture workshop, but only got to do the regular session.
16.Nov.2009 at 12:16 by Georg Gradwohl
The keynote provided a good overview about the state-of-the-art architecture and touched also a wide range of common pitfalls and misstakes. As Surfrdan mentioned a concrete example or a short case-study would have helped us to get more out of it. But all in all, a great prelude to the architecture day, which gave me some good approaches to get off from. Looking forward to your next session.
16.Nov.2009 at 13:03 by Kyle Caine
Really a nice talk - I enjoyed it a lot. Still a lot of software developers underestimate the parallels between "regular" engineering and software engineering: Do your work properly at the beginning of your project or you'll loose the battle. Thank you Stefan for the entertaining overview over architectual pitfalls. I'm eager to see more of the architecture day.
18.Nov.2009 at 12:03 by Sascha Ternes
A very interesting and well presented talk, I especially enjoyed your analogies to buildings and your refreshing presentation style. A good choice for the first conference talk!
18.Nov.2009 at 21:50 by Stefan Priebsch
I'm sorry, "Anonymous", that the session did not work out for you. And I regret to inform you that I have to consider an anonymous one-line feedback as spam. Did it really take you two days to realize that you did not like my session at all?
I'm all in to listen and respond to constructive criticism. What would you have expected from the session? What was missing for you, what was in your opinion superfluous?
Feel free to email me privately at stefan@thephp.cc.
23.Nov.2009 at 05:49 by Tobias K.
(I'm not the anymous.)
But also for me - to much introduction, nothing really new and PHP special. I arrived 10 min to late, so I didn't got the opening. But about 30 min for various buildings/architecture and their history is not what I thought this talk is about.
I was expection php-specific architecture and design patterns that you are using in your daily projects. As you're well-known and you're long into this business, you'll have a lot of experience. So it would have been great if you could have spoken about that.
23.Nov.2009 at 09:03 by Stefan Priebsch
Thanks for you feedback, tobiask. I'm sorry my talk did not give you what you had expected. In the "building" part that you've mentioned, I've tried to make a connection between building and software architecture, and show that they share similar problems. The idea was to give people a less abstract view on software architecture. This seems to have worked for a part of the audience, for others, including you, I did not manage to get the point across, so I'll probably have to rethink this approach.
As for architectural patterns, I've covered quite some (Layered architecture, database-centric architecture, MVC, pipes and filters, blackboard). Covering design patterns is a different level of abstraction, and has really nothing to do with architecture, as the following Wikipedia articles will tell you:
http://en.wikipedia.org/wiki/Design_pattern_%28computer_science%29
http://en.wikipedia.org/wiki/Architectural_pattern_%28computer_science%29
Know of an event happening? Let us know! We love to get the word out about events the community would be interested in and you can help us spread the word!
16.Nov.2009 at 10:12 by Dan Field
Thanks Stefan. An interesting talk and plenty to think about. You covered all the main areas but It would have been nice to see a few more details. Or perhaps some best practice by example.