If someone can preferably use an analogy to explain the Spring framework I’d really appreciate it.
It doesn’t have to be advanced, I just want a general understanding of how things used to be, and a layman’s explanation of how Spring makes the way things used to be a lot easier now.
In: Technology
Software frameworks in general, not specific to Spring, basically do the boring housekeeping things for you. Pretty much every application has a bunch of basic things to do (get input, perhaps refer to data, make decisions, send output); so rather than code that by hand in every application, you use a framework so you don’t have to worry about the “guts”. The framework also “forces” you to use a specific coding style, so that everything is consistent across different developers and different parts of the application. If you used a hypothetical perfect framework, all that would be left to be done is just coding the actual business logic (in reality it’s not *quite* that simple).
Spring in particular is designed to simplify developing enterprise-level Java applications.
Latest Answers