Using Scala to Drive Modernization in Enterprise Environments

Enterprise Environments tend to show resistance to change. innoQ has been involved in many modernization projects for customers, especially in combination with vast architectural tasks and re-engeering. Based on this experience, Martin will show how Scala can help to push modernization efforts and bring the desired changes to these companies.

http://lampwww.epfl.ch/~hmiller/scala2014/index.html

Transcript

1. We’ll take care of it. Personally! Using Scala to Drive Modernization Scala 2014
 July 28th, Uppsala, Sweden 
 Martin Schmidt, innoQ Switzerland
2. We’ll take care of it. Personally! Using Scala to Drive Modernization in Enterprise Environments
3. © 2011 innoQ Deutschland GmbH Who am I?
4. © 2011 innoQ Deutschland GmbH If so, how many?
5. © 2011 innoQ Deutschland GmbH
6. © 2011 innoQ Deutschland GmbH Using Scala
7. © 2011 innoQ Deutschland GmbH Enterprise Environments
8. © 2011 innoQ Deutschland GmbH
9. © 2011 innoQ Deutschland GmbH Drive Modernization
10. © 2011 innoQ Deutschland GmbH
11. © 2011 innoQ Deutschland GmbH Main Drivers for Modernization Software Solutions never 
 fit current requirements
12. © 2011 innoQ Deutschland GmbH
13. © 2011 innoQ Deutschland GmbH
14. © 2011 innoQ Deutschland GmbH
15. © 2011 innoQ Deutschland GmbH Evolutionary Modernization
16. © 2011 innoQ Deutschland GmbH
17. © 2011 innoQ Deutschland GmbH ?
18. © 2011 innoQ Deutschland GmbH Architecture Drivers AUTOMATIZATION (STRAIGHT THROUGH PROCESSING) ! BUSINESS PROCESS OUTSOURCING MANUAL TASK OUTSOURCING ! BUSINESS SERVICE PROVIDING ! LOW TCO ! SHORT TIME TO MARKET
19. © 2011 innoQ Deutschland GmbH Event Driven Architecture
20. © 2011 innoQ Deutschland GmbH Drivers for choosing a programming environment Costs! Time to market Quality Human Resources Licenses • Fewer bugs => higher quality • Higher developer productivity => shorter time to market – Faster development of new features – Easier integration of changes – DSL-based development (more idiomatic/precise, bridges the gap) • Quick ramp-up of new resources => reduced HR cost, shorter time to market • Portable platform => higher quality, shorter time to market • No vendor lock-in => optimize license cost
21. © 2011 innoQ Deutschland GmbH Why Scala? • Because it … – Helps increasing code Quality – Provides the means to achieve shorter time to market – Can be used to allow a quick ramp-up for new employers and as such decrease Human Resources costs – No vendor lock-in => optimize License costs
22. © 2011 innoQ Deutschland GmbH Scala features supporting these drivers • Rich type system
 (e.g. traits, co-variants, self types, Try/Option, pattern matching) ! ⇒Less errors => higher Quality ! • More expressive code
 (e.g. through type inference, concise syntax, compile time reflection for code generation, internal DSL) ! ⇒Improve understandability of code => higher Quality, reduced Human Resources costs ! ⇒Less code to write => higher Quality, shorter Time-to- Market
23. © 2011 innoQ Deutschland GmbH Scala features supporting these drivers • Macro annotations / parser/generator ⇒ Improved Expressiveness through DSLs ! • Functional idioms
 (e.g. high order functions, monads, for-comprehension) ⇒Focus on “what to do” and not “how to do it” ! ⇒ higher Quality, shorter Time-to-Market
24. © 2011 innoQ Deutschland GmbH Scala Macros
25. © 2011 innoQ Deutschland GmbH Generate optimized boilerplate
26. © 2011 innoQ Deutschland GmbH Checking for syntactical (structural) backward compatibility of structures
27. © 2011 innoQ Deutschland GmbH Alternatives to Macros
28. © 2011 innoQ Deutschland GmbH Framework 
 vs 
 Business Code
29. © 2011 innoQ Deutschland GmbH Potential risks when selecting Scala • Availability of skilled resources – Focused training and on-boarding process for new employees (they need to be trained anyway) ⇒Mitigation: Separate framework and business logic (reduce perceived complexity) ! • Scala is not yet as established as other languages (e.g. Java/C#/…) – But looks very promising (*) ⇒ It is JVM- and open-source-based (*) http://typesafe.com/company/casestudies
30. © 2011 innoQ Deutschland GmbH logical
31. © 2011 innoQ Deutschland GmbH psychological
32. © 2011 innoQ Deutschland GmbH http://commons.wikimedia.org/wiki/File:Cat_into_the_box.jpg
33. © 2011 innoQ Deutschland GmbH !
34. We’ll take care of it. Personally! Thank you! Martin Schmidt martin.schmidt@innoq.com http://www.innoq.com +41 (0) 79 5226816 © 2011 innoQ Deutschland GmbH