Skip to main content

Spring Boot or Plain Spring?

In Simple Terminology, Spring Boot = Spring Framework + Embedded HTTP Servers – XML / annotations.
Here we don’t need to write any XML Configuration. (the reason it has been subtracted in the above explanation.)

So firstly, I am going to talk about some benefits of using spring boot over Plain Spring.


1. It is easier to develop Spring Based applications with Java or Groovy.
2. It reduces lots of development time and increases productivity.
3. It avoids writing lots of boilerplate Code.
4. It is easier to integrate Spring Boot Application with its Spring Ecosystem.
5. It provides Embedded HTTP servers.
6. It provides a lot of options to work with embedded and in-memory Databases.

The costs that would be uncured to switch to spring boot in OpenMRS, are –


·         Since we do not have to write the XML configuration in Spring Boot, there would be no value of the XML and a few annotations written using Spring.
·         The spring boot will reduce the length of the code.
·         It will shorten the time of any developing application.

If your mind is tingling on reading more stuff about Spring, you can refer to one of my blogs that I have written, related to it: https://mygci19blog.blogspot.com/2019/12/spring-controllers.html
Other than just that, you can also refer to the following links below, which also includes interactive and easy YouTube videos related to spring Boot-
https://spring.io/guides/gs/spring-boot/

https://youtu.be/Ch163VfHtvA

https://youtu.be/Ke7Tr4RgRTs



Sources: https://stackify.com/spring-boot-level-up/

Comments

Popular posts from this blog

Google Code-In 2020 Wrap Up

"You do not need to be a programmer, you don’t have to know how to code at all!" is where it all started.    Google Code-in  ( GCI ) As its name suggests, is an annual programming competition hosted by Google that allows students to complete tasks specified by various open-source organizations. the organization which I chose was - OpenMRS.  What is OpenMRS?  OpenMRS is both a software and a community. It serves as a medical record system (EMR) which is designed for developing countries. OpenMRS follows a principle that information should be stored in a way that makes it easy to summarize and analyze. If you are interested in learning more about the OpenMRS community, you may go  here  and know more about it. If one would ask me to define OpenMRS in one line, it would be "we write code for humans first and then computers." as their main motto is to save lives.  My interactions in OpenMRS My interaction with OpenMRS ...

Cracking the enigma for Microfrontends!

“Software architecture should never be an end goal, but a means to an end” I write this blog from the perspective of an inexperienced learner and hence the language adopted here would be in the layman’s terms making it easier to understand. We begin with the most obvious and important question that one should know the answer to before studying the applications of Micro frontend, i.e.  what is meant by the term Micro frontend.  Micro frontend is basically a term for Self-contained Systems or Frontend Integration for Vertical Systems which simply refer to an idea that considers a website or a web app as a composition of features which are owned by independent teams. Each team has a distinct area of business or mission it cares about and specializes in. A team is cross-functional and develops its features end-to-end, from database to user interface. Now we consider the secondary question:  How would using micro frontend development architecture over the t...