Amadeus/guice
1
0
Fork 0
mirror of https://github.com/google/guice.git synced 2024-04-21 12:32:36 +00:00
Code Issues Releases Wiki Activity
Page: OrganizeModulesByFeature
Pages
3rdPartyModules AOP AppsThatUseGuice AssistedInject Avoid Injecting Closable Resources AvoidCallingProvideMethodsAndInjectConstructors AvoidConditionalLogicInModules AvoidStaticState BeCarefulAboutIoInProviders BestPractices BindingAnnotations BindingResolution Bindings Bootstrap BoundFields BuiltInBindings ClassLoading CustomInjections CustomScopes CyclicDependencies DocumentPublicBindings DontReuseAnnotations Errors ExtendingGuice ExtensionSPI ExternalDocumentation FrequentlyAskedQuestions GettingStarted GoogleAppEngine Grapher Guice10 Guice20 Guice30 Guice40 Guice41 Guice42 Guice421 Guice422 Guice423 Guice500 Guice501 Guice510 Guice600 Guice700 GuiceDiscussions GuiceInKotlin GuicePersist GuicePersistMultiModules Home InjectOnlyDirectDependencies InjectingProviders InjectingTheInjector InjectionPoints Injections InspectingModules InstanceBindings JPA JSR330 JustInTimeBindings KeepConstructorsHidden LinkedBindings MentalModel MinimizeMutability ModulesShouldBeFastAndSideEffectFree Motivation Multibindings OSGi OptionalAOP OrganizeModulesByFeature PreferAtProvides ProviderBindings ProvidesMethods RestrictedBindingSource Scopes ServletExtensionSPI ServletModule ServletRegexKeyMapping Servlets SpringComparison Struts2Integration ThrowingProviders ToConstructorBindings Transactions UntargettedBindings UseNullable
Clone
2
OrganizeModulesByFeature
Copybara-Service edited this page 2021-04-12 13:36:51 -07:00
Table of Contents

Organize modules by feature, not by class type

Group bindings into features. Ideally it should be possible to enable/disable an entire working feature by simply installing or not installing a single module in the injector.

For example, don't just make a FiltersModule that has bindings for all the classes that implement Filter in it, and a GraphsModule that has all the classes that implement Graph, etc. Instead, try to organize modules by feature, for example an AuthenticationModule that authenticates requests made to your server, or a FooBackendModule that lets your server make requests to the Foo backend.

This principle is also known as "organize modules vertically, not horizontally".