20131112 Presenting Neo4j
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

View only
 
 
ABCDEFGHIJKLMNOPQRSTUV
1
IDNodeTypeCommentsFromTypeTo
2
1Neo4jProductcreate (n:node:Product{id:'1', name:'Neo4j', type:'Product', comments:''});1IS_A2MATCH (n1:node), (n2:node) where n1.id='1' and n2.id='2' create n1-[:IS_A]->n2;
3
2Graph DatabaseCategorycreate (n:node:Category{id:'2', name:'Graph Database', type:'Category', comments:''});2BASED_ON_THEORY_OF3MATCH (n1:node), (n2:node) where n1.id='2' and n2.id='3' create n1-[:BASED_ON_THEORY_OF]->n2;
4
3GraphsMathcreate (n:node:Math{id:'3', name:'Graphs', type:'Math', comments:''});3PART_OF9MATCH (n1:node), (n2:node) where n1.id='3' and n2.id='9' create n1-[:PART_OF]->n2;
5
4SetsMathcreate (n:node:Math{id:'4', name:'Sets', type:'Math', comments:''});6PART_OF9MATCH (n1:node), (n2:node) where n1.id='6' and n2.id='9' create n1-[:PART_OF]->n2;
6
5DatabaseSystemcreate (n:node:System{id:'5', name:'Database', type:'System', comments:''});7PART_OF9MATCH (n1:node), (n2:node) where n1.id='7' and n2.id='9' create n1-[:PART_OF]->n2;
7
6DocumentsDatamodelcreate (n:node:Datamodel{id:'6', name:'Documents', type:'Datamodel', comments:''});8PART_OF9MATCH (n1:node), (n2:node) where n1.id='8' and n2.id='9' create n1-[:PART_OF]->n2;
8
7Key-Value pairsDatamodelcreate (n:node:Datamodel{id:'7', name:'Key-Value pairs', type:'Datamodel', comments:''});2STORES_DATA_IN_A5MATCH (n1:node), (n2:node) where n1.id='2' and n2.id='5' create n1-[:STORES_DATA_IN_A]->n2;
9
8Column FamiliesDatamodelcreate (n:node:Datamodel{id:'8', name:'Column Families', type:'Datamodel', comments:''});10STORES_DATA_IN_A5MATCH (n1:node), (n2:node) where n1.id='10' and n2.id='5' create n1-[:STORES_DATA_IN_A]->n2;
10
9Not Only SQLCategorycreate (n:node:Category{id:'9', name:'Not Only SQL', type:'Category', comments:''});10BASED_ON_THEORY_OF4MATCH (n1:node), (n2:node) where n1.id='10' and n2.id='4' create n1-[:BASED_ON_THEORY_OF]->n2;
11
10RDBMSCategorycreate (n:node:Category{id:'10', name:'RDBMS', type:'Category', comments:''});11IS_A10MATCH (n1:node), (n2:node) where n1.id='11' and n2.id='10' create n1-[:IS_A]->n2;
12
11MySQLProductcreate (n:node:Product{id:'11', name:'MySQL', type:'Product', comments:''});12IS_A10MATCH (n1:node), (n2:node) where n1.id='12' and n2.id='10' create n1-[:IS_A]->n2;
13
12MS AccessProductcreate (n:node:Product{id:'12', name:'MS Access', type:'Product', comments:''});13IS_A10MATCH (n1:node), (n2:node) where n1.id='13' and n2.id='10' create n1-[:IS_A]->n2;
14
13MS SQL ServerProductcreate (n:node:Product{id:'13', name:'MS SQL Server', type:'Product', comments:''});14IS_A10MATCH (n1:node), (n2:node) where n1.id='14' and n2.id='10' create n1-[:IS_A]->n2;
15
14OracleProductcreate (n:node:Product{id:'14', name:'Oracle', type:'Product', comments:''});15IS_A10MATCH (n1:node), (n2:node) where n1.id='15' and n2.id='10' create n1-[:IS_A]->n2;
16
15IBM DB2Productcreate (n:node:Product{id:'15', name:'IBM DB2', type:'Product', comments:''});16IS_A10MATCH (n1:node), (n2:node) where n1.id='16' and n2.id='10' create n1-[:IS_A]->n2;
17
16PostgreSQLProductcreate (n:node:Product{id:'16', name:'PostgreSQL', type:'Product', comments:''});1IS_GOOD_AT17MATCH (n1:node), (n2:node) where n1.id='1' and n2.id='17' create n1-[:IS_GOOD_AT]->n2;
18
17Use CaseCategorycreate (n:node:Category{id:'17', name:'Use Case', type:'Category', comments:''});18IS_A17MATCH (n1:node), (n2:node) where n1.id='18' and n2.id='17' create n1-[:IS_A]->n2;
19
18RecommendationsUseCasecreate (n:node:UseCase{id:'18', name:'Recommendations', type:'UseCase', comments:''});19IS_A17MATCH (n1:node), (n2:node) where n1.id='19' and n2.id='17' create n1-[:IS_A]->n2;
20
19Fraud Analysis and DetectionUseCasecreate (n:node:UseCase{id:'19', name:'Fraud Analysis and Detection', type:'UseCase', comments:''});20IS_A17MATCH (n1:node), (n2:node) where n1.id='20' and n2.id='17' create n1-[:IS_A]->n2;
21
20Impact AnalysisUseCasecreate (n:node:UseCase{id:'20', name:'Impact Analysis', type:'UseCase', comments:''});21IS_A17MATCH (n1:node), (n2:node) where n1.id='21' and n2.id='17' create n1-[:IS_A]->n2;
22
21Route planning and path findingUseCasecreate (n:node:UseCase{id:'21', name:'Route planning and path finding', type:'UseCase', comments:''});22IS_A17MATCH (n1:node), (n2:node) where n1.id='22' and n2.id='17' create n1-[:IS_A]->n2;
23
22Social networksUseCasecreate (n:node:UseCase{id:'22', name:'Social networks', type:'UseCase', comments:''});23IS_A17MATCH (n1:node), (n2:node) where n1.id='23' and n2.id='17' create n1-[:IS_A]->n2;
24
23Access and IdentityUseCasecreate (n:node:UseCase{id:'23', name:'Access and Identity', type:'UseCase', comments:''});24IS_A17MATCH (n1:node), (n2:node) where n1.id='24' and n2.id='17' create n1-[:IS_A]->n2;
25
24Master Data ManagementUseCasecreate (n:node:UseCase{id:'24', name:'Master Data Management', type:'UseCase', comments:''});1WORKS_FOR25MATCH (n1:node), (n2:node) where n1.id='1' and n2.id='25' create n1-[:WORKS_FOR]->n2;
26
25IndustriesCategorycreate (n:node:Category{id:'25', name:'Industries', type:'Category', comments:''});26IS_A25MATCH (n1:node), (n2:node) where n1.id='26' and n2.id='25' create n1-[:IS_A]->n2;
27
26TelecomIndustrycreate (n:node:Industry{id:'26', name:'Telecom', type:'Industry', comments:''});27IS_A25MATCH (n1:node), (n2:node) where n1.id='27' and n2.id='25' create n1-[:IS_A]->n2;
28
27Financial ServicesIndustrycreate (n:node:Industry{id:'27', name:'Financial Services', type:'Industry', comments:''});28IS_A25MATCH (n1:node), (n2:node) where n1.id='28' and n2.id='25' create n1-[:IS_A]->n2;
29
28Media and EntertainmentIndustrycreate (n:node:Industry{id:'28', name:'Media and Entertainment', type:'Industry', comments:''});29IS_A25MATCH (n1:node), (n2:node) where n1.id='29' and n2.id='25' create n1-[:IS_A]->n2;
30
29Biotech, Pharma, Life SciencesIndustrycreate (n:node:Industry{id:'29', name:'Biotech, Pharma, Life Sciences', type:'Industry', comments:''});30IS_A25MATCH (n1:node), (n2:node) where n1.id='30' and n2.id='25' create n1-[:IS_A]->n2;
31
30GamingIndustrycreate (n:node:Industry{id:'30', name:'Gaming', type:'Industry', comments:''});1OFFERS31MATCH (n1:node), (n2:node) where n1.id='1' and n2.id='31' create n1-[:OFFERS]->n2;
32
31BenefitsCategorycreate (n:node:Category{id:'31', name:'Benefits', type:'Category', comments:''});32IS_A31MATCH (n1:node), (n2:node) where n1.id='32' and n2.id='31' create n1-[:IS_A]->n2;
33
32AgilityBenefitcreate (n:node:Benefit{id:'32', name:'Agility', type:'Benefit', comments:''});33IS_A31MATCH (n1:node), (n2:node) where n1.id='33' and n2.id='31' create n1-[:IS_A]->n2;
34
33AbilityBenefitcreate (n:node:Benefit{id:'33', name:'Ability', type:'Benefit', comments:''});34IS_A31MATCH (n1:node), (n2:node) where n1.id='34' and n2.id='31' create n1-[:IS_A]->n2;
35
34CostBenefitcreate (n:node:Benefit{id:'34', name:'Cost', type:'Benefit', comments:''});35IS_A31MATCH (n1:node), (n2:node) where n1.id='35' and n2.id='31' create n1-[:IS_A]->n2;
36
35PerformanceBenefitcreate (n:node:Benefit{id:'35', name:'Performance', type:'Benefit', comments:''});1BENEFITS36MATCH (n1:node), (n2:node) where n1.id='1' and n2.id='36' create n1-[:BENEFITS]->n2;
37
36AudiencesCategorycreate (n:node:Category{id:'36', name:'Audiences', type:'Category', comments:''});37IS_A36MATCH (n1:node), (n2:node) where n1.id='37' and n2.id='36' create n1-[:IS_A]->n2;
38
37DevelopersAudiencecreate (n:node:Audience{id:'37', name:'Developers', type:'Audience', comments:''});38IS_A36MATCH (n1:node), (n2:node) where n1.id='38' and n2.id='36' create n1-[:IS_A]->n2;
39
38ArchitectsAudiencecreate (n:node:Audience{id:'38', name:'Architects', type:'Audience', comments:''});39IS_A36MATCH (n1:node), (n2:node) where n1.id='39' and n2.id='36' create n1-[:IS_A]->n2;
40
39Project ManagersAudiencecreate (n:node:Audience{id:'39', name:'Project Managers', type:'Audience', comments:''});40IS_A36MATCH (n1:node), (n2:node) where n1.id='40' and n2.id='36' create n1-[:IS_A]->n2;
41
40CIOAudiencecreate (n:node:Audience{id:'40', name:'CIO', type:'Audience', comments:''});41IS_A36MATCH (n1:node), (n2:node) where n1.id='41' and n2.id='36' create n1-[:IS_A]->n2;
42
41Business ManagersAudiencecreate (n:node:Audience{id:'41', name:'Business Managers', type:'Audience', comments:''});42IS_A36MATCH (n1:node), (n2:node) where n1.id='42' and n2.id='36' create n1-[:IS_A]->n2;
43
42General PublicAudiencecreate (n:node:Audience{id:'42', name:'General Public', type:'Audience', comments:''});36TWO_MINUTE_EXPLANATIONS43MATCH (n1:node), (n2:node) where n1.id='36' and n2.id='43' create n1-[:TWO_MINUTE_EXPLANATIONS]->n2;
44
43Elevator PitchesCategorycreate (n:node:Category{id:'43', name:'Elevator Pitches', type:'Category', comments:''});44IS_A43MATCH (n1:node), (n2:node) where n1.id='44' and n2.id='43' create n1-[:IS_A]->n2;
45
44DevelopersElevatorPitchA smart NOSQL database that uses a completely different datamodel (a property graph) to store data. Normalisation all of a sudden becomes cheap, and join-style operations go lightning fast. Use it for complex queries, recursive lookups and/or pathfinding operations - and you will never look back. And it is a fully transactional, ACID database that will take excellent care of your data, and will scale nicely as your application grows.create (n:node:ElevatorPitch{id:'44', name:'Developers', type:'ElevatorPitch', comments:'A smart NOSQL database that uses a completely different datamodel (a property graph) to store data. Normalisation all of a sudden becomes cheap, and join-style operations go lightning fast. Use it for complex queries, recursive lookups and/or pathfinding operations - and you will never look back. And it is a fully transactional, ACID database that will take excellent care of your data, and will scale nicely as your application grows.'});45IS_A43MATCH (n1:node), (n2:node) where n1.id='45' and n2.id='43' create n1-[:IS_A]->n2;
46
45ArchitectsElevatorPitchNetworked problems benefit from network-centric solutions.That is why you should be using a graph database for some of the business solutions that you are building: many datasets are densely connected, and both your technical staff (developers/sysadmins) and your business users will love the simplicity and elegance with which neo4j enables using these. Whether it is the simple Cypher query language or the intuitive graph visualisations, they all contribute to a better architectural fit for the project.create (n:node:ElevatorPitch{id:'45', name:'Architects', type:'ElevatorPitch', comments:'Networked problems benefit from network-centric solutions.That is why you should be using a graph database for some of the business solutions that you are building: many datasets are densely connected, and both your technical staff (developers/sysadmins) and your business users will love the simplicity and elegance with which neo4j enables using these. Whether it is the simple Cypher query language or the intuitive graph visualisations, they all contribute to a better architectural fit for the project.'});46IS_A43MATCH (n1:node), (n2:node) where n1.id='46' and n2.id='43' create n1-[:IS_A]->n2;
47
46Project ManagersElevatorPitchDelivering an on-time, in-budget project means that you have to use the right tool for the job. That is why projects that are dealing with networked datasets benefit from network-centric solutions: they allow the technical staff (developers/sysadmins) to be more productive, and provide business users with a simpler, more responsive and elegant result. Next time you are doing projects involving recommendations, master data management, impact analysis or any of the other use cases, ask why people are not using neo4j - if they have not already done so themselves.create (n:node:ElevatorPitch{id:'46', name:'Project Managers', type:'ElevatorPitch', comments:'Delivering an on-time, in-budget project means that you have to use the right tool for the job. That is why projects that are dealing with networked datasets benefit from network-centric solutions: they allow the technical staff (developers/sysadmins) to be more productive, and provide business users with a simpler, more responsive and elegant result. Next time you are doing projects involving recommendations, master data management, impact analysis or any of the other use cases, ask why people are not using neo4j - if they have not already done so themselves.'});47IS_A43MATCH (n1:node), (n2:node) where n1.id='47' and n2.id='43' create n1-[:IS_A]->n2;
48
47CIOElevatorPitchNeo4j offers a smart new database architecture that complements existing relational systems for specific workloads: graph (or "network centric") queries. The graph database allows you to run these complex queries more efficiently, with less hardware and less time and effort spent on implementations. Overall, the Neo4j graph database will contribute to making the IT organisation more agile, cost-effective and business focused.create (n:node:ElevatorPitch{id:'47', name:'CIO', type:'ElevatorPitch', comments:'Neo4j offers a smart new database architecture that complements existing relational systems for specific workloads: graph (or "network centric") queries. The graph database allows you to run these complex queries more efficiently, with less hardware and less time and effort spent on implementations. Overall, the Neo4j graph database will contribute to making the IT organisation more agile, cost-effective and business focused.'});48IS_A43MATCH (n1:node), (n2:node) where n1.id='48' and n2.id='43' create n1-[:IS_A]->n2;
49
48Business ManagersElevatorPitchEvery IT system needs a place to store their data. But many systems have been using the wrong kind of technology to do so - and this has led to poor a poor business user experience. Whether it is a slow system, a late project, or a budget that has been overrun, many of these issues can just be avoided by using the right tool for the job. Graph Databases offer your IT users a better tool for specific, network-oriented problems. Do not let the default be yet another RDBMS - ask why not consider an alternative that is better fit for purpose.create (n:node:ElevatorPitch{id:'48', name:'Business Managers', type:'ElevatorPitch', comments:'Every IT system needs a place to store their data. But many systems have been using the wrong kind of technology to do so - and this has led to poor a poor business user experience. Whether it is a slow system, a late project, or a budget that has been overrun, many of these issues can just be avoided by using the right tool for the job. Graph Databases offer your IT users a better tool for specific, network-oriented problems. Do not let the default be yet another RDBMS - ask why not consider an alternative that is better fit for purpose.'});49IS_A43MATCH (n1:node), (n2:node) where n1.id='49' and n2.id='43' create n1-[:IS_A]->n2;
50
49General PublicElevatorPitchComputers need data - and that data needs to be stored and managed somewhere. Typically, that is what databases do. Your bank, your supermarket, your gas station - they all store data about the things you buy from them in databases. But not all data is the same - there are different types of data (files, pictures, transactions, documents, ...) and some data is very interesting to understand. That is why a specific type of database - we call it a graph database, after the math terminology that supports it - was created to understand patterns, relationships and connections between data better. Banks use it to detect fraud, supermarkets to recommend other products, and facebook uses it to suggest new friends. It is way cool.create (n:node:ElevatorPitch{id:'49', name:'General Public', type:'ElevatorPitch', comments:'Computers need data - and that data needs to be stored and managed somewhere. Typically, that is what databases do. Your bank, your supermarket, your gas station - they all store data about the things you buy from them in databases. But not all data is the same - there are different types of data (files, pictures, transactions, documents, ...) and some data is very interesting to understand. That is why a specific type of database - we call it a graph database, after the math terminology that supports it - was created to understand patterns, relationships and connections between data better. Banks use it to detect fraud, supermarkets to recommend other products, and facebook uses it to suggest new friends. It is way cool.'});37TWO_MINUTE_EXPLANATIONS44MATCH (n1:node), (n2:node) where n1.id='37' and n2.id='44' create n1-[:TWO_MINUTE_EXPLANATIONS]->n2;
51
50Technical DetailsCategorycreate (n:node:Category{id:'50', name:'Technical Details', type:'Category', comments:''});38TWO_MINUTE_EXPLANATIONS45MATCH (n1:node), (n2:node) where n1.id='38' and n2.id='45' create n1-[:TWO_MINUTE_EXPLANATIONS]->n2;
52
51CypherTechnicalDetailDeclarative, Pattern Matching query languages that allows you to express graphs in ASCII-art, allowing you to formulate Ad-Hoc queries - just like you expect a database to behave.create (n:node:TechnicalDetail{id:'51', name:'Cypher', type:'TechnicalDetail', comments:'Declarative, Pattern Matching query languages that allows you to express graphs in ASCII-art, allowing you to formulate Ad-Hoc queries - just like you expect a database to behave.'});39TWO_MINUTE_EXPLANATIONS46MATCH (n1:node), (n2:node) where n1.id='39' and n2.id='46' create n1-[:TWO_MINUTE_EXPLANATIONS]->n2;
53
52ScalableTechnicalDetailExcellent scalability, comparable to RDBMSes. Master/Slave replication clusters for horizontal scalingcreate (n:node:TechnicalDetail{id:'52', name:'Scalable', type:'TechnicalDetail', comments:'Excellent scalability, comparable to RDBMSes. Master/Slave replication clusters for horizontal scaling'});40TWO_MINUTE_EXPLANATIONS47MATCH (n1:node), (n2:node) where n1.id='40' and n2.id='47' create n1-[:TWO_MINUTE_EXPLANATIONS]->n2;
54
53ACIDTechnicalDetailMaster is immediately consistent, slaves are eventually consistentcreate (n:node:TechnicalDetail{id:'53', name:'ACID', type:'TechnicalDetail', comments:'Master is immediately consistent, slaves are eventually consistent'});41TWO_MINUTE_EXPLANATIONS48MATCH (n1:node), (n2:node) where n1.id='41' and n2.id='48' create n1-[:TWO_MINUTE_EXPLANATIONS]->n2;
55
54Multi-purposeTechnicalDetailMany graph systems are specific purpose (eg. social networking, genome analysis, ...) - but neo4j is designed to be generic so that it can be used for many purposes...create (n:node:TechnicalDetail{id:'54', name:'Multi-purpose', type:'TechnicalDetail', comments:'Many graph systems are specific purpose (eg. social networking, genome analysis, ...) - but neo4j is designed to be generic so that it can be used for many purposes...'});42TWO_MINUTE_EXPLANATIONS49MATCH (n1:node), (n2:node) where n1.id='42' and n2.id='49' create n1-[:TWO_MINUTE_EXPLANATIONS]->n2;
56
55Open sourceTechnicalDetailAll versions & editions of neo4j are open source - because we love it. The license (GPL or AGPL) varies - so you may actually be better of with a commercial license.create (n:node:TechnicalDetail{id:'55', name:'Open source', type:'TechnicalDetail', comments:'All versions & editions of neo4j are open source - because we love it. The license (GPL or AGPL) varies - so you may actually be better of with a commercial license.'});1HAS_SOME50MATCH (n1:node), (n2:node) where n1.id='1' and n2.id='50' create n1-[:HAS_SOME]->n2;
57
56Neo TechnologyCategorycreate (n:node:Category{id:'56', name:'Neo Technology', type:'Category', comments:''});51IS_A50MATCH (n1:node), (n2:node) where n1.id='51' and n2.id='50' create n1-[:IS_A]->n2;
58
57Commercial LicensingOfferingcreate (n:node:Offering{id:'57', name:'Commercial Licensing', type:'Offering', comments:''});52IS_A50MATCH (n1:node), (n2:node) where n1.id='52' and n2.id='50' create n1-[:IS_A]->n2;
59
58Enterprise SupportOfferingcreate (n:node:Offering{id:'58', name:'Enterprise Support', type:'Offering', comments:''});53IS_A50MATCH (n1:node), (n2:node) where n1.id='53' and n2.id='50' create n1-[:IS_A]->n2;
60
59Product ConsultingOfferingcreate (n:node:Offering{id:'59', name:'Product Consulting', type:'Offering', comments:''});54IS_A50MATCH (n1:node), (n2:node) where n1.id='54' and n2.id='50' create n1-[:IS_A]->n2;
61
60www.neo4j.orgCategorycreate (n:node:Category{id:'60', name:'www.neo4j.org', type:'Category', comments:''});55IS_A50MATCH (n1:node), (n2:node) where n1.id='55' and n2.id='50' create n1-[:IS_A]->n2;
62
1CREATED_AND_MAINTAINED_BY56MATCH (n1:node), (n2:node) where n1.id='1' and n2.id='56' create n1-[:CREATED_AND_MAINTAINED_BY]->n2;
63
56OFFERS57MATCH (n1:node), (n2:node) where n1.id='56' and n2.id='57' create n1-[:OFFERS]->n2;
64
DON'T FORGET TO CREATE THE INDEX:create index on :node(id);56OFFERS58MATCH (n1:node), (n2:node) where n1.id='56' and n2.id='58' create n1-[:OFFERS]->n2;
65
56OFFERS59MATCH (n1:node), (n2:node) where n1.id='56' and n2.id='59' create n1-[:OFFERS]->n2;
66
1HAS_WEBSITE60MATCH (n1:node), (n2:node) where n1.id='1' and n2.id='60' create n1-[:HAS_WEBSITE]->n2;
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...