book

Spring Start Here

by Laurentiu Spilca

October 2021

Beginner

416 pages

11h 25m

English

Manning Publications

Read now

Unlock full access

forewordprefaceacknowledgmentsabout this bookWho should read this bookHow this book is organized: A roadmapAbout the codeliveBook discussion forumabout the authorabout the cover illustration
1.1 Why should we use frameworks?1.2 The Spring ecosystem1.2.1 Discovering Spring Core: The foundation of Spring1.2.2 Using Spring Data Access feature to implement the app’s persistence1.2.3 The Spring MVC capabilities for developing web apps1.2.4 The Spring testing feature1.2.5 Projects from the Spring ecosystem1.3 Spring in real-world scenarios1.3.1 Using Spring in the development of a backend app1.3.2 Using Spring in a automation test app1.3.3 Using Spring for the development of a desktop app1.3.4 Using Spring in mobile apps1.4 When not to use frameworks1.4.1 You need to have a small footprint1.4.2 Security needs dictate custom code1.4.3 Abundant existing customizations make a framework impractical1.4.4 You won’t benefit from switching to a framework1.5 What will you learn in this bookSummary
2.1 Creating a Maven project2.2 Adding new beans to the Spring context2.2.1 Using the @Bean annotation to add beans into the Spring context2.2.2 Using stereotype annotations to add beans to the Spring context2.2.3 Programmatically adding beans to the Spring contextSummary
3.1 Implementing relationships among beans defined in the configuration file3.1.1 Wiring the beans using a direct method call between the @Bean methods3.1.2 Wiring the beans using the @Bean annotated method’s parameters3.2 Using the @Autowired annotation to inject beans3.2.1 Using @Autowired to inject the values through the class fields3.2.2 Using @Autowired to inject the values through the constructor3.2.3 Using dependency injection through the setter3.3 Dealing with circular dependencies3.4 Choosing from multiple beans in the Spring contextSummary
4.1 Using interfaces to define contracts4.1.1 Using interfaces for decoupling implementations4.1.2 The requirement of the scenario4.1.3 Implementing the requirement without using a framework4.2 Using dependency injection with abstractions4.2.1 Deciding which objects should be part of the Spring context4.2.2 Choosing what to auto-wire from multiple implementations of an abstraction4.3 Focusing on object responsibilities with stereotype annotationsSummary
5.1 Using the singleton bean scope5.1.1 How singleton beans work5.1.2 Singleton beans in real-world scenarios5.1.3 Using eager and lazy instantiation5.2 Using the prototype bean scope5.2.1 How prototype beans work5.2.2 Prototype beans in real-world scenariosSummary

6.1 How aspects work in Spring6.2 Implementing aspects with Spring AOP6.2.1 Implementing a simple aspect6.2.2 Altering the intercepted method’s parameters and the returned value6.2.3 Intercepting annotated methods6.2.4 Other advice annotations you can use6.3 The aspect execution chainSummary
7.1 What is a web app?7.1.1 A general overview of a web app7.1.2 Different fashions of implementing a web app with Spring7.1.3 Using a servlet container in web app development7.2 The magic of Spring Boot7.2.1 Using a project initialization service to create a Spring Boot project7.2.2 Using dependency starters to simplify the dependency management7.2.3 Using autoconfiguration by convention based on dependencies7.3 Implementing a web app with Spring MVCSummary
8.1 Implementing web apps with a dynamic view8.1.1 Getting data on the HTTP request8.1.2 Using request parameters to send data from client to server8.1.3 Using path variables to send data from client to server8.2 Using the GET and POST HTTP methodsSummary
9.1 Using the request scope in a Spring web app9.2 Using the session scope in a Spring web app9.3 Using the application scope in a Spring web appSummary
10.1 Using REST services to exchange data between apps10.2 Implementing a REST endpoint10.3 Managing the HTTP response10.3.1 Sending objects as a response body10.3.2 Setting the response status and headers10.3.3 Managing exceptions at the endpoint level10.4 Using a request body to get data from the clientSummary
11.1 Calling REST endpoints using Spring Cloud OpenFeign11.2 Calling REST endpoints using RestTemplate11.3 Calling REST endpoints using WebClientSummary
12.1 What a data source is12.2 Using JdbcTemplate to work with persisted data12.3 Customizing the configuration of the data source12.3.1 Defining the data source in the application properties file12.3.2 Using a custom DataSource beanSummary
13.1 Transactions13.2 How transactions work in Spring13.3 Using transactions in Spring appsSummary
14.1 What Spring Data is14.2 How Spring Data works14.3 Using Spring Data JDBCSummary
15.1 Writing correctly implemented tests15.2 Implementing tests in Spring apps15.2.1 Implementing unit tests15.2.2 Implementing integration testsSummary
A.1 The monolithic approachA.2 Using a service-oriented architectureA.2.1 Complexity caused by communication among servicesA.2.2 Complexity added to the security of the systemA.2.3 Complexity added for the data persistenceA.2.4 Complexity added in the deployment of the systemA.3 From microservices to serverlessA.4 Further reading
C.1 What is HTTP?C.2 The HTTP request as a language between client and serverC.3 The HTTP response: The way the server respondsC.4 The HTTP session
Step 1: Install a DBMS on your local systemStep 2: Install a client application for your DBMSStep 3: Connecting to the local DBMSStep 4: Add a new database

Content preview from Spring Start Here

13 Using transactions in Spring apps

This chapter covers

What a transaction is
How Spring manages transactions
Using transactions in a Spring app

One of the most important things we take into consideration when managing data is to keep accurate data. We don’t want specific execution scenarios to end up with wrong or inconsistent data. Let me give you an example. Suppose you implement an application used to share money—an electronic wallet. In this application, a user has accounts where they store their money. You implement a functionality to allow a user to transfer money from one account to another. Considering a simplistic implementation for our example, this implies two steps (figure 13.1):