Finally finished converting a 220k LOC codebase at work to ZIO. It was a ton of work but totally worth it in my opinion. I learned a lot in the process too. Thanks for the awesome library @jdegoes and all the #zio contributors. @adamfraser too for being so helpful on Discord.
@jdegoes @adamfraser Technically you can introduce ZIO gradually into your project, and I have done that successfully before, but I went all-in because I wanted to leverage all of ZIO's capabilities in the project and not just in certain "islands" of code. Removing some 2.12 deps was a plus too.
@jdegoes @adamfraser Some immediate benefits were: async stack traces (much nicer coming from Future). Plus no more ExecutionContext everywhere. This migration exposed some operations that were running on unintended ExecutionContexts.
@jdegoes @adamfraser And maybe the biggest thing for me is principled error handling reflected in the types. This is big. Now I have confidence about which errors I've already handled, and which I haven't. ZIO exposed a lot of cases which weren't explicitly being considered.
@jdegoes @adamfraser Upcoming tasks:
- Migrate to ZIO test
- Replace remaining usages of Akka
- Increase parallelism where it makes sense: sequencePar, sequenceParN, etc.
- Try to replace Play bootstrap + stop hooks with ZManaged
- Migrate to ZIO test
- Replace remaining usages of Akka
- Increase parallelism where it makes sense: sequencePar, sequenceParN, etc.
- Try to replace Play bootstrap + stop hooks with ZManaged
@jdegoes @adamfraser Oh, and also IntelliJ doesn't hate me anymore. 😅 (monad transformer type inference issues)
