Thursday, February 21, 2019

REST API: Java Spring Boot and MongoDB

  • Introduction
  • Step 1: Creating a Database
  • Step 2: Adding a MongoDB Collection and Data
  • Step 3 : Using Spring Initializr to Create a Project
  • Step 4 : Import project into Eclipse
  • Step 5 : Adding Model to Spring Boot Project
  • Step 6 : Adding Repository to Spring Boot Project
  • Step 7 : Adding the MongoDB Connection Info
  • Step 8 : Creating REST Controller
  • Step 9 : Adding the REST Endpoints
  • Step 10 : Creating Service

Introduction

This document walks you through the process of using Spring Boot and MongoDB to build a Rest API that stores data in and retrieves it from MongoDB, a document-based database.
Tools Used in this Tutorial
  1. Java
  2. Spring Boot
  3. Maven
  4. MongoDB
  5. Postman
  6. Eclipse

Step 1: Creating a Database

It is assumed that you already have an accessible instance of MongoDB that you can connect to.
Let us start by creating a test database. I will call mine "rest_pets" using the following command in the MongoDB shell, or through a database manager like Robo 3T 1.1.1.

   use rest_pets;    
This will create a new database in MongoDB that we can use for our tutorial.

Step 2: Adding a MongoDB Collection and Data

In MongoDB, collections are analogous to tables in a relational database — they hold the data that we will be querying using our REST API. I will be creating a sample collection that will hold data about different types of pets. Let's create the collection with the following command:
    db.createCollection("pets"); 

Once the collection is created, we need to add some data! This collection will hold the names, breeds, and species of various pets.
We can add data to the collection with the following command:
 db.pets.insertMany([
  {
    "name" : "Spot",
    "species" : "dog",
    "breed" : "pitbull"
  },
  {
    "name" : "Daisy",
    "species" : "cat",
    "breed" : "calico"
  },
  {
    "name" : "Bella",
    "species" : "dog",
    "breed" : "australian shepard"       
  }    
]); 

Querying the collection with db.pets.find({}); reveals that MongoDB automatically assigns a unique _id field to each document to make it easier to find and edit documents

Step 3 : Using Spring Initializr to Create a Project

Spring offers a tool called the Spring Initializr to help jump-start your Spring Boot project. Access the Initializr at start.spring.io and enter the following information:
  • Group: This is the package name
    • Example: com.esb.demo
  • Artifact: This is the project name
    • Example: SpringBootMongoDB
  • Dependencies: These are the features that will be added to your project (remember, you can always add these later)
    • Our tutorial will use the "Web" and "MongoDB" dependencies

Then click Generate Project to download a .zip file with the basic project structure.

Step 4 : Import project into Eclipse

With the project downloaded from the Spring Initializer, you can now open it in your favorite IDE to begin editing the project. In my case i am using eclipse

Step 5 : Adding Model to Spring Boot Project

 First, we will want to add a pets model, so that Spring will know what kind of data the database will return. We can do this by creating a new folder in src/main/java/[package name]/ called "models". In the new "models" folder, we can create a file called Pets.java. This Java class will hold the basic structure of a document in the "pets" collection, so the class looks as follows:
package com.esb.demo.SpringBootMongoDB.models;
import org.bson.types.ObjectId;
import org.springframework.data.annotation.Id;

public class Pets {
    @Id
    public ObjectId _id;

    public String name;
    public String species;
    public String breed;

    // Constructors
    public Pets() {
    }

    public Pets(ObjectId _id, String name, String species, String breed) {
        this._id = _id;
        this.name = name;
        this.species = species;
        this.breed = breed;
    }

    // ObjectId needs to be converted to string
    public String get_id() {
        return _id.toHexString();
    }

    public void set_id(ObjectId _id) {
        this._id = _id;
    }

    public String getName() {
        return name;
    }

    public void setName(String name) {
        this.name = name;
    }

    public String getSpecies() {
        return species;
    }

    public void setSpecies(String species) {
        this.species = species;
    }

    public String getBreed() {
        return breed;
    }

    public void setBreed(String breed) {
        this.breed = breed;
    }
}

Step 6 : Adding Repository to Spring Boot Project

