If you’ve ever gone through a Spring Boot tutorial and then finally got that job or started working on that side project where you can put your new know-how to use, then you’ve probably experienced the Spring Boot drop-off. It's the stage where you need to know more and do more than Spring Boot is doing for you. You need more revealed. You need to look inside and dig deeper to uncover the tweaks that are being hidden from you. That’s what this course is all about. In particular, this chapter is about those first common curiosities of a new Spring MVC developer. Shonna shares what you need to do to make Spring MVC configuration changes that suit your project’s needs.
- [Instructor] There are many benefits to learning how to use Spring MVC properly. But before I dive straight into how to use Spring MVC, I think it's important to spend some time getting some perspective on why you should use it anyway. I'm from the begin-with-the-why school of thought. So with that in mind, I want to review some reasons why learning Spring MVC is a worthwhile thing to do. When you first start learning the Spring framework, you'll probably begin by going to Spring's website.
Eventually you'll find your way to the Spring guides page and download a project or two. And this is a great place to begin your Spring know-how journey. However, while you're able to have a working application quickly, you really don't know how all that Spring magic works. You will accomplish a lot with very little effort, but you won't be learning as much as you need to. At some point, and that point usually comes pretty quickly, you will need to start customizing a Spring Boot project to meet your needs.
For instance, your application is going to have its own user interface needs, its own security needs, logging needs, and a host of other things that just aren't going to be completely handled for you out of the box. And even if they were handled, they're probably being handled in some partial way that's not fully solving your needs. You need to take that partial solution, pick up from where Spring Boot leaves off, and add your own know-how to your project.
This is when a deeper understanding of Spring MVC is absolutely necessary. There's many shortcuts and convenient choices made for you by a Spring Boot project. You need to understand where and what those shortcuts are so you can redo them to meet your unique needs. And if you want to give yourself an extra challenge, you can learn Spring MVC the way I did and try to create a Spring-based Web project by creating all of your scaffolding, all of your Getting Started component configurations all on your own.
Mind you, I learned this way because my Spring know-how predates the existence of Spring Boot. However, I find it to be very useful that I already know all of the things that Spring Boot is hiding from me. It's also useful to learn it this way if you know you're going to be joining a project that's already in progress, in which case, a deeper knowledge is a requirement. And speaking of joining a project already in progress, having that deep understanding of Spring MVC also means that you're better suited for quickly improving or even troubleshooting existing code written using Spring MVC.
Since code spends most of its lifetime in maintenance mode anyway, then your ability to maintain that code is better when you know more of the ins and outs of the development framework that it uses. When you're able to quickly contribute to an existing project, that makes you more valuable not only to yourself but to the team you're working with. Let's face it. The Spring framework and all of its offshoots are pretty much a de facto choice for many of today's enterprise-scale projects.
Most large organizations, such as Fortune 100 and Fortune 500 companies, they invest tons of monies, six, seven, even eight or more figures, into major software development projects. With that kind of investment, these projects are definitely going to be using enterprise-scale backend frameworks such as Spring, Spring MVC, and all of its related frameworks. The Web runs the world, and the enterprise Web is what runs the software used or sold by a lot of these large organizations.
And that software is probably going to be powered by Spring Web MVC. If you're interested in joining the world of enterprise software development, then you definitely need to have some deep Spring MVC know-how. If you've done any Java development job searching lately, then you may have noticed a trend. That trend is towards being an extremely knowledgeable backend or maybe even a full-stack developer. And somewhere in that stack is going to require Spring MVC know-how or a framework that's very similar to Spring MVC.
The kinds of things you'll learn in this course tend to be mandatory know-how on many of today's enterprise projects. You need to come to those projects with some experience under your belt. Having a project or two in your portfolio to demonstrate your deep understanding is going to be a benefit. Well, that's what this course will give you. Your career as a professional software developer relies heavily on constantly building skills. If you're on an enterprise Java developer track or you want to be on that track, then learning Spring MVC inside and out is a definite stop on your professional development journey.
Even if you have no immediate plans or desires to join a team using Spring MVC, it's safe to say that at some point in your career, this type of knowledge will pay off. And there's no time like the present to get started on what will definitely be a critical part of your self-education roadmap. By now, I hope you're convinced on why taking this course is beneficial to you. So how about we get started on that deep dive into Spring MVC?
- Using Spring MVC for web projects
- Spring MVC controllers
- Creating controllers and views
- Spring MVC models
- Creating the model
- Request mapping
- Spring MVC views
- Custom app configuration