Architecting Web Applications with Spring
by Kevin Jones
Building applications is hard, but a good architecture should help to make it easier. This course looks at the idea of building your application with isolated components while making use of Spring Data and Spring Security.
What you'll learn
How do you go about designing and building a complex web application while keeping the code maintainable and testable? This course, Architecting Web Applications with Spring, examines how to build your application from 'components,' where each component is a feature of your application. That feature is isolated as much as possible from the rest of the application and will contain all the code it needs. You'll be shown how to unit test these features by injecting dependencies to make them mockable, and how to use Mockito as the mocking framework that will allow features to be unit-tested. You'll learn how to integrate test components with support from Spring, as well as database integration, using Flyway to manage database migrations, and using Spring Data to access that data. Last, but not least, you'll discover how to use Spring Security to provide a layer of authentication and authorization to your application. By the end of this course, you'll be able to fully architect web apps with multiple components in Spring using code that you can easily test and maintain.
About the author
A long time ago in a university far, far away Kevin fell in love with programming. Initially on the university's DEC20 computer doing BASIC and Pascal and a little bit of Fortran. His first job had him writing batch PL/1 on an IBM mainframe where he also discovered the arcane delights of JCL. He soon realized the multiuser systems were not for him after discovering the delights of dBase IV on IBM PCs. From here it was all downhill as he became addicted to C and the Windows API. Just missing out ... moreon coding for Windows 1, he did code for the other 16 bit versions of Windows, 2 and 3, including the various network-ready versions. He still remembers the awkwardness of having to carry an IBM Token Ring MAU with him wherever he went.
After trying to pretend that Windows and C were really object oriented he decided that it would be better to learn C++. It was around this point that he realized that as well as writing code for a living he could be paid for telling people how to write code for a living. He taught Windows, MFC and C++ for a UK training company before his spirit was broken on the back of the OLE support in MFC when he finally stepped away from the nightmare of unmanaged code to the nirvana of the managed runtime called Java.
It was at this time that he spoke at several JavaOne conferences usually on the subject of Servlets, JavaServer Pages and tag libraries. After buying the Sun employees copious amounts of Apple Martini Kevin was invited onto the expert groups for the Servlet and JSP specifications.
Oh, how he laughed when .Net appeared and the same arguments raged about non-deterministic destruction and garbage collection that were now so old hat in the Java world. He finally got his hands dirty in C# and .Net about eight years ago, again working in the web tier and hating every minute of the using the monstrosity that was and is ASP.Net Web Forms. It wasn't until MVC appeared that he finally felt he had come home to Microsoft.
Now of course MVC is so last year and Kevin is focusing more and more on rich clients using JavaScript and tools such as Knockout and AngularJS. He believes that JavaScript is the best thing since, well, JavaScript.
He still retains his passion for developing and teaching; spending about a quarter of the year doing the latter and most of the time doing the former.
When not stuck in front of a computer you can find him: with his nose in a book, a good one preferably, but almost any book would do; watching a film; walking; running; or annoying his wife by watching sports on television.
