Simplified JAVA Concept

Transaction Management : Important aspect of transaction management is defining the right transaction boundary for e.g when should a transaction start,when should it end,when data should be committed in DB and when it should be rolled back (in the case of exception). Spring provides the facility of AOP based transaction management in which transactions can be associated to the business logic as a concern. Two types of transaction management are supported by the spring.    Declarative transaction management   Programmatic transaction management Programmatic transaction management  : This means that you have to manage the transaction with the help of programming. That gives you extreme flexibility, but it is difficult to maintain.  Declarative transaction management : This means you separate transaction management from the business code. You only use annotations or XML based configuration to manage the transactions. Choosing between  Programmatic  and 

S pring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can “just run”. We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration. You can use Spring Boot to create Java applications that can be started using  java -jar  or more traditional war deployments. We also provide a command line tool that runs “spring scripts”.  Primary goals are: Provide a radically faster and widely accessible getting started experience for all Spring development. Be opinionated out of the box, but get out of the way quickly as requirements start to diverge from the defaults. Provide a range of non-functional features that are common to large classes of projects (e.g. embedded servers, security, metrics, health checks, externalized configuration). Absolutely no code generation and no requirement for XML configuratio n