Win a copy of 97 Things Every Java Programmer Should Know this week in the Java in General forum!
  • 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 ...
  • Campbell Ritchie
  • Paul Clapham
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
  • Ron McLeod
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Frits Walraven
  • Tim Holloway
  • Carey Brown
  • Piet Souris
  • salvin francis
  • fred rosenberger

Questions about Spring Boot

Ranch Hand
Posts: 225
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm learning about Spring Boot on my own. I'm a developer, but I don't use it at work. I'm developing some Spring Boot applications at home and I'm running them on my local machine.

In the workplace, where are Spring Boot applications developed and how are they deployed?

What are some examples of challenging Spring Boot applications that I can develop on my own?

If I apply for a job that requires Spring Boot experience, do I have to say that my experience with Spring Boot comes from outside of work?
Saloon Keeper
Posts: 22122
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Spring Boot is a handy way to create pre-packaged web applications with a built-in server. A good example of this was that once upon a time VMWare had a desktop management console app that was written as a webapp. They had to package up their very own private copy of Tomcat along with their management app code and make it all easy enough to install and operate that the average drooling VM operator wouldn't have to even know that they were dealing with Java. Alas for them, Spring Boot was still several years in the future, but they did a decent job of it, regardless.

These days many times it's useful to have a single-app webserver. They lend themselves well to containerization, for example. But of course, they're not the solution for everything. Sometimes you may find it better to host multiple applications in a single appserver, old-style. Sometimes you want something whose insides are more accessible for advanced custom configuration.

Where you get your experience from is less important than what you can demonstrate having done with it. In that sense, publishing open-source projects is actually better, since as a rule, it would be a problem for me to display applications from a former employer to a potential new employer.
I am going to test your electrical conductivity with this tiny ad:
Devious Experiments for a Truly Passive Greenhouse!
    Bookmark Topic Watch Topic
  • New Topic