Configure Once, run everyhere! Configuration with Apache Tamaya BASEL BERN BRUGG DÜSSELDORF FRANKFURT A.M. FREIBURG I.BR. GENF HAMBURG KOPENHAGEN LAUSANNE MÜNCHEN STUTTGART WIEN ZÜRICH About Me Anatole Tresch Principal Consultant, Trivadis AG (Switzerland) Star Spec Lead Technical Architect, Lead Engineer PPMC Member Apache Tamaya @atsticks
[email protected] [email protected] 6.09.16 Configure once, run everywhere 2 Agenda ● Motivation ● Requirements ● The API ● Configuration Backends ● Demo ● Extensions 6.09.16 Configure once, run everywhere 3 Motivation 6.09.16 Configure once, run everywhere 4 What is Configuration ? Simple Key/value pairs? Typed values? 6.09.16 Configure once, run everywhere 5 When is Configuration useful? Use Cases? 6.09.16 Configure once, run everywhere 6 How is it stored? Remotely or locally? Classpath, file or ...? Which format? All of the above (=multiple sources) ? 6.09.16 Configure once, run everywhere 7 When to configure? Develpment time ? Build/deployment time? Startup? Dynamic, anytime? 6.09.16 Configure once, run everywhere 8 Configuration Lifecycle ? Static ? Refreshing ? Changes triggered ? 6.09.16 Configure once, run everywhere 9 Do I need a runtime ? Java SE? Java EE? OSGI? 6.09.16 Configure once, run everywhere 10 Requirements 6.09.16 Bezeichnung Präsentation Requirements ● Developer‘s Perspective ● Architectural/Design Requirements ● Operational Aspects ● Other Aspects 6.09.16 Configure once, run everywhere 12 Developer‘s Requirements ● Easy to use. ● Developers want defaults. ● Developers