This is a presentation which was held on 24 September 2015 by Web Developer Boy Wijnmalen at the Breda PHP Meetup. Who CM telecom is? CM first started in 1999 as a messaging company, but nowadays we'd like to think about ourselves as one platform for messaging, payments, apps and voice. We believe mobile is the most effective way to engage with customers. Because we are a global mobile services company we deliver 24 hours a day, 365 days a year support for our clients worldwide from our headquarters here in Breda. Besides that, all our clients are provided with real-time statistics and insights to all their mobile transactions going through our platform. With clients spanning financial institutions, governments and TV stations good up time is very important. 25% of our employees are developers, our development team is loosely divided into three departments, we have both.NET and PHP developers, they make up the backend part, we have a Frontend development team and at last we have a mobile development team. Introduction into CM Development Challenges This presentation reflects CM Telecom's vision on Future Web Development, the why, how and which technologies CM is currently implementing. One of the learnings of last period is that development time decreased rapidly by using tools such as Composter, NPM, Bower & Gulp. These tools make our Development live easier. After starting using these tools we're noticed that development time is decreasing, but other delays are revealed such as delays in testing, in deployment, and delays in network & server configuration. First CM had to tackle delays from developers point of view, now we want to tackle other challenges. One is monolithic vs micro-services approach, the second is called the 'Continuous Delivery' principle. High-light: Accelerated Time to Market: If you can deliver software faster to your customers you are potentially one step ahead of the competition. Building the Right Product: Frequent releases let the development teams obtain user feedback more quickly. This lets them work on only the useful features. Improved Productivity and Efficiency: If you only focus on the useful features you will save time on development as well as testers and developers. Reliable Releases: The risks associated with a release have significantly decreased, and the release process has become more reliable. Improved Product Quality: The number of open bugs and production incidents will decrease big time. Improved Customer Satisfaction: A higher level of customer satisfaction is achieved.

1. WWW.CMTELECOM.COM
Welcome!

2. Our vision on
the future of
web development

3. CM Development

4. Next challenge
• Micro Services

5. Header can be included in every application

6. CM Style guide

7. Next challenge
• Micro Services
• Continuous Delivery

8. Continuous Delivery
Werner Vogels
CTO @ Amazon
“You build it, you run it”

9. Continuous Deployment
• Accelerated time to market
• Building the right product
• Reliable releases
• Improved Product Quality
• Improved Customer Satisfaction

10. DevOps
“development method about
communication, collaboration,
automation and cooperation
between software engineers and
other IT professionals.”
Source: https://en.wikipedia.org/wiki/DevOps

11. DevOps
• To be able to increase the rate of production releases
• To increase the focus on test automation and
configuration management tools
Why?

12. Downsides
• Is it fair to make a developer responsible for two different expertises?
• Less feeling and overview of what is happening

13. Conclusion
Downsides? Yes
Upsides? Yes
The advantages far outweigh the disadvantages

14. WWW.CMTELECOM.COM
THANKS FOR LISTENING!
AND
WE ARE HIRING!