Understanding Sprint boot Framework in nutshell

Spring Boot enables building production-ready applications quickly and provides non-functional features:
  • Embedded servers which are easy to deploy with the containers 
  • It helps in monitoring the multiples components 
  • It helps in configuring the components externally 
Disadvantages:

 Automating the Components:  It becomes difficult to automate everything because there are a number of smaller components instead of a monolith, i.e. Builds, Deployment, Monitoring, etc.

 Perceptibility: There are number of small components to deploy and maintain which sometimes becomes difficult to monitor and identify problems. It requires great perceptibility around all the components. 

Configuration Management: There is a great need to maintain the configurations for the components across the various environments. 

Debugging: It becomes difficult to probe each and every service for an error. Centralized Logging and Dashboards are essential to make it easy to debug problems. 

Consistency: You cannot have a wide range of tools solving the same problem. While it is important to foster innovation, it is also important to have some decentralized governance around the languages, platforms, technology and tools used for implementing/deploying/monitoring microservices.

Steps to configure the Sprint boot in your system:

  1. Install STS 3.x.
    Once the tool is installed, click on File -> New -> Other. A dialog box opens up. In that, select Spring Boot Starter Project under the Spring Boot option and click Next.
    Here, make sure you select Maven as Type and click Next. Refer to the snapshot below

2. In the next dialog box that shows up, select the dependencies that you want to add to your Spring Boot Eclipse Project and click Finish. Refer the snapshot below


3. Once created you can visualize below Screens


4. Running the application



5. Even though this application acts ready as a stand-alone application, we will still add a configuration file to it. This will help us handle the HTTP requests. Refer to the snapshot below.





Now, run the application as a Spring Boot App. You observe that the application has started and produces the following output on the console.

This application runs on 8080. So, if we pass /hello request to the following port number, then it produces the message returned from the requested method in the configuration file. Refer to the snapshot below





Thats it!!



Comments

Post a Comment

Popular posts from this blog

Microservice Pattern: SAGA

Image
  Context You are developing a server-side enterprise application. It must support a variety of different clients including desktop browsers, mobile browsers and native mobile applications. The application might also expose an API for 3rd parties to consume. It might also integrate with other applications via either web services or a message broker. The application handles requests (HTTP requests and messages) by executing business logic; accessing a database; exchanging messages with other systems; and returning a HTML/JSON/XML response. There are logical components corresponding to different functional areas of the application. Problem What’s the application’s deployment architecture? Forces There is a team of developers working on the application New team members must quickly become productive The application must be easy to understand and modify You want to practice continuous deployment of the application You must run multiple instances of the application on multiple machines ...
Read more

Microservice Pattern: Database per service Context

Image
Let’s imagine you are developing an online store application using the   Microservice architecture pattern . Most services need to persist data in some kind of database. For example, the   Order Service   stores information about orders and the   Customer Service   stores information about customers. Problem What’s the database architecture in a microservices application? Forces Services must be loosely coupled so that they can be developed, deployed and scaled independently Some business transactions must enforce invariants that span multiple services. For example, the  Place Order  use case must verify that a new Order will not exceed the customer’s credit limit. Other business transactions, must update data owned by multiple services. Some business transactions need to query data that is owned by multiple services. For example, the  View Available Credit  use must query the Customer to find the  creditLimit  and Orders to calcula...
Read more

SQL vs NoSQL | Difference between SQL & NoSQL | SQL Vs NoSQL Tutorial | SQL, NoSQL system design

  SQL  1. Structure          Table,row,column          PreDetermined Schema                    Create table with all the defined datatypes and size.                    Then you can use the table          Relations               1:1,1:M,M:M 2. Nature            Centralized data-all tables in the same database server 3. Scalability          Vertical                     Increase the RAM,Storage         Horizontal -> NOT good for horizontal scaling                    Sharding                      ...
Read more