Skip to main content

CRUD in MongoDB & Spring Data

Now, since we have already been introduced to mongo and its server is setup. We shall now move on to performing basic CRUD operations.
Lets take a use case example of ‘Company’ database that stores employee information. 

We wish to store employee name, email address, age and multiple addresses. Traditionally in RDBMS we would create an Employee table and Address Table having foreign key reference to ‘employee id ‘




Incase of NoSQL, we will be creating Employee documnet which will have store employee information like name, email, age and an array of employes address. Following is a snippet of the schema defined
{
"name" : "",
"email" : "",
"age" : “”,
"address" : [ ... ]
}
Thus to begin with, we will first define the entities. We have employee as an aggregate root entity that stores list of address having 1-M relatioship. Address Entity is represend as @Embeddable as it is embaded in another aggregate root entity. Employee is represented as @Document as the object to presist. The Employees id property is annotated with @Id so that JPA will recognize it as the object’s ID. The id property is also annotated with @GeneratedValue to indicate that the ID should be generated automatically.

Employee.java

Address.java

We have to specify the server host & port in the configuration file here localhost : 27017. Mongo Template offers convenience to create, update, delete and query for MongoDB documents and provides a mapping between your domain objects and MongoDB documents.Here, we will be creating & mapping employee bean which is our domain object.

ApplicationContext.xml

Now creating repository interface with CRUD methods.
 


EmployeeRepository.java
EmployeeRepositoryImpl.java





EmployeeMain.java

We shall also define a web service that would return the list of all employees and also an employee by id


EmployeeWS.java

EmployeeWSImpl.java

You can also find the complete source code at  https://github.com/meta-magic/MongoDB.git

Output
Displaying all Employees [
******************************************************************
     Employee Information :=1, name:=aaa, age:=10, email:= a@y.com
      Employee Address
     Address :=home addr, pin:=22235  
     Address :=ofc addr, pin:=21345    ,
******************************************************************
     Employee Information :=2, name:=bbb, age:=3, email:= b@y.com
      Employee Address
     Address :=home addr 2, pin:=22235  
     Address :=ofc addr 2, pin:=21345    ]
Find Employee with EMPID:1
******************************************************************
     Employee Information :=1, name:=aaa, age:=10, email:= a@y.com
      Employee Address
     Address :=home addr, pin:=22235  
     Address :=ofc addr, pin:=21345  
Displaying all Employees after update EMPID:1[
******************************************************************
     Employee Information :=1, name:=abc, age:=10, email:= a@y.com
      Employee Address
     Address :=home addr, pin:=22235  
     Address :=ofc addr, pin:=21345    ,
******************************************************************
     Employee Information :=2, name:=bbb, age:=3, email:= b@y.com
      Employee Address
     Address :=home addr 2, pin:=22235  
     Address :=ofc addr 2, pin:=21345    ]
Displaying all Employees after deleting EMPID:2 [
******************************************************************
     Employee Information :=1, name:=zzz, age:=10, email:= a@y.com
      Employee Address
     Address :=home addr, pin:=22235  
     Address :=ofc addr, pin:=21345    ]

Comments

Popular posts from this blog

Centralized configuration using Spring Cloud Config

In this blog we will be focusing on centralized configuration using  Spring Cloud Config  project. For single standalone application we can keep all required configuration bundle with application itself.  However, when we have more than one application, say in a microservice architecture, a better alternative would be to manage the configurations centrally. With the Config Server we have a central place to manage external properties for applications with support for different environments. Configuration files in several formats like YAML or properties are added to a Git repository. Features Spring Cloud Config Server features: HTTP, resource-based API for external configuration (name-value pairs, or equivalent YAML content) Encrypt and decrypt property values (symmetric or asymmetric) Embeddable easily in a Spring Boot application using  @EnableConfigServer Config Client features (for Spring applications): Bind to the Config Server and initialize...

Function Point Analysis : ISO/IEC 20926:2009

This blog focuses on explaining the Function Point calculations. Software Sizing Background Function Point Rules for Counting FP Deep Dive - Function Point Analysis Case Study General Software Characteristics Details History - Measurement Methodologies Lines of Code (Oldest) Use case based Software Sizing IPFUG Function Point Analysis (ISO) Need for Software Sizing. Estimation and Budgeting Phasing Development Work Prioritization of Work Monitoring the Progress Bidding for Projects Allocating Testing Resources To measure and Manage Productivity Risk Assessment Software Asset Valuation CMMi Level 2 and 3 require that a valid sizing method be used. Software Sizing - Lines of Code The easiest and historically the most common method in Sizing Software project has been counting the number of lines of code and / or the number of screens. Advantages Automation of the counting process can be done Intuitive as the measurements are easily u...