Now that we have a model that identifies the data structure stored in the database to Spring Boot, we can create the connector between the model and MongoDB. This is done through a Repository interface. We can create this first by making a new folder called "repositories" in src/main/java/[package name]/.
In the new "repositories" folder, we can create a file called PetsRepository.java. The name of this repository is extremely important because it tells MongoDB the collection that it will be querying (in this case, the pets collection). This interface will extend the MongoRepository class, which already contains generic methods like save (for creating/updating documents) and delete (for removing documents), but we will need to specify additional methods ourselves.
Luckily, we do not need to manually implement these queries, we can simply use Spring Boot's repository naming conventions, and the MongoRepository will intelligently construct the queries at runtime. This means that our interface will be extremely simple, as follows:
package com.esb.demo.SpringBootMongoDB.repositories;
import org.bson.types.ObjectId;
import org.springframework.data.mongodb.repository.MongoRepository;
import com.esb.demo.SpringBootMongoDB.models.Pets;

public interface PetsRepository extends MongoRepository<Pets, String> {
    Pets findBy_id(ObjectId _id);
}

Step 7 : Adding the MongoDB Connection Info

To tell Spring the connection information for our MongoDB, we will need to add connection details to the application.properties file, located in the "src/main/resources" folder. Add the following lines to the file, replacing the information in brackets with the information specific to your MongoDB instance:
spring.data.mongodb.host=localhost
spring.data.mongodb.port=27017
spring.data.mongodb.authentication-database=admin
spring.data.mongodb.username=dev
spring.data.mongodb.password=dev
spring.data.mongodb.database=rest_pets
This is all the information that Spring will need to connect to the database.

Step 8 : Creating REST Controller

Spring should now be able to connect to MongoDB, so now we can establish the enpoints that we can contact to interact with the database. This will be done in a Spring Rest Controller, which uses Request Mappings to map requests with functions. We can create a Rest Controller by adding a file called PetsController.java to the src/main/java/[package name]/ folder. The basic file structure will look as follows:
package com.esb.demo.SpringBootMongoDB.controller;

import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RestController;
import com.esb.demo.SpringBootMongoDB.service.PetsService;

@RestController
@RequestMapping(value = "/pets")
public class PetsController {
   @Autowired
    private PetsService petsService;
}

The @RestController annotation tells Spring that this class will requested by URL and will return data to the requester. The @RequestMapping annotation specifies the base URL that the controller will be handling, so any request to the host starting with "/pets" will be directed to this controller. The @Autowired annotation creates an instance of the PetsRepository object that will allow us to access and modify the pets database.

Step 9 : Adding the REST Endpoints

All of the following enpoints will be added directly into the PetsController class.
GET
    @RequestMapping(value = "/all", method = RequestMethod.GET)
    public List<Pets> getAllPets() {
        return petsService.getAllPets();

    }

    @RequestMapping(value = "{id}", method = RequestMethod.GET)
    public Pets getPetById(@PathVariable("id") ObjectId id) {
        return petsService.getPetbyId(id);
    }

The first mapping takes any GET requests to the host with a URL of /pets/all and maps them to the getAllPets() method, which requests all documents from the pets collection.
The second mapping takes and GET requests to the host with a URL of /pets/ followed by an ObjectId and maps them to the getPetById() method, which searches the pets collection for the document with an _id field equal to the ObjectId in the URL.
PUT
    @RequestMapping(value = "{id}", method = RequestMethod.PUT)
    public void modifyPetById(@PathVariable("id") ObjectId id, @RequestBody Pets pets) {
        pets.set_id(id);
        petsService.updatePetById(pets);
    }

This mapping expects a request body (in JSON format) with each of the fields that a Pets object contains (namespecies, and breed). The id in the request URL is the _id of the document to be modified.
POST
    @RequestMapping(value = "/create", method = RequestMethod.POST)
    public Pets createPet(@RequestBody Pets pets) {
        pets.set_id(ObjectId.get());
        return petsService.save(pets);
    }

This mapping expects a request body (in JSON format) with each of the fields that a Pets object contains (namespecies, and breed), and assigns it a new ObjectId. This object is then inserted into the pets collection, and the new Pets object is returned.
DELETE
 @RequestMapping(value = "{id}", method = RequestMethod.DELETE)
 public void deletePet(@PathVariable ObjectId id) {
      petsService.deletePet(id);
 }

Completed Controller
package com.esb.demo.SpringBootMongoDB.controller;

