Win a copy of High Performance Python for Data Analytics this week in the Python forum!

Laurentiu Spilca

Author
+ Follow
since Oct 02, 2020
Laurentiu likes ...
Spring Java
Cows and Likes
Cows
Total received
5
In last 30 days
0
Total given
0
Likes
Total received
13
Received in last 30 days
0
Total given
12
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Laurentiu Spilca

Hey Nathan. In the repository create a method that finds the records by your condition (E.g name contains :param). You can provide the search term then in your controller by a request parameter or a path variable.
You use that value further up to the repo. Cheers!
2 months ago
Hi Mike. Thanks for the question. I will cover the basics in Spring Quickly in 30 - 50 pages. Of course, Spring Security is a complex topic. One complex enough I've written a book of 560 pages on it. If you already know the basics for Spring you can go directly with learning Spring Security by reading Spring Security in Action. If you don't yet know the basics of Spring, then I recommend you first read Spring Quickly and then read Spring Security in Action. I also share tons of knowledge on my youtube channel: youtube.com/c/laurentiuspilca  There you'll also find a nice playlist on Spring Security fundamentals Cheers!
2 months ago
Hm. That would be difficult. Practically you can create war files with Spring and run them in an application server. However, in software development what you practically do is not necessarily what you should do. Now, the fact that Spring is the management's choice is good. To run your Spring apps in an application server is not what I would recommend. What I would recommend you is decouple parts of your app step by step and run them individually. Use Spring Boot which comes with preconfigured servlet container and convention over configuration. Try to progressively get rid of the application server and aim to a service oriented architecture where each app is independent. In the future this will give you a lot of opportunities, from deployment to work management. Of course, I don't expect it to be an easy job. But it is possible. I've seen it done more than once
2 months ago
Excellent advice, I'll check that too
2 months ago
I John, I hope so. This is the idea of the book. The path should be appropriate for a very beginner. Starts with simple examples and explains them with visuals and code examples as well. Every example is also provided as a project you can import and run yourself.
In the end you should be able to understand but also use the basics of Spring in production-ready apps.
2 months ago
A difficult question to answer in a comment post, Dragos. Thanks for such awesome questions. I actually have a full course lecture in my software architecture course to discuss this topic. Mainly to answer you, it depends a lot on:

- the data model you have
- how much do you care about consistency
- how much do you care about availability
- how much do you care about performance

Then you might decide to use SQL or NoSQL, and mind that NoSQL is not only one implementation. When you decide for NoSQL you have several options. For example you might decide to use MongoDB because your data is modeled as documents, or you might prefer Neo4J because a graph approach fits better to the structure of your data
2 months ago
Correct me if I'm wrong. Isn't that an application server? In this case, we jumped into another subject that goes away from using Spring MVC for that. In that case, you'd probably use CDI directly and then yes, you really on what the AS provides you for JSON deserialization. If you write a Spring app, then you don't need an application server but only a servlet container (which is more light). In this case, you really on what you configure with Spring.
2 months ago
Hi Germán and thanks for the question. The idea of quickly is not about the time in which you can read the book. As a software developer, I learned that the estimations should never be done in time but in complexity. For some readers reading Spring Quickly might take one week while for others it might take 6 months. It really depends on the reader. Now, the idea of "quickly" in Spring Quickly and what I guarantee you is that you will learn for the beginners step by step only what you need to get into working with production-ready apps. So it is the quickest path to achieve this goal starting from zero.
2 months ago
Hi Charles. Thanks for the question. I happen to have used Java/Jakarta EE and Spring as well. There are many similarities but also many differences between these two. I don't think we could cover these in a discussion thread It's rather more of a topic of a separate book.
2 months ago
Hi Charles. I will discuss JDBC with JdbcTemplate and JPA with Spring Data. I also want to cover using NoSQL with MongoDB as an implementation and Spring Data in the book.
As from my own perspective, I do use all in real-world examples. As a consultant, I worked with many different apps that used various technologies.
2 months ago
Hi Nandakumar. Thanks for your question. I'm not sure what you're doing there, so can't really answer your question. Normally you can do integration tests with embedded mongo, but you might have some config problems in your code.
2 months ago
Hi Charles. For the examples in the book I use IntelliJ. However, any of these examples are just Maven projects which you can use with any IDE: Eclipse, STS, Netbeans. You choose your axe
2 months ago
Hi Charles. Thanks for the question. From my point of view one books is never enough no matter for what certification. I however think starting with Spring Quickly is a good point. I then also recommend you Spring in Action and Spring Security in Action. You should also read Spring Boot up and running by Mark Heckler.
But after all, you will find very useful to use some mock exams. Also on my YT channel you'll find some nice videos which are of course free youtube.com/c/laurentiuspilca
2 months ago
Hi Joey. Thanks for your question. A difficult question I can say. I'll try to put some points I learned from my experience that you need to take into consideration for choosing a framework.

1. Does the framework have a big community? Make sure you choose a framework with a big and active community to get easier over problems you may encounter. You need to make sure you have who to ask questions at some point.
2. Is the framework still developed or only maintained? You need to make sure you choose a framework that is both maintained and still developed. Our domain changes quickly and you want to make sure next year you'll be able to use new inventions
3. What does your team know? You need to take into consideration of course what the members of your team already know. Say you have two frameworks A and B. These two frameworks both have a big community and are developed and maintained. If most members of your team know how to use B, then of course in your project best will be to choose B and not A.
4. How easy is to find developers who know to use that framework? Is the framework still new? Sometimes we like to use new technologies but this comes with a risk. If in the future, it won't be that hot anymore, you'll end up with increased costs and difficulty of finding new devs for the team.

I honestly like the discussion on this aspect. There're probably more points but I've tried the most relevant that come now to my mind

Cheers!
2 months ago
Hi Charles. Thanks for the question. I can't say how much will take a reader to read the book in hours. Also as a developer, I dislike estimations in hours and I prefer to discuss complexity. The "quickly" in Spring Quickly is not about time needed to learn which is relative of course to the reader. But what I promise is that it the fastest path one should take to learn Spring from zero. It delivers you with nice examples of what should you need to get into writing production-ready apps with Spring as fast as possible.
2 months ago