Wednesday, 27. September 2017 09:30 - 10:00 (30 min)
The DevOps movement has greatly enhanced how development results are transitioned to operations. However, developers still write code keeping only the functional requirements in mind. Whether this code holds up in a production environment or not is anyone's guess.
In this session we highlight best-practices, patterns to follow and anti-patterns to avoid in order to create software, specifically in an OSGi + Sling + AEM context, that comes without bad awakenings in production, and that enables an operations team to run and monitor your software, and to resolve issues themselves, without giving you the weekend call.