Hello Steemit User,

![jbbjb.png](https://steemitimages.com/DQmaySGoCPhm7KCSFpEwwebHz2cahEAoU535VrCar1mnKrA/jbbjb.png)

The Spring Framework is a Java platform that provides comprehensive infrastructure support for developing Java applications. Spring handles the infrastructure so you can focus on your application.

Spring enables you to build applications from "plain old Java objects" (POJOs) and to apply enterprise services non-invasively to POJOs. This capability applies to the Java SE programming model and to full and partial Java EE.

Examples of how you, as an application developer, can benefit from the Spring platform:

• Make a Java method execute in a database transaction without having to deal with transaction APIs.
• Make a local Java method a remote procedure without having to deal with remote APIs.
• Make a local Java method a management operation without having to deal with JMX APIs.
• Make a local Java method a message handler without having to deal with JMS APIs.

![fd.jpg](https://steemitimages.com/DQmYKz4CrtRCFZjdNL2N8Bwh5oViGeNYGVdK46SxVK4kamk/fd.jpg)


Modules :

The Spring Framework consists of features organized into about 20 modules. These modules are grouped into Core Container, Data Access/Integration, Web, AOP (Aspect Oriented Programming), Instrumentation, Messaging, and Test, as shown in the following diagram

![njnj.jpg](https://steemitimages.com/DQmfXgZFtMRwPKnXXLKsCHcriaM4UXHgRcNPS9KJebASENE/njnj.jpg)

 Dependency Injection and Inversion of Control


A Java application — a loose term that runs the gamut from constrained, embedded applications to n-tier, server-side enterprise applications — typically consists of objects that collaborate to form the application proper. Thus the objects in an application have dependencies on each other.
Although the Java platform provides a wealth of application development functionality, it lacks the means to organize the basic building blocks into a coherent whole, leaving that task to architects and developers. Although you can use design patterns such as Factory, Abstract Factory, Builder, Decorator, and Service Locator to compose the various classes and object instances that make up an application, these patterns are simply that: best practices given a name, with a description of what the pattern does, where to apply it, the problems it addresses, and so forth. Patterns are formalized best practices that you must implement yourself in your application.
The Spring Framework Inversion of Control (IoC) component addresses this concern by providing a formalized means of composing disparate components into a fully working application ready for use. The Spring Framework codifies formalized design patterns as first-class objects that you can integrate into your own application(s). Numerous organizations and institutions use the Spring Framework in this manner to engineer robust, maintainable applications.

tools

![scs.gif](https://steemitimages.com/DQmY5t8nMRUxr1LPZMFfghfkHSh5thbEy3Dn4X5ZKJnpJH6/scs.gif)

by @ravik2492

![ravik2492 level.png](https://steemitimages.com/DQmZGH4NbaYDEEA1KutTx73KBXTiBaqKYt5LzKM4KBkifZ5/ravik2492%20level.png)