Tweakers.net Developers Summit - Winfred Peereboom - Architecture for the future.

1. Architecture for the future Winfred Peereboom, w.peereboom@vnumedia.nl

2. Imaginethis You are in charge of the architecture

3. What are the requirements A website for selling shoes Site can handle a lot of traffic Marketing must have good traffic insight Connected to the backoffice for orders Good uptime Vaguerequirements…….. As always, we developers say

4. Many difference in definition of architecture Information architecture Application architecture Software architecture

5. Theory Scalability Modifiability Simplicity Reliability Performance Software Architecture in Practice by Len Bass, Paul Clements, Rick Kazman, Ken Bass.

6. Practice. Make our technology stack Should do the job…

7. Conclusion so far.. Theory is to vague to make a good selection in components Just pick some hot stuff doesn’t feel good Will I be really ready for the future?

8. Still got some questions.. Who is going to maintain the components? Do I really need so much functionality What is the time schedule for this to implement? How do I get everything under control? Problems that you just don’t want to have

9. Let’s keep close to the facts Development team Sysadmin Organization

10. Important criteria Meet concrete requirements (if they are there) Stable and in Repository Knowledge available (documentation, best practises, internal/external development) Learning curve for a component Is the technology proven for my goal How much do I use of the component functionality

11. The component selection VNU Media issues with Hadoop No failover for Hadoop’snamenode From PHP hard to append to Hadoopfilesystem

12. Architecture for the near future

13. Things to keep in mind There can be requirements that needs “state of art” components or even unstable, but be very very careful. Focus on abstraction in code, so you can change Keep track of updates of your components during development Don’t let business requirements instantly change your mind about a component Never stop experimenting with new tools and components, maybe it can make your architecture better in the future.

14. It’s better to create an architecture that lasts for one year, than trying to create an architecture that lasts for ten years. Stefan Priebsch