import java.util.List;

import org.bson.types.ObjectId;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.web.bind.annotation.PathVariable;
import org.springframework.web.bind.annotation.RequestBody;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RequestMethod;
import org.springframework.web.bind.annotation.RestController;

import com.esb.demo.SpringBootMongoDB.models.Pets;
import com.esb.demo.SpringBootMongoDB.service.PetsService;

@RestController
@RequestMapping(value = "/pets")
public class PetsController {

    @Autowired
    private PetsService petsService;

    @RequestMapping(value = "/all", method = RequestMethod.GET)
    public List<Pets> getAllPets() {
        return petsService.getAllPets();

    }

    @RequestMapping(value = "{id}", method = RequestMethod.GET)
    public Pets getPetById(@PathVariable("id") ObjectId id) {
        return petsService.getPetbyId(id);
    }

    @RequestMapping(value = "{id}", method = RequestMethod.PUT)
    public void modifyPetById(@PathVariable("id") ObjectId id, @RequestBody Pets pets) {
        pets.set_id(id);
        petsService.updatePetById(pets);
    }

    @RequestMapping(value = "/create", method = RequestMethod.POST)
    public Pets createPet(@RequestBody Pets pets) {
        pets.set_id(ObjectId.get());
        return petsService.save(pets);
    }

    @RequestMapping(value = "{id}", method = RequestMethod.DELETE)
    public void deletePet(@PathVariable ObjectId id) {
        petsService.deletePet(id);
    }
}


Step 10 : Creating Service

Now We will  create a Service class  by adding a file called PetsService.java to the src/main/java/[package name]/ folder.

package com.esb.demo.SpringBootMongoDB.service;

import java.util.List;

import org.bson.types.ObjectId;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.stereotype.Service;

import com.esb.demo.SpringBootMongoDB.models.Pets;
import com.esb.demo.SpringBootMongoDB.repositories.PetsRepository;

@Service
public class PetsService {

    @Autowired
    private PetsRepository repository;

    public List<Pets> getAllPets() {
        return repository.findAll();
    }

    public Pets getPetbyId(ObjectId id) {
        return repository.findBy_id(id);
    }

    public void updatePetById(Pets pets) {
        repository.save(pets);
    }

    public Pets save(Pets pets) {
        return repository.save(pets);
    }

    public void deletePet(ObjectId id) {
        repository.delete(repository.findBy_id(id));
    }
}



Step 10 : Testing Your API
Now that the controller has all of our endpoints, we can begin testing our API! From the command line, in the project root, run the mvn spring-boot:run command to compile the code and start the Spring server with the default port 8080.
Once the server starts, you are free to test your API however you choose.
With body : {"name" : "Liam", "species" : "cat", "breed" : "tabby"}
and header : 'Content-Type: application/json'
Returns:
{
    "_id": "5aecef5b6d55754834124df3",
    "name": "Liam",
    "species": "cat",
    "breed": "tabby"
}
With body : {"name" : "Liam", "species" : "cat", "breed" : "siamese"}
and header : Content-Type : application/json
empty response
Returns:
{
    "_id": "5aecef5b6d55754834124df3",
    "name": "Liam",
    "species": "cat",
    "breed": "siamese"
}

Returns:
empty response
Returns:
[
    {
        "_id": "5aeccb0a18365ba07414356c",
        "name": "Spot",
        "species": "dog",
        "breed": "pitbull"
    },
    {
        "_id": "5aeccb0a18365ba07414356d",
        "name": "Daisy",
        "species": "cat",
        "breed": "calico"
    },
    {
        "_id": "5aeccb0a18365ba07414356e",
        "name": "Bella",
        "species": "dog",
        "breed": "australian shepard"
    }
]


Wednesday, February 6, 2019

Code Review Guildline


What Do Code Reviewers Look For?

Code reviews should look at:

  • Design: Is the code well-designed and appropriate for your system?
  • Functionality: Does the code behave as the author likely intended? Is the way the code behaves good for its users?
  • Complexity: Could the code be made simpler? Would another developer be able to easily understand and use this code when they come across it in the future?
  • Tests: Does the code have correct and well-designed automated tests?
  • Naming: Did the developer choose clear names for variables, classes, methods, etc.?
  • Comments: Are the comments clear and useful?
  • Style: Does the code follow our style guides?
  • Documentation: Did the developer also update relevant documentation?



