The bigger a monolithic application, the larger the dependency set. Adding or changing dependencies becomes a tricky task. Similarly, the complexity is in the number of beans and their dependencies in components container. You learn how to split a monolithic SpringFramework ApplicationContext into a set of sub-contexts, how to isolate sub-context internal components, clear their APIs and avoid non-trivial dependencies. Each sub-context can have its own classpath, which tackles the dependency hell problem. After being divided, a monolithic system becomes easier to split into a set of micro-services or processes. From the talk, attendees will learn several practical tips and tricks on how to split component containers into smaller ones to reduce the complexity.
comments powered by Disqus