:PROPERTIES: :ID: 0b91d24c-a454-44e8-a64a-59420da910d8 :END: #+title: Toward IROH 2.0 #+Author: Yann Esposito #+Date: [2023-09-20] - tags :: - source :: * Local changes ** Use reitit ** OpenTelemetry - https://github.com/steffan-westcott/clj-otel - https://www.elastic.co/guide/en/apm/guide/current/open-telemetry.html * Global changes - Monolith repository vs micro services - How to slowly migrate? Code organization: 1. Keep Monolith? + Good: - easy to make global change - easier to secure and maintain libs. - huge battle tested toolset (it simply works) + Bad: - harder to change lib - harder to experiment Ideas: Isolate part of the code which has been very stable for a few years. Keep it as IROH-Core. Support a way to add services using this core. Connection? - RAM (require iroh-core....) - force usage of exactly the same libs