What do peer reviewers look for?

Feature Completion

The reviewer will make sure that the code meets the requirements, pointing out if something has been left out or has been done without asking the client.

Potential Side Effects

The reviewer will check to see whether the changed code causes any issues in other features.

Readability and Maintenance

The reviewer will make sure the code is readable and is not too complicated for someone completely new to the project. Model and variable names should be immediately obvious (again, even to new developers) and as short as possible without using abbreviations.

Consistency

Conducting peer reviews is the best approach for achieving consistency across all company projects. Define a code style with the team and then stick to it.

Performance

The reviewer will assess whether code that will be executed more often (or the most critical functionalities) can be optimized.

Exception Handling

The reviewer will make sure bad inputs and exceptions are handled in the way that was pre-defined by the team (it must be visible/accessible to everyone).

Simplicity

The reviewer will assess whether there are any simpler or more elegant alternatives available.

Reuse of Existing Code

The reviewer will check to see if the functionality can be implemented using some of the existing code. Code has to be aggressively “DRYed” (as in, Don’t Repeat Yourself) during development.

Test Cases

Finally, the reviewer will ensure the presence of enough test cases to go through all the possible execution paths. All tests have to pass before the code can be merged into the shared repository.


Tuesday, February 5, 2019

Gatling : A powerful open-source load testing solution



Gatling is designed for continuous load testing and integrates with your development pipeline. Gatling includes a web recorder and colorful reports.


https://gatling.io/download/

Tuesday, January 22, 2019

Mule: How to check mUnit Coverage

If you are using Mule Server CE. you cannot see the MUnit Coverage report. "Coverage is only available when using an EE Mule Server"




Anypoint Studio




You can solve the problem by changing the mule server run-time.

RightClient > Mule-project.xml




Re-run mUnit
RightClient> Run As > Munit







Now you can see the coverage. if you wan to see details. client on the "Generate Report"



Friday, January 4, 2019

Difference between Agile and Scrum

It seems lot of  people are confused about the difference between agile and scrum. In this article i will describe the difference in very easy and graphical way. look at the following images. Agile is a kind of Umbrella of framework and methodologies. 







Agile software development refers to a group of software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams.


scrum is one of the agile framework.
Scrum is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value





Saturday, November 17, 2018

Conflict Resolution : Importance and techniques

Imagine going to work everyday and facing a colleague who does not respect you or having to work with someone who was constantly undermining you decisions.Would it make getting up in the morning and heading off to work a motivating experience?

Conflict is an inevitable part of project work.

 Whenever people come together to solve problems, there will be differences of opinion and competing interests. Some degree of conflict is healthy , to ensure that ideas are sufficiently tested before adopted. However , we need to make sure the conflict does not escalate beyond healthy skepticism and friendly teasing, or will end up with a negative and repressive team environment.

Creating an environment in which people can use conflict constructively is a key part of successfully engaging stockholder in a project. We must watch for instances when conflict moves beyond normal, healthy debate and become destructive and harmful to the relationship and the team.


Speed B. Leas offer a framewod that helps us judge the seriousness of a conflict and better understand teh escalation path from Level 1 (Problem to Solve) to Level 5(World Ward).




Understanding Lea's framework on the stages of conflict can help us look at a situation more objectively, moving past our own judgement to see what is really happening. Identifying the conflict stage can also help us determine what actions we should take or what tools or techniques may work in the given situation.


Therefore, when a team is in a state of conflict, we should first take some time to observe the conflict and make sure we are seeing both sides of the dispute. not just jumping in with a knee-jerk reaction.
We need to allow time for proper observation, conversation, and intuition about the the issues before taking action. This means at-first we simply listen to the complaints, without immediately trying to solve them. we feel the energy of the group, and assess the conflict levels. We look for glances, eye rolling, and words that halt conversations to ascertain if the conflict is out in the open , or if it is playing in the out in subsurface snippets.

One way to assess the level of conflict is to focus on the language  the team uses and then compare the conversation against the 1 to 5 conflict scale. let's look at the language used at the level in more details.




5 Strategies for Getting More Work Done in Less Time

Summary.    You’ve got more to do than could possibly get done with your current work style. You’ve prioritized. You’ve planned. You’ve dele...