Databases Reference
In-Depth Information
// Relate users to each other
users
.
createRelationshipsTo
(
getExisting
(
users
)
.
numberOfTargetNodes
(
minMax
(
50
,
100
)
)
.
relationship
(
friend
)
.
relationshipConstraints
(
BOTH_DIRECTIONS
)
)
.
updateNoReturn
(
dataset
);
dataset
.
end
();
}
Neode uses node and relationship specifications to describe the nodes and relationships
in the graph, together with their properties and permitted property values. Neode then
provides a fluent interface for creating and relating nodes.
Capacity Planning
At some point in our application's development life cycle we'll want to start planning
for production deployment. In many cases, an organization's project management gat‐
ing processes mean a project cannot get underway without some understanding of the
production needs of the application. Capacity planning is essential both for budgeting
purposes and for ensuring there is sufficient lead time for procuring hardware and
reserving production resources.
In this section we describe some of the techniques we can use for hardware sizing and
capacity planning. Our ability to estimate our production needs depends on a number
of factors: the more data we have regarding representative graph sizes, query perfor‐
mance, and the number of expected users and their behaviors, the better our ability to
estimate our hardware needs. We can gain much of this information by applying the
techniques described in
“Testing” on page 82
early in our application development life
cycle. In addition, we should understand the cost/performance trade-offs available to
us in the context of our business needs.
Optimization Criteria
As we plan our production environment we will be faced with a number of optimization
choices. Which we favor will depend upon our business needs:
Cost
We can optimize for cost by installing the minimum hardware necessary to get the
job done.
Performance
We can optimize for performance by procuring the fastest solution (subject to
budgetary constraints).
