In this chapter, we will cover the following topics:
Performing data modeling and table creations
Developing services for the sign-up activity for web applications
Developing services for the sign-in activity for web applications
Developing services for the Address Book application
Deploying web applications on AWS Elastic Beanstalk
In the earlier chapters, we learned various things about DynamoDB and worked on various recipes to see how things work. Now, it's time to develop a real-world application step by step, integrating all the pieces together to build an Internet scalable web application.
In this chapter, we are going to see how to build an Address Book web application. The requirements are quite similar to any application that we use these days:
A new user should be able to register to the application
A registered user should be able to log in to the application
A logged-in user should be able to add new contacts
A logged-in user should be able to view the already added contacts
We would also like to see our application being hosted on AWS Beanstalk so that any user on the Internet should be able to use this application.
The technology stack for this application would be as follows:
Java for backend services
Spring MVC for the REST API development
DynamoDB for data storage
AngularJS for frontend
AWS Elastic...
In this recipe, we will see how to model data for this web application and create a DynamoDB table accordingly.
To get started with this recipe, you need to know how to create a table in DynamoDB using the console.
To perform data modeling for any web application using the NoSQL database as a backend, we need to first start with what queries we would like to execute on the tables. Considering the requirements, we will need at least two tables:
User: This is a table used to store information of a valid user's details along with the credentials
Contact: This is a table used to store information of all the contacts added by the users
As we will use the user table to save the registered user's information, as well as to sign-in, we can use email as the hash key for this table.
Here, we won't need a range key as the e-mail ID should be good enough to recognize a user for its registration and login. So, let's create the user table...
In the earlier recipe, we created DynamoDB tables based on the need. Now, we will write services to put the data into DynamoDB and get the data back for our application. In this recipe, we will learn how to write services for the sign-up/user registration activity.
Let's write services to put the data into DynamoDB:
To get started, we will first create a maven project and add the AWS SDK:
dependency:<dependency> <groupId>com.amazonaws</groupId> <artifactId>aws-java-sdk-dynamodb</artifactId> <version>1.10.4.1</version> </dependency>
Next, we will create a model class for the user table. Here, we will use the DynamoDBMapper class to connect to DynamoDB using Object Persistence Model. We will also consider attributes, such as the first name, last name, password, and so on...
In the earlier recipe, we wrote and tested services for user registration. In this recipe, we will implement services for the user sign-in.
For this recipe, we will use the same project that we created earlier:
To start with, we use the same user model that we defined in the earlier recipe. As we had encrypted the password during registration, it is very important to use the same client, which was initiated by the encryption provider:
static AmazonDynamoDBClient client = new AmazonDynamoDBClient(
new ClasspathPropertiesFileCredentialsProvider());
static DynamoDBMapper mapper = new DynamoDBMapper(client,
DynamoDBMapperConfig.DEFAULT, new AttributeEncryptor(
EncryptorProvider.getProvider()));
static {
client.setRegion(Region.getRegion(Regions.US_WEST_2));
}Next, we write a method which will fetch the user record...
Now that we are done with the sign-up and sign-in activities for our address book application, it's time to get star ted with developing address-related services. In this recipe, we will develop two APIs, one to add a new contact and another one to view all the contacts.
For this recipe, we will also use the same project setup that we had earlier:
To get started, we need to first create a model class for a contact record in the contact table. Here, we create the table with the hash key as ID (auto-generated) and the range key as the parent ID (e-mail ID of the user who added this contact):
@DynamoDBTable(tableName = "contact")
public class Contact {
private String id;
private String parentId;
private String fname;
private String lname;
private String phone;
private String email;
@DynamoDBHashKey
@DynamoDBAutoGeneratedKey...AWS Elastic Beanstalk allows you to quickly deploy your applications on Cloud, and they can be made accessible to the public. You can build your applications in languages, such as Java, PHP, Ruby, and so on and deploy them to the application server of your choice, such as Apache Tomcat, PHP, Windows Server, Node.js, and so on.
You can read more about Elastic Beanstalk at http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/Welcome.html.
In this recipe, we will see how to deploy the Address Book application using Elastic Beanstalk and access it from Cloud.
To get started with this recipe, you should already have built your application and tested it locally. There are several ways to deploy the application, but for this recipe, we will use the Eclipse AWS Toolkit. You should also have installed the AWS Toolkit for Eclipse. If you haven't done this yet, you can refer to http://docs.aws.amazon.com/AWSToolkitEclipse/latest/GettingStartedGuide...
© 2015 Packt Publishing Limited All Rights Reserved
