• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
  • Bear Bibeault
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Piet Souris
  • salvin francis
  • Stephan van Hulst
Bartenders:
  • Frits Walraven
  • Carey Brown
  • Jj Roberts

does Spring Quickly help someone to understand better Spring Boot and gives examples about it?

 
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I used Spring a lot in my work projects but I am yet to familiarize and understand better how to use Spring Boot properly to create a personal project faster from the ground up; does Spring Quickly help someone to understand better Spring Boot and gives examples about it?
 
Author
Posts: 24
5
Spring Java
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Dragos. Even if Spring Quickly is not a book designed expecially for Spring Boot, you will find nice examples with Spring Boot starting with chapter 7. Hopefully they're good enough to make even a beginner understand Spring Boot projects and the very basics of them At least I try my best!
 
Dragos Pavel
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you, I observed your other reply for the persistence post and I have one more question please: so in what situations or use cases do you recommend to use NoSQL with MongoDB as an implementation and Spring Data?  (over the other more traditional persistence options let's say)
 
Laurentiu Spilca
Author
Posts: 24
5
Spring Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
 
Make yourself as serene as a flower, as a tree. And on wednesdays, as serene as this tiny ad:
the value of filler advertising in 2020
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic