# modularization Published articles for modularization. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How we standardized MariaDB in our Integration Server DevFeed: [How we standardized MariaDB in our Integration Server]() Original publisher: [Read original article]() Author: Eloy Gonzalez Published: 2026-03-26T18:59:43Z Content type: article Language: en Sources: [Wealthfront]() Topics: [MariaDB](), [Testing](), [migration](), [Databases](), [Jenkins](), [CI/CD](), [Back end]() Tags: [architecture](), [backend](), [careers](), [ci-cd](), [data](), [engineering-culture](), [hibernate](), [infrastructure](), [integrity](), [jenkins](), [locking](), [migration](), [modularization](), [production](), [sql](), [testing](), [tests](), [wealthfront-engineering]() ### AI overview Wealthfront describes migrating its Integration Server from HSQLDB to MariaDB to improve parity with production. The article covers the migration strategy, architectural hurdles, and benefits for data integrity, concurrency, locking, and production-like testing. ### Source excerpt Engineering at Wealthfront is centered on the idea that code should be written to facilitate testing, not the other way around. Without a staging environment to fall back on, we maximize confidence through a sophisticated, multi-layered testing strategy. While unit tests provide our most rigorous line of defense, our Integration Server is the workhorse that... Read more ## XcodeGen and the quest to modularize the Wealthfront iOS app DevFeed: [XcodeGen and the quest to modularize the Wealthfront iOS app]() Original publisher: [Read original article]() Author: Matthew Bommer Published: 2026-03-02T17:56:41Z Content type: tutorial Language: en Sources: [Wealthfront]() Topics: [XcodeGen](), [iOS](), [Swift](), [Xcode](), [Command-line interface](), [configuration](), [Development]() Tags: [automation](), [careers](), [declarative](), [infrastructure](), [ios](), [modularization](), [swift](), [wealthfront-engineering](), [xcode](), [xcodegen](), [yaml]() ### AI overview Wealthfront describes adopting XcodeGen to generate Xcode project files from declarative YAML, reducing project-file merge conflicts and making build configuration more reviewable. The team also plans to use it to support modularizing its large iOS application into independently compilable modules. ### Source excerpt Every iOS application starts as a monolith. Xcode's default project structure places all source files, resources, and build configuration into a single module (or target, for all the iOS devs reading this). For small apps, this works fine. For a 10+ year old financial application with roughly 2,000 Swift and a handful of Objective-C files,... Read more ## Modularizing Rails Monoliths One Bite at a Time DevFeed: [Modularizing Rails Monoliths One Bite at a Time]() Original publisher: [Read original article]() Author: Doximity Published: 2023-12-05T13:00:00Z Content type: article Language: en Sources: [Doximity]() Topics: [Ruby on Rails](), [Refactoring](), [modules](), [Architecture & Design](), [Microservices]() Tags: [microservices](), [modular-monolith](), [modularization](), [modules](), [rails](), [refactoring](), [ruby](), [ruby-on-rails]() ### AI overview The article describes using a phased refactoring approach and the packwerk gem to modularize growing Rails monoliths into modules with enforced boundaries. It presents the modular monolith as a lower-complexity alternative to adopting microservices and references Doximity's experience. ### Source excerpt As Rails monoliths grow, coupling becomes increasingly difficult to manage. Developers often reach for microservices to help simplify things, but instead find higher complexity. The Modular Monolith approach is a proven, lightweight alternative that offers the benefits of enforced boundaries without being cumbersome. I spoke at the 2023 Rocky Mountain Ruby conference on how teams can use a phased approach to refactoring toward this style using the packwerk gem. At Doximity, we've used this gem and a phased approach to break some of our most critical rails applications into modules that are easier for our teams to work with. In November, 2023, I also chatted with Elise Shaffer on The Ruby on Rails Podcast about our experience with application modularization at Doximity. Be sure to follow @doximity_tech if you'd like to be notified about new blog posts. ## Scaling Teams Mobile Development -- The Mental Model DevFeed: [Scaling Teams Mobile Development -- The Mental Model]() Original publisher: [Read original article]() Author: Anand Nath Published: 2023-03-03T02:22:43Z Content type: article Language: en Sources: [Android@Microsoft - Medium]() Topics: [Mobile](), [Development](), [App](), [Code](), [interfaces]() Tags: [android](), [code](), [design-patterns](), [development](), [integration](), [interfaces](), [ios](), [mobile](), [mobile-development](), [modularization](), [patterns]() ### AI overview This article presents a mental model for scaling partner integrations in the Microsoft Teams mobile codebase. It describes the existing tight coupling between feature producers and consumer entry points, then proposes decoupling them through interfaces, a producer registry, and a manager that handles feature discovery and coordination. ### Source excerpt Scaling Teams Mobile Development -- The Mental Model In the article Scaling Teams Mobile Development -- Evolving the design pattern we explored how multiple partner teams working on a large code base can be streamlined by employing the contributor design pattern. I decided to write this article as a prequel. In this article we will discuss the problem statement in a more generic way and draw some parallels with popular design patterns. Photo by Xavi Cabrera on Unsplash We started with the following mission statement in mind: Make partner integrations with Teams mobile easier, well segregated, with clear protocols. Teams is a complex mobile application with a LOT of integration points. Partner teams surface their features through these entry points. The following image highlight few entry points available in Teams. Few entry points in Teams mobile app When we looked at the partner integration story in Teams codebase, it became evident that the whole integration story is a Producer-Consumer design pattern which is not implemented correctly. Producer -- Consumer deep coupling Here is the mental model that we built: Entry points are consumers of features and partner teams are producers of features. In the existing method, each partner team directly integrated with the entry point. This meant each consumer had to know the producers directly and when a new producer was added, the consumer had to be updated. This resulted in tight coupling. This is not a scalable model. N x N relationship between Producers and Consumers For the system to scale we need to decouple the producers and the consumers and build strong contracts between them. We wanted to safeguard changes to the consumer. At the same time, we wanted to make the producers independent and able to churn out their features fast. We also wanted to centralize control on producers and its features for deciding their ordering, filtering, enablement etc. So, we evolved this design pattern, where we define multiple Feature in ## Mastering The Gradle Dependency Tree DevFeed: [Mastering The Gradle Dependency Tree]() Original publisher: [Read original article]() Author: Ishan Khanna Published: 2023-01-11T23:09:51Z Content type: tutorial Language: en Sources: [Ishan Khanna]() Topics: [Gradle](), [modules](), [Library](), [Maven Central]() Tags: [debug](), [dependencies](), [dependency](), [gradle](), [library](), [maven-central](), [modularization](), [modules](), [resolved](), [transitive-dependencies]() ### AI overview This tutorial explains Gradle dependencies, transitive dependencies, dependency configurations, and dependency trees. It also presents five ways to generate a dependency tree and discusses managing versions to avoid conflicts and unnecessary project bloat. ### Source excerpt Learn everything about the Gradle Dependency Tree and Five Different Ways to Generate Them. ## Impact of Dependency Tree Depth on Gradle Builds DevFeed: [Impact of Dependency Tree Depth on Gradle Builds]() Original publisher: [Read original article]() Author: Ishan Khanna Published: 2022-12-05T07:46:58Z Content type: tutorial Language: en Sources: [Ishan Khanna]() Topics: [Gradle](), [build performance](), [build times](), [modules](), [Caching]() Tags: [build](), [build-times](), [caching](), [gradle](), [modularization](), [tips-and-tricks]() ### AI overview This tutorial examines how dependency tree depth affects Gradle build times in modularized, multi-project builds. It analyzes changes at the top, middle, and bottom of the dependency tree and explains Gradle tasks, dependency graphs, and task output caching. ### Source excerpt In this post, Ishan shows the impact of dependency tree depth on Gradle Builds with a complete analysis of changes at the Top, Middle, and Bottom of the Dependency Tree. ## Building Plugable Features on Android DevFeed: [Building Plugable Features on Android]() Original publisher: [Read original article]() Published: 2022-08-07T15:05:54Z Content type: tutorial Language: en Sources: [Blogs on Ryan Harter]() Topics: [Gradle](), [App](), [configuration](), [screen](), [feature flags]() Tags: [android](), [building](), [configuration](), [dependencies](), [developer](), [feature-flags](), [gradle](), [modularization]() ### AI overview This article discusses modularizing Android projects with Gradle and designing reusable developer settings features. It describes aggregating feature dependencies and moving each feature's debug configuration alongside the code it configures. ### Source excerpt As Gradle projects and their teams grow, modularization becomes an important tool to help ensure developers can continue to be productive without stepping on each other's toes. This can lead to some interesting architectural challenges, however, when creating features that require aggregating dependencies. One example of a feature like this could be a developer settings screen, which allows configuration of different features within an app, and whose features might change between apps. ## Dagger Tips: Guide to using Dagger-Android effectively DevFeed: [Dagger Tips: Guide to using Dagger-Android effectively]() Original publisher: [Read original article]() Author: Gabor Varadi Published: 2021-02-13T05:05:50Z Content type: tutorial Language: en Sources: [Stories by Gabor Varadi on Medium]() Topics: [Dagger](), [Android](), [Architecture & Design](), [Development](), [Scalability]() Tags: [android](), [dagger](), [dagger-2](), [dagger-android](), [dependency-injection](), [development](), [guide](), [interface](), [modularization](), [module](), [scalability]() ### AI overview A guide to using Dagger-Android, explaining its field-injection approach, the modularization constraints it addresses, and alternatives involving interfaces or shared superclasses. The article notes that Dagger-Android has been superseded by Hilt for common injection cases. ### Source excerpt Something people could ask me as they're reading this title: "Hold on a second, isn't Dagger-Android no longer in active development? Isn't it made obsolete with the introduction of Hilt?" Technically, yes. Dagger-Android is superseded by Hilt. So there is a good chance that if you are already using Hilt, then for the most common cases (injecting Activity, Fragment, ViewModel, Worker), you don't need to think about Dagger-Android whatsoever. However, as I still see @ContributesAndroidInjector popping up every now and then, I feel that it's best if I write an article on how it works, what it intended to solve, how to use it, and how NOT to use it (for better scalability). What was Dagger-Android? Dagger-Android was a way to field-inject classes (not necessarily just Android classes since Dagger 2.20+) without having to define a fun inject(target: MyConcreteClassTarget) injector method on the component -- as we don't know the class itself. When do you want to avoid creating fun inject(t: T) in a component? After all, this is what normally allows field injection to be type-safe. The answer is, when you can't. If you use a modularization pattern where :app contains the ApplicationComponent(or SingletonComponent), then while ApplicationComponent can see any Activity or Fragment within the app, the submodules don't see :app and therefore don't see ApplicationComponent. Therefore, they can't call component.inject(this)! On the other hand, if you were to define an Application.ActivityLifecycleCallbacks to do it automatically, that wouldn't work with the standard approach -- as you see only the superclass, but not the concrete class! So if one wants to use field injection with our provided restrictions, there are two options: Expose an interface from the child module that defines the injection targets, and implement that on the ApplicationComponent -- then make it possible to access it (for example, using the ApplicationContext for lookup) and cast it to the interface to be abl ## Structural and navigation anti-patterns in modularized Android applications DevFeed: [Structural and navigation anti-patterns in modularized Android applications]() Original publisher: [Read original article]() Author: Gabor Varadi Published: 2020-12-25T11:38:05Z Content type: article Language: en Sources: [Stories by Gabor Varadi on Medium]() Topics: [Android](), [Gradle](), [modules](), [navigation](), [Code](), [Dagger](), [Dependency injection](), [RxJava]() Tags: [android](), [android-app-development](), [antipattern](), [architecture](), [clean-architecture](), [code](), [dagger](), [dagger-2](), [dependency-injection](), [domain-driven-design](), [gradle](), [modularization](), [modules](), [navigation](), [navigation-architecture](), [rxjava]() ### AI overview This article examines structural and navigation anti-patterns in modularized Android applications. It traces the history of Android Clean Architecture and argues that organizing an application around top-level data, domain, and presentation modules can be problematic, particularly when the structure is adopted from educational examples rather than feature-based organization. ### Source excerpt Structural and navigation anti-patterns in multi-module and modularized applications: The case against "Android Clean Architecture" and the "domain" moduleTop-level "domain" module is a code smell. Merry Christmas to all! The subject of this article is one that has been on my mind for a very long time. After all, "Clean Architecture" is often seen as the end goal, the hallmark of the finest of Android application code structure -- it is the best of the very best. The name itself, "Clean Architecture", signals that it's a good thing ~ after all, who wants to work with "messy" code in comparison? Of course, the title of this article shows that this isn't the conclusion we'll come to. The following tweet is closer to our final evaluation -- let us analyze why it might be accurate. Clean architecture + Android for us was like building a beautiful sailing boat in your backyard because someone on TV convinced you it's better for crossing the sea than an inflatable, while you live in the mountains and also your house is on fire. https://t.co/iGqy25wk7m The history of "Android Clean Architecture"The origins To understand "Clean Architecture" as done on Android, we must trace it back to its roots, and where/when it was made popular in the first place. As far as I'm aware, it dates back to 2014, the original proposition in "Fernando Cejas: Architecting Android... the clean way?". It was a highly influential article, as it revolutionized the structure of Android apps. Code that is actually separated across layers (back when Fragments were untrustworthy, and all code was in OS-level components), rather than just throwing everything into 2000+ line Activities? A pioneer of its time. One interesting decision however in the representative sample code was that in order to signify the strict separation of layers, these layers were each separated from one another using top-level Gradle modules, each labeled data, domain, and presentation. As we will see, this is the downfall of the sampl ## Android library development - Modularization DevFeed: [Android library development - Modularization]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2020-11-04T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [Android Library](), [Library](), [SDK](), [Development](), [Android Gradle Plugin](), [Gradle](), [Jetpack]() Tags: [android](), [android-gradle-plugin](), [android-jetpack](), [android-library](), [blogs](), [development](), [gradle](), [kotlin](), [library](), [maven](), [modularization](), [sdk]() ### AI overview This article explains modularization challenges in Android libraries and SDKs, including missing submodule dependencies and unintended exposure of submodule APIs. It presents three approaches: publishing submodules to Maven, bundling them into a fat AAR, or creating a single-module SDK. ### Source excerpt With modularization being all the hype, should you also modularize an SDK? Are fat aar files really needed? And how do you prevent internal APIs from being exposed on your public interface? ## Modularization - Lessons learned DevFeed: [Modularization - Lessons learned]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2019-06-12T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [modules](), [Gradle](), [Android Studio](), [Git](), [Kotlin Multiplatform]() Tags: [android-studio](), [architecture](), [blogs](), [git](), [gradle](), [kotlin-multiplatform](), [modularization](), [modules](), [software-engineering](), [tips]() ### AI overview The article shares lessons learned from modularizing apps at Philips Hue. It covers simplifying module configuration, visualizing module dependencies, organizing settings.gradle, and structuring large multi-module projects. ### Source excerpt Wrapping up this series on modularization I'd like to share some of the things we've learned at Philips Hue while going through this process the past year. ## Modularization - How to approach DevFeed: [Modularization - How to approach]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2019-04-24T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [modules](), [Library](), [legacy](), [Code]() Tags: [android-library](), [architecture](), [blogs](), [code](), [how-to](), [legacy](), [library](), [migrate](), [modularization](), [modules](), [software-engineering]() ### AI overview This tutorial explains two strategies for gradually modularizing an existing Android app: converting the old app into a library and pulling code up, or keeping the old app in place and pushing modules down. It describes the trade-offs and migration challenges of each approach, including legacy dependencies and upfront changes. ### Source excerpt Now that we have a clear idea of how a modularized app could look like how can this be applied to an existing app? Part four will dive deeper into how existing apps can be sliced and how you can gradually migrate to a fully modularized architecture. ## Modularization - Real-life example DevFeed: [Modularization - Real-life example]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2019-04-02T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [modules](), [navigation](), [App](), [test](), [Code]() Tags: [app](), [architecture](), [blogs](), [code](), [how-to](), [modularization](), [modules](), [navigation](), [sample](), [software-engineering](), [test]() ### AI overview This tutorial presents a practical example of a multi-module application architecture. It examines the resulting application structure, navigation graphs, staged rollouts, testing, and a production application using the architecture. ### Source excerpt With a clear view on how multi-module apps should be architected, let's dive into a real-life practical example. We'll discover how the architecture results in a clear application structure, how navigation is handled, how to use staged rollouts, how to test everything and even look at a production app that is using this architecture. ## Modularized Architecture for Android Apps DevFeed: [Modularized Architecture for Android Apps]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2019-03-18T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [modules](), [App](), [Android](), [business logic](), [ui](), [screen]() Tags: [android](), [app](), [architecture](), [blogs](), [business-logic](), [modularization](), [modules](), [navigation](), [screen](), [software-engineering](), [ui]() ### AI overview This tutorial presents a modularized architecture for Android apps. It describes splitting apps into independent feature modules connected through a simple startActivityForResult contract, with shared business logic and UI components organized into library modules. ### Source excerpt Now that we've established that modularization is a really good thing to strive for, how should a modularized app look like? How are the different modules connected? ## Modularization - Why you should care DevFeed: [Modularization - Why you should care]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2019-03-06T00:00:00Z Content type: article Language: en Sources: [Jeroen Mols]() Topics: [modules](), [build performance](), [Gradle](), [Development](), [Deployment]() Tags: [app-size](), [architecture](), [blogs](), [deployment](), [development](), [gradle](), [incremental](), [modularization](), [software-engineering]() ### AI overview This first post in a series explains why app modularization can be useful. It covers potential benefits including faster builds through Gradle caching and parallelism, on-demand delivery, simpler development, module reuse, experimentation, scaling teams, refactoring, and test automation. ### Source excerpt Modularizing your app seems to be all the hype these days. But why should you actually care? What are the benefits for you and your team? ## Lazy Angular Modules DevFeed: [Lazy Angular Modules]() Original publisher: [Read original article]() Published: 2014-07-20T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Angular](), [modules](), [Single-page application (SPA)](), [JavaScript](), [mvc]() Tags: [angular](), [guide](), [javascript](), [lazy-loading](), [modularization](), [modules](), [mvc]() ### AI overview This article examines lazy loading approaches for Angular modules and argues for organizing Angular applications by feature rather than by MVC folders. It discusses startup performance, modularization, maintainability, and examples from the Angular community. ### Source excerpt Lorem ipsum dolor sit amet