Unit 5 FSD Iv Icse
Unit 5 FSD Iv Icse
Unit 5 FSD Iv Icse
Relational Schema
Relation schema defines the design and structure of the relation like it consists of the relation
name, set of attributes/field names/column names. every attribute would have an associated
domain.
There is a student named Geeks, she is pursuing B.Tech, in the 4th year, and belongs to IT
department (department no. 1) and has roll number 1601347 She is proctored by Mrs. S
Mohanty. If we want to represent this using databases we would have to create a student
table with name, sex, degree, year, department, department number, roll number and proctor
(adviser) as the attributes.
Note –
If we create a database, details of other students can also be recorded.
Similarly, we have the IT Department, with department Id 1, having Mrs. Sujata Chakravarty
as the head of department. And we can call the department on the number 0657 228662 .
This and other departments can be represented by the department table, having department
ID, name, hod and phone as attributes.
The course that a student has selected has a courseid, course name, credit and department
number.
The professor would have an employee Id, name, sex, department no. and phone number.
professor (empId, name, sex, startYear, deptNo, phone)
We can have another table named enrollment, which has roll no, courseId, semester, year and
grade as the attributes.
When we start courses, there are some courses which another course that needs to be
completed before starting the current course, so this can be represented by the Prerequisite
table having prerequisite course and course id attributes.
The relations between them is represented through arrows in the following Relation
diagram,
1. This represents that the deptNo in student table table is same as deptId used in department
table. deptNo in student table is a foreign key. It refers to deptId in department table.
2. This represents that the advisor in student table is a foreign key. It refers to empId in
professor table.
3. This represents that the hod in department table is a foreign key. It refers to empId in
professor table.
4. This represents that the deptNo in course table table is same as deptId used in department
table. deptNo in student table is a foreign key. It refers to deptId in department table.
5. This represents that the rollNo in enrollment table is same as rollNo used in student
table.
6. This represents that the courseId in enrollment table is same as courseId used in course
table.
7. This represents that the courseId in teaching table is same as courseId used in course
table.
8. This represents that the empId in teaching table is same as empId used in professor table.
10. This represents that the deptNo in student table is same as deptId used in department
table.
About SQL
Structured Query Language is a standard Database language that is used to create, maintain, and
retrieve the relational database. In this article, we will discuss this in detail about SQL. Following
are some interesting facts about SQL. Let’s focus on that.
SQL is case insensitive. But it is a recommended practice to use keywords (like SELECT, UPDATE,
CREATE, etc.) in capital letters and use user-defined things (like table name, column name, etc.) in
small letters.
We can write comments in SQL using “–” (double hyphen) at the beginning of any line. SQL is the
programming language for relational databases (explained below) like MySQL, Oracle, Sybase, SQL
Server, Postgre, etc. Other non-relational databases (also called NoSQL) databases like MongoDB,
DynamoDB, etc. do not use SQL.
Although there is an ISO standard for SQL, most of the implementations slightly vary in syntax. So
we may encounter queries that work in SQL Server but do not work in MySQL.
A relational database means the data is stored as well as retrieved in the form of relations (tables).
Table 1 shows the relational database with only one relation called STUDENT which
stores ROLL_NO, NAME, ADDRESS, PHONE, and AGE of students.
STUDENT Table
Important Terminologies
These are some important terminologies that are used in terms of relation.
Attribute:Attributes are the properties that define a relation. e.g.; ROLL_NO, NAME etc.
Tuple:Each row in the relation is known as tuple. The above relation contains 4 tuples, one of
which is shown as:
ROLL_NO
ROLL_NO
Data Definition Language:It is used to define the structure of the database. e.g; CREATE
TABLE, ADD COLUMN, DROP COLUMN and so on.
Data Query Language:It is used to extract the data from the relations. e.g.; SELECT So first we
will consider the Data Query Language. A generic query to retrieve from a relational database is:
DDL, or Data Definition Language, is a subset of SQL used to define and manage the structure of
database objects. DDL commands are typically executed once to set up the database schema.
DDL commands are used to define, modify, and manage the structure of database objects, such as
tables, indexes, and constraints. Some common DDL commands include:
Here are code snippets and their corresponding outputs for DDL commands:
SQL
Code Snippet Output
Command
“Email” column
ALTER
ALTER TABLE Employees ADD Email VARCHAR(100); added to the
TABLE
“Employees” table.
DML, or Data Manipulation Language, is a subset of SQL used to retrieve, insert, update, and delete data in a
database. DML commands are fundamental for working with the data stored in tables.
Here are code snippets and their corresponding outputs for DML commands:
SQL
Code Snippet Output
Command
INSERT INTO Employees (FirstName, LastName, New employee record added to the
INSERT
Department) VALUES ('John', 'Doe', 'HR'); “Employees” table.
DCL, or Data Control Language, is a subset of SQL used to manage database security and access control. DCL
commands determine who can access the database and what actions they can perform.
Here are code snippets and their corresponding real-value outputs for DCL commands:
SQL
Code Snippet Output (Real Value Example)
Command
TCL, or Transaction Control Language, is a subset of SQL used to manage database transactions. TCL
commands ensure data integrity by allowing you to control when changes to the database are saved permanently
or rolled back.
Here are code snippets and their corresponding outputs for TCL commands:
SQL
Code Snippet Output
Command
ROLLBACK BEGIN; -- SQL statements ROLLBACK; Changes made in the transaction rolled back.
NOTE:
An attribute which is not a part of GROUP BY clause can’t be used for selection.
Any attribute which is part of GROUP BY CLAUSE can be used for selection but it is not
mandatory.
But we could use attributes which are not a part of the GROUP BY clause in an aggregate function.
Conclusion
SQL is a standard language used to manage data in relational databases. SQL is mainly divided into
four main categories: Data definition language, data manipulation language, transaction control
language, and data query language and SQL is a powerful language that can be used to carry out a
wide range of operations like insert ,delete and update.
Normalization SQL
A large database defined as a single relation may result in data duplication. This repetition of data may
result in:
o It isn't easy to maintain and update data as it would involve searching many records in relation.
So to handle these problems, we should analyze and decompose the relations with redundant data into
smaller, simpler, and well-structured relations that are satisfy desirable properties. Normalization is a
process of decomposing the relations into relations with fewer attributes.
What is Normalization?
o Normalization is used to minimize the redundancy from a relation or set of relations. It is also
used to eliminate undesirable characteristics like Insertion, Update, and Deletion Anomalies.
o Normalization divides the larger table into smaller and links them using relationships.
o The normal form is used to reduce redundancy from the database table.
The main reason for normalizing the relations is removing these anomalies. Failure to eliminate
anomalies leads to data redundancy and can cause data integrity and other problems as the database
grows. Normalization consists of a series of guidelines that helps to guide you in creating a good
database structure.
o Insertion Anomaly: Insertion Anomaly refers to when one cannot insert a new tuple into a
relationship due to lack of data.
o Deletion Anomaly: The delete anomaly refers to the situation where the deletion of data
results in the unintended loss of some other important data.
o Updatation Anomaly: The update anomaly is when an update of a single data value requires
multiple rows of data to be updated.
Normalization works through a series of stages called Normal forms. The normal forms apply to
individual relations. The relation is said to be in particular normal form if it satisfies constraints.
2NF A relation will be in 2NF if it is in 1NF and all non-key attributes are fully functional
dependent on the primary key.
4NF A relation will be in 4NF if it is in Boyce Codd's normal form and has no multi-valued
dependency.
5NF A relation is in 5NF. If it is in 4NF and does not contain any join dependency, joining
should be lossless.
o First normal form disallows the multi-valued attribute, composite attribute, and their
combinations.
EMPLOYEE table:
14 John 7272826385, UP
9064738238
The decomposition of the EMPLOYEE table into 1NF has been shown below:
14 John 7272826385 UP
14 John 9064738238 UP
o In the second normal form, all non-key attributes are fully functional dependent on the primary
key
Example: Let's assume, a school can store the data of teachers and the subjects they teach. In a school,
a teacher can teach more than one subject.
TEACHER table
TEACHER_ID SUBJECT TEACHER_AGE
25 Chemistry 30
25 Biology 30
47 English 35
83 Math 38
83 Computer 38
To convert the given table into 2NF, we decompose it into two tables:
TEACHER_DETAIL table:
TEACHER_ID TEACHER_AGE
25 30
47 35
83 38
TEACHER_SUBJECT table:
TEACHER_ID SUBJECT
25 Chemistry
25 Biology
47 English
83 Math
83 Computer
o A relation will be in 3NF if it is in 2NF and not contain any transitive partial dependency.
o 3NF is used to reduce the data duplication. It is also used to achieve the data integrity.
o If there is no transitive dependency for non-prime attributes, then the relation must be in third
normal form.
A relation is in third normal form if it holds atleast one of the following conditions for every non-
trivial function dependency X → Y.
1. X is a super key.
Example:
EMPLOYEE_DETAIL table:
Non-prime attributes: In the given table, all attributes except EMP_ID are non-prime.
That's why we need to move the EMP_CITY and EMP_STATE to the new
<EMPLOYEE_ZIP> table, with EMP_ZIP as a Primary key.
EMPLOYEE table:
EMPLOYEE_ZIP table:
201010 UP Noida
02228 US Boston
60007 US Chicago
06389 UK Norwich
462007 MP Bhopal
o A table is in BCNF if every functional dependency X → Y, X is the super key of the table.
o For BCNF, the table should be in 3NF, and for every FD, LHS is super key.
Example: Let's assume there is a company where employees work in more than one department.
EMPLOYEE table:
1. EMP_ID → EMP_COUNTRY
The table is not in BCNF because neither EMP_DEPT nor EMP_ID alone are keys.
To convert the given table into BCNF, we decompose it into three tables:
EMP_COUNTRY table:
EMP_ID EMP_COUNTRY
264 India
264 India
EMP_DEPT table:
EMP_DEPT_MAPPING table:
EMP_ID EMP_DEPT
D394 283
D394 300
D283 232
D283 549
Functional dependencies:
1. EMP_ID → EMP_COUNTRY
2. EMP_DEPT → {DEPT_TYPE, EMP_DEPT_NO}
Candidate keys:
Forthefirsttable: EMP_ID
Forthesecondtable: EMP_DEPT
For the third table: {EMP_ID, EMP_DEPT}
Now, this is in BCNF because left side part of both the functional dependencies is a key.
o A relation will be in 4NF if it is in Boyce Codd normal form and has no multi-valued
dependency.
o For a dependency A → B, if for a single value of A, multiple values of B exists, then the
relation will be a multi-valued dependency.
Example
STUDENT
21 Computer Dancing
21 Math Singing
34 Chemistry Dancing
74 Biology Cricket
59 Physics Hockey
The given STUDENT table is in 3NF, but the COURSE and HOBBY are two independent entity.
Hence, there is no relationship between COURSE and HOBBY.
In the STUDENT relation, a student with STU_ID, 21 contains two courses, Computer and Math and
two hobbies, Dancing and Singing. So there is a Multi-valued dependency on STU_ID, which leads to
unnecessary repetition of data.
So to make the above table into 4NF, we can decompose it into two tables:
STUDENT_COURSE
STU_ID COURSE
21 Computer
21 Math
34 Chemistry
74 Biology
59 Physics
STUDENT_HOBBY
STU_ID HOBBY
21 Dancing
21 Singing
34 Dancing
74 Cricket
59 Hockey
o A relation is in 5NF if it is in 4NF and not contains any join dependency and joining should be
lossless.
o 5NF is satisfied when all the tables are broken into as many tables as possible in order to avoid
redundancy.
Example
SUBJECT LECTURER SEMESTER
In the above table, John takes both Computer and Math class for Semester 1 but he doesn't take Math
class for Semester 2. In this case, combination of all these fields required to identify a valid data.
Suppose we add a new Semester as Semester 3 but do not know about the subject and who will be
taking that subject so we leave Lecturer and Subject as NULL. But all three columns together acts as a
primary key, so we can't leave other two columns blank.
So to make the above table into 5NF, we can decompose it into three relations P1, P2 & P3:
P1
SEMESTER SUBJECT
Semester 1 Computer
Semester 1 Math
Semester 1 Chemistry
Semester 2 Math
P2
SUBJECT LECTURER
Computer Anshika
Computer John
Math John
Math Akash
Chemistry Praveen
P3
SEMSTER LECTURER
Semester 1 Anshika
Semester 1 John
Semester 1 John
Semester 2 Akash
Semester 1 Praveen
Advantages of Normalization
Disadvantages of Normalization
o You cannot start building the database before knowing what the user needs.
o The performance degrades when normalizing the relations to higher normal forms, i.e., 4NF,
5NF.
o Careless decomposition may lead to a bad database design, leading to serious problems.
There are a number of options for selecting an approach to form the basis for your JDBC
database access. Spring framework provides the following approaches for JDBC database
access:
JdbcTemplate
NamedParameterJdbcTemplate
SimpleJdbcTemplate
SimpleJdbcInsert and SimpleJdbcCall
JDBC Template
JdbcTemplate is a central class in the JDBC core package that simplifies the use of
JDBC and helps to avoid common errors. It internally uses JDBC API and
eliminates a lot of problems with JDBC API. It executes SQL queries or updates,
initiating iteration over ResultSets and catching JDBC exceptions
and translating them to the generic. It executes core JDBC workflow, leaving application
code to provide SQL and extract results. It handles the exception and provides the
informative exception messages with the help of exception classes defined in the
org.springframework.dao package.
The common methods of spring JdbcTemplate class.
Methods Description
public int update(String query) Used to insert, update and delete records.
public int update(String query, Used to insert, update and delete records using
Object… args) PreparedStatement using given arguments.
{
DriverManagerDataSource dataSource
= newDriverManagerDataSource();
dataSource.setDriverClassName(
"com.mysql.jdbc.Driver"); dataSource.setUrl(
"jdbc:mysql://localhost:8800/springjdbc");
dataSource.setUsername("user"); dataSource.setPassword("password");
returndataSource;
}
}
A. File: Student.java
Java
packagecom.exploit.org;
// Class
publicclassStudent {
B. File: StudentDAO.java
Below is the implementation of the Data Access Object interface file StudentDAO.java
Example:
Java
// Class
publicinterfaceStudentDAO {
// Used to initialize database resources
// ie. connection
publicList<Student> listStudents();
XML
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-jdbc</artifactId>
</dependency>
<dependency>
<groupId>mysql</groupId>
<artifactId>mysql-connector-java</artifactId>
<scope>runtime</scope>
</dependency>
D. File: StudentJDBCTemplate.java
Below is the implementation class file StudentJDBCTemplate.java for the defined
DAO interface StudentDAO.
Example:
Java
// Java Program Illustrating Implementation
// of StudentDAO Class
packagecom.exploit.org;
// Class
publicclassStudentJDBCTemp implementsStudentDAO {
privateDataSource dataSource;
privateJdbcTemplate jdbcTemplateObject;
// Method 1
// Method 2
publicList<Student> listStudents()
returnstudents;
}
Agile development principles
Any Agile Software method is characterized during a manner that addresses a variety of key
assumptions concerning the bulk of software projects:
It is troublesome to predict before that software needs will persist and which can
amendment. it’s equally troublesome to predict however client priorities can amendment
because of the project payoff.
For many sorts of software, style and construction are interleaved. That is, each activity
ought to be performed in order that style models are verified as they’re created. it’s
troublesome to predict what proportion design is critical before construction is employed to
prove the look
Analysis, design, construction, and testing aren’t as inevitable (from a designing purpose of
view) as we’d like.
Given these 3 assumptions, a crucial question arises: however will we produce a method which
will manage unpredictability? the solution, as I’ve got already noted, lies in method ability (to
quickly dynamic project and technical conditions). the associate agile method, therefore,
should be adaptable.
But continual adaptation while not forward progress accomplishes very little. Therefore, the
associate agile software method should adapt to incrementally. To accomplish progressive
adaptation, the associate agile team needs client feedback (so that the suitable variations are
often made).
A good catalyst for client feedback is an associate operational paradigm or a little of an
operational system. Hence, associate progressive development strategy ought to be instituted.
software increments (executable prototypes or parts of the associated operational system)
should be delivered in brief time periods in order that adaptation keeps pace with the
amendment (unpredictability).
This unvarying approach permits the client to evaluate the package increment frequently, offer
necessary feedback to the software team, and influence the method variations that are created
to accommodate the feedback.
Agility Principles:
Agile is based on 4 key values and 12 key principles. While the agile values provide project managers
and developers with a very general overview of what it means to be ‘agile,’ and help guide the agile
process, the 12 agile principles give examples of how agile should be implemented.
The 12 agile principles underpin every successful agile project and can inspire even non-agile teams.
They form a core part of any agile project management course.
When developing a product, speed and precision is key. Should development take too long, there is an
increasing risk that the final product will no longer satisfy rapidly changing market demands and
consumer needs.
Traditional methods may often develop a product in a vacuum, following a strict development plan
with no deviation which results in delivering a final product that is already obsolete.
Our highest priority is to satisfy the customer through early and continuous delivery of valuable
software.
Agile aims to deliver a functioning product in the very first development iteration. It will be a long
way from being finished; but it just has to give the customer enough of an idea so that developers can
receive valuable feedback. In doing so, agile projects can tailor the product as it is being developed to
deliver something that satisfies customers’ needs.
Agile takes large tasks and breaks them up into smaller, more manageable chunks. The interactive
nature of agile not only improves project development but also service delivery.
2. Embrace change
Project development is becoming increasingly unpredictable. Markets are becoming more complex and
the number of diverse products available to consumers grows every day. It’s nearly impossible to
predict what the final requirements of a project will be and as such, development projects are an
increasingly risky.
Welcome changing requirements, even late in development. Agile processes harness change for the
customer’s competitive advantage.
Most businesses don’t like risk, but what is even less desirable is wasting time and resources
developing a product that’s no longer relevant by the time it’s finally completed. By welcoming
change and actively seeking to make improvements through consumer feedback, businesses can gain a
competitive edge – their products will satisfy the immediate needs of consumers and their products
will be guaranteed to provide business value.
People change, times change, markets change. Trying to fight it is pointless. Traditional project
management usually sees change as a problem to be solved, but agile embraces change and uses it to
the customer’s advantage.
3. Frequent delivery
This principle may closely mirror the first, but while the first states that products should be
delivered early, this principle goes a little more into detail as to why products should be
delivered continuously.
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference
to the shorter timescale.
Smaller, more frequent releases mean less chance of error. Frequent releases give consumers more
opportunity to provide feedback which, in turn, aids developers in correcting errors that might
otherwise have derailed a project. If developers only receive feedback every few months, any errors
made early in development may have since become much more difficult and costly to fix.
Many businesses apply this principle so that they deliver new iterations of software or products every
few days. This just goes to show the importance of frequent delivery, which is arguably one of the
most defining agile principles.
4. Cooperation
In traditional management, the work business owners and stakeholders is usually kept distinct from the
work of developers. Analysist are put in place to ‘translate’ business needs into development plans and
project managers simply help mediate the demands of owners in a way that doesn’t negatively affect
product development.
Business people and developers must work together daily throughout the project.
Agile requires that stakeholders, customers and developers work in unison (often in the same room) to
achieve project goals. This reduces the risk inherent to project development, by helping improve
communication and cooperation. In addition, the more closely management is involved with
development, the easier it is for them to understand the challenges faced by developers and the
ramifications of changes made to development.
Too often, business owners forget that their employees are professionals who take pride in their work
(this is especially true in any creative role). If you build your projects around people who aren’t
motivated to succeed, they’re very likely to fail. That’s not the fault of developers, it’s the fault of
management.
Owners and managers need to create an environment that rewards success, fosters healthy working
relationships and helps improve employees’ work/life balance. Give developers the tools and
motivation to succeed and you’ll be rewarded with easier project development and better returns on
investment.
6. Better communication
Technology provides businesses a hundred different ways to communicate with employees, but none
will ever be as good as face-to-face communication. 2020 has drastically changed the way we work,
with more employees working remotely than ever before, businesses are becoming reliant on
communication tools such as Skype and Microsoft Teams. While these might be just good enough, the
changes of error do increase when teams lack fact-to-face communication. Information gets lost in
translation, emails and memos get buried in inboxes etc.
The most efficient and effective method of information to and within a development is face-to-face
conversation.
7. Working software
Replace ‘software’ with ‘products’ and you’ll find a fairly self-explanatory principles applicable to
every project every developed. This principle came about in response to excessive documentation and
procedures in the IT industry that slowed development.
Working software is the primary measure of progress.
In other industries, this principle might be summarized as such: “A working product is more valuable
than a checklist.” Requirements analysis documents, models and mock-ups may be useful, but they
aren’t very useful if you can’t convert this information into a working product.
Project managers and business owners alike need to focus on minimizing paperwork and maximizing
productivity. Unfinished products are inventory and inventory is an expense that provides no value.
Agile promotes the idea of sustainable development. In short, this means that with the correct
implementation of agile methods, there should never be the need for developers to work ridiculous
hours just to meet deadlines.
Agile requires stakeholders, customers and developers to act as one coherent team. When everyone
involved feeds information into an agile framework, it becomes very easy to create accurate forecasts,
budgets and timelines.
Agile processes promote sustainable development. The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.
Customers tell developers what they need, stakeholders understand how changes may affect
development and teams can make informed decisions as to how progress is to be made. No one is left
out of the loop and no one is taken by surprise by unexpected developments.
9. Quality assurance
Many businesses prioritize speed or quantity over quality. In some cases, this makes a lot of sense.
Sometimes customers don’t care as much for quality so whether or not a product works.
But, if development teams neglect quality for too long, their ability to adapt the product to suit current
consumer demands diminishes and it becomes less agile.
Continuous attention to technical excellence and good design enhances agility.
10. Simplicity
This principle is like number 7: working software. But while the focus of that principle was about
removing unnecessary documentation, this principle focuses more on processes.
This principle can be achieved in several ways. Firstly, you can remove bloated processes that do not
contribute to the overall quality or progress of a project. Secondly, you can rely on automation to
complete repetitive or time-consuming tasks. Or thirdly, you might use pre-existing assets from past
projects rather than creating ones from scratch each time you begin something new.
Simplicity—the art of maximizing the amount of work not done—is essential.
This principle should be an ongoing effort. Agile teams need to recognize that there is always room for
improvement. Technology provides us more varied, easier ways of doing things. Project management
research helps managers and business continuously improve their practices to suit modern trends etc.
Being agile requires businesses hold weekly or even daily meetings. A large part of these should be
dedicated towards finding new and better ways of accomplishing tasks.
Agile teams however, are comprised of multiple individuals, who share a wide variety of skills in
several disciplines. Furthermore, agile development teams often include stakeholders, managers and
consumers as core team-members. This allows them to work independently as a unit without the need
to look to others for assistance.
This not only minimizes the need for upper management to micro-manage development but also
ensures that processes such as quality assurance and adaptation are an inherent part of agile
development and thus occur naturally and autonomously.
No team acts perfectly but a mature, informed and responsible team can improve itself by taking both
pro-active and reactive measures to improve development.
Although the 12 agile principles were developed almost 2 decades ago, they are still relevant and will
likely remain relevant for a long time to come.
That is because the key agile principles are anthropocentric. That is to say, they are based on human
values and helps improve the quality of life in the workspace. Agile aims to improve the well-being of
workers just as much as it aims to deliver high-quality products.
Better, smoother, more efficient development means happier, less stressed workers and more satisfied
customers.
Deploying application in Cloud
The use of cloud services is expeditiously growing among businesses. Indeed, a majority of companies
are switching from on-premises solutions to cloud deployment models because of their engaging
features.
However, it is still complicated for many of them to understand cloud deployment, its pros, cons, and
how they can deploy an app through different cloud platforms.
So, this article will share a detailed guide about cloud deployment with all of its models, advantages,
and limitations. It will also discuss how to deploy an application through leading cloud service
providers.
How to deploy an application on a cloud computing platform?
IaaS, or Infrastructure as a Service is a cloud service model that guarantees the supply of
storage, servers, networking, compute, and security resources. This cloud computing model
enables businesses to run their programs on rented and globally installed servers.
If we discuss the IaaS benefits, it lowers the on-premises infrastructure cost and provides
spontaneous insights of the app’s performance. Besides, IaaS ensures business continuity with
updated hardware and decreases capital expenditures.
AWS, Azure, Linode, IBM Cloud, and DigitalOcean are prominent IaaS vendors.
Platform as a Service is another most used cloud computing model that provides users with a thorough
environment to deploy and create an application in the cloud.
In this regard, PaaS doesn’t only offer resources like computing, servers, networking, and
storage. But it also confers operating systems, database management, development, and further
middleware tools.
By the same token, if we talk about PaaS advantages, it doesn’t only reduce the coding duration
by providing supportive tools but also is cost-efficient.
Moreover, Platform as a Service provider saves the time that you have to consume for stack
lineup and maintenance.
AWS Elastic Beanstalk, Heroku, Dokku, Engine Yard, and OpenShift are leading platforms in
this regard.
BaaS is another computing model that permits developers to outsource assistance for server-side
operations and only emphasizes frontend development.
With Backend as a Service (BaaS) platforms, businesses only have to invest energies in
client-side logic and core competencies. Surely, BaaS vendors take care of cloud storage,
database management, hosting, authentication, and further backend tasks in this regard.
This cloud computing model helps companies and development teams get an edge over
competitors with fast development, minimal cost, and less time to market. Cross-platform app
creation and less need for backend engineers are also pros of using BaaS platforms.
Back4App, 8Base, Kuzzle, and Parse are reliable BaaS vendors hereof.
Software as a Service (SaaS) confers an all-in-one solution to utilize cloud applications and
integrate them with other apps.
In other words, this cloud computing model includes all PaaS and IaaS resources with hosted
applications. Additionally, SaaS vendors allow users to choose a pay-as-you-go policy despite
purchasing the software at once.
With SaaS providers, businesses don’t have to install, run and update any hardware, software,
and middleware resources. Remote work, data approach from anywhere, and high scalability are
benefits of using SaaS platforms.
Deployment Models
The cloud deployment model identifies the specific type of cloud environment based on
ownership, scale, and access, as well as the cloud’s nature and
purpose. The location of the servers you’re utilizing and who controls them are defined by a
cloud deployment model. It specifies how your cloud infrastructure will look, what you can
change, and whether you will be given services or will have to create everything yourself.
Relationships between the infrastructure and your users are also defined by cloud
deployment types.
Public Cloud
The public cloud makes it possible for anybody to access systems and services. The public
cloud may be less secure as it is open to everyone. The public cloud is one in which
cloud infrastructure services are provided over the internet to the general people or
major industry groups. The infrastructure in this cloud model is owned by the entity that
delivers the cloud services, not by the consumer. It is a type of cloud hosting that allows
customers and users to easily access systems and services. This form of cloud computing is
an excellent example of cloud hosting, in which service providers supply services to a
variety of customers. In this arrangement, storage backup and retrieval services are given
for free, as a subscription, or on a per-user basis. Example: Google App Engine etc.
Private Cloud
The private cloud deployment model is the exact opposite of the public cloud deployment
model. It’s a one-on-one environment for a single user (customer). There is no need to
share your hardware with anyone else. The distinction between private and public clouds is
in how you handle all of the hardware. It is also called the “internal cloud” & it refers to the
ability to access systems and services within a given border or organization. The cloud
platform is implemented in a cloud-based secure environment that is protected by powerful
firewalls and under the supervision of an organization’s IT department. The private cloud
gives greater flexibility of control over cloud resources.
Hybrid Cloud
By bridging the public and private worlds with a layer of proprietary software, hybrid cloud
computing gives the best of both worlds. With a hybrid solution, you may host the app in
a safe environment while taking advantage of the public cloud’s cost savings.
Organizations can move data and applications between different clouds using a
combination of two or more cloud deployment methods, depending on their needs.
Advantages of Hybrid Cloud Model:
.
Disadvantages of Hybrid Cloud Model:
Difficult to manage: Hybrid clouds are difficult to manage as it
is a combination of both public and private cloud. So, it is
complex.
Community Cloud
o Rigid in customization: As the data and resources are shared among different
organizations according to their mutual interests if an organization wants some changes
according to their needs they cannot do so because it will have an impact on other
organizations
Multi-cloud
We’re talking about employing multiple cloud providers at the same time under this
paradigm, as the name implies. It’s similar to the hybrid cloud deployment approach, which
combines public and private cloud resources. Instead of merging private and public
clouds, multi-cloud uses many public clouds. Although public cloud providers
provide numerous tools to improve the reliability of their services, mishaps still occur. It’s
quite rare that two distinct clouds would have an incident at the same moment. As a result,
multi-cloud deployment improves the high availability of your services even more.
Advantages of a Multi-Cloud Model:
You can mix and match the best features of each cloud provider’s services to suit
the demands of your apps, workloads, and business by choosing different cloud
providers.
Reduced Latency: To reduce latency and improve user experience, you can choose
cloud regions and zones that are close to your clients.
High availability of service: It’s quite rare that two distinct clouds would have an
incident at the same moment. So, the multi-cloud deployment improves the high
availability of your services.
Complex: The combination of many clouds makes the system complex and
bottlenecks may occur.
Security issue: Due to the complex structure, there may be loopholes to which a
hacker can take advantage hence, makes the data insecure.
Example:
AWS
Amazon Web Service (AWS) is the world’s leading cloud infrastructure and service provider.
According to a report by Synergy Research Group, AWS occupies the first position among CSPs, with
a market share worth $200 billion in the second quarter of 2022. In addition, this cloud platform is also
known for providing more than 200 cloud products.
However, if we talk about how to deploy an app on AWS, the first thing that you need to do is signup.
Unluckily, registration is not wholly free. You will have to provide your credit card details to AWS, and
it will probably hold $1 from your card.
After completing all registration steps, you can now access AWS Console, and AWS Amplify could be
a reliable place to deploy or host your app with AWS. It is undoubtedly a trustworthy product for
deploying JS, React, or Vue.js applications.
AWS Amplify doesn’t only help in building the server side of your applications, but it is also swift and
safe to deploy applications in the cloud. Developers can choose the ‘AWS Amplify’ from AWS
Console. You can now elect the Deliver section and then click on ‘Get Started’.
To deploy and host an application with AWS Amplify, businesses and developers can take advantage of
various means, including GitHub, Bitbucket, GitLab, and AWS CodeCommit. It is also possible to
perform cloud deployment with AWS Amplify in the absence of a Git provider, but we are showing a
way to set up an app in the cloud through GitHub.
Now, users just need to conduct GitHub authorization and select the right branch and repository. After
performing this step, you can see two options: backend environments and frontend environments. You
can choose the desired environment and connect the branch.
Subsequently, it takes a few seconds to provision, build, deploy and verify an application.
On the other hand, if you want to deploy a web application, then Amazon EC2 should be preferred.
Similarly, Amazon S3 could also be an option for cloud deployment.
Conclusion
Cloud deployment is getting a competitive edge over other means of setting up applications. Therefore,
this article confers a detailed guide about deploying apps in the cloud through different CSPs.
Hopefully, with this comprehensive road map, it will be uncomplicated for startups, novice developers,
and enterprises to adopt or switch to cloud service.
10. Entertainment Applications : Many people get entertainment from the internet, in that case,
cloud computing is the perfect place for reaching to a varied consumer base. Therefore
different types of entertainment industries reach near the target audience by adopting a multi-
cloud strategy. Cloud- based entertainment provides various entertainment applications such
as
11. online music/video, online games and video conferencing, streaming services, etc and it an
reach any device be it TV, mobile, set-top box, or any other form. It is a new form of
entertainment called On-Demand Entertainment (ODE). With respect to this as a cloud, the
market is growing rapidly and it is providing various services day by day. So other
application of cloud computing includes social applications, management application, business
applications, art application, and many more. So in the future cloud computing is going to
touch many more sectors by providing more applications and services.