Bootstrap vs Spring Boot: What are the differences?
What is Bootstrap? Simple and flexible HTML, CSS, and JS for popular UI components and interactions. Bootstrap is the most popular HTML, CSS, and JS framework for developing responsive, mobile first projects on the web.
What is Spring Boot? Create Spring-powered, production-grade applications and services with absolute minimum fuss. Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration.
Bootstrap belongs to "Front-End Frameworks" category of the tech stack, while Spring Boot can be primarily classified under "Frameworks (Full Stack)".
"Responsiveness", "UI components" and "Consistent" are the key factors why developers consider Bootstrap; whereas "Powerful and handy", "Easy setup" and "Java" are the primary reasons why Spring Boot is favored.
Bootstrap and Spring Boot are both open source tools. It seems that Bootstrap with 134K GitHub stars and 66K forks on GitHub has more adoption than Spring Boot with 39.8K GitHub stars and 25.8K GitHub forks.
Spotify, Twitter, and Lyft are some of the popular companies that use Bootstrap, whereas Spring Boot is used by MIT, Intuit, and OpenGov. Bootstrap has a broader approval, being mentioned in 7046 company stacks & 1115 developers stacks; compared to Spring Boot, which is listed in 333 company stacks and 615 developer stacks.
Starting a new company in 2020, with a whole new stack, is a really interesting opportunity for me to look back over the last 20 years of my career with web software and make the right decision for my company.
And, I went with the most radical decision– which is to ignore "sexy" / "hype" technologies almost entirely, and go back to a stack that I first used over 15 years ago.
For my purposes, we are building a video streaming platform, where I wanted rapid customer-facing feature development, high testability, simple scaling, and ease of hiring great, experienced talent. To be clear, our web platform is NOT responsible for handling the actual bits and bytes of the video itself, that's an entirely different stack. It simply needs to manage the business rules and the customers experience of the video content.
I reviewed a lot of different technologies, but none of them seemed to fit the bill as well as Rails did! The hype train had long left the station with Rails, and the community is a little more sparse than it was previously. And, to be honest, Ruby was the language that was easiest for developers, but I find that most languages out there have adopted many of it's innovations for ease of use – or at least corrected their own.
Even with all of that, Rails still seems like the best framework for developing web applications that are no more complex than they need to be. And that's key to me, because it's very easy to go use React and Redux and GraphQL and a whole host of AWS Lamba's to power my blog... but you simply don't actually NEED that.
There are two choices I made in our stack that were new for me personally, and very different than what I would have chosen even 5 years ago.
1) Postgres - I decided to switch from MySql to Postgres for this project. I wanted to use UUID's instead of numeric primary keys, and knew I'd have a couple places where better JSON/object support would be key. Mysql remains far more popular, but almost every developer I respect has switched and preferred Postgres with a strong passion. It's not "sexy" but it's considered "better".
I do prefer to write things from scratch however when it came to wanting to jump-start the frontend, I found that it was taking me a lot longer hence why needing to use something very fast.
Bootstrap was the boom when it came out, I didn't like it, to be honest, set in its way and a pain to over-ride and in addition, you can tell from a distance if you're using boostrap and as everything looks the same.
I came across Tailwind CSS as I wanted more dynamic features, you could say, I've been now doing it for a few days and I love it a lot. I've been practising with the full stack part installed but I an't we wait until I do a new project, and I'll e able to select exactly what I want. Much faster.
I find the Tailwind provides a lot for flexibility in how we approach design for Mojinxo, while still giving me the benefits of a defined framework and centralised configuration. With tailwind we can create something that is very much Mojinxo and not just a carbon copy of every other site using Tailwind, which is what I find tends to be the case with Bootstrap and Bulma.
There is a tradeoff in familairity for users, especially with Bootstrap where users just 'know' how a site will work based on the card display, the common navigation look and feel and the slide-out burger menus.
The icing on the cake is definitely size. Tailwind is just so small, effective and easy to pick up.
Sign up to add or upvote prosMake informed product decisions
Sign up to add or upvote consMake informed product decisions
What is Bootstrap?
What is Spring Boot?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions