Enterprise graph applications
•
1 gostou•935 visualizações
The opportunities to enhance today's enterprise applications with graph database technologies are out there - and now there is a way to implement graph applications quickly with the xnlogic framework.
Recomendados
Recomendados
Mais conteúdo relacionado
Destaque
Destaque (19)
Semelhante a Enterprise graph applications
Semelhante a Enterprise graph applications (20)
Último
Último (20)
Enterprise graph applications
- 1. Graph
- 2. Applications
- 3. for
- 4. the
- 5. Enterprise,
- 6. FAST David
- 7. Colebatch
- 14. Wednesday, 6 November, 13
- 15. Who
- 16. Are
- 17. We? • Toronto-based Graph Database services company • Partner with Neo Technology • Organizers of GraphTO GraphTO • Authors of the popular Pacer gem, an extensible graph traversal library David
- 18. Colebatch
- 21. dc@xnlogic.com
- 26. Enterprise
- 27. Application
- 28. Examples David
- 29. Colebatch
- 32. dc@xnlogic.com
- 37. CRM P ERccounting A MRP PLM MDM AMDB CMDB Wednesday, 6 November, 13 Inventory Excel
- 38. MRP PLM MDM CRM P ERccounting A AMDB CMDB Wednesday, 6 November, 13 Inventory Excel
- 39. The
- 40. Zone
- 41. of
- 42. SQL
- 43. Adequacy SQL database Performance Requirement of application Data complexity Wednesday, 6 November, 13
- 44. The
- 45. Zone
- 46. of
- 47. SQL
- 48. Adequacy SQL database Performance Requirement of application Data complexity Wednesday, 6 November, 13
- 49. The
- 50. Zone
- 51. of
- 52. SQL
- 53. Adequacy SQL database Requirement of application Performance Salary List ERP CRM Data complexity Wednesday, 6 November, 13
- 54. The
- 55. Zone
- 56. of
- 57. SQL
- 58. Adequacy Social SQL database Requirement of application Geo Performance Salary List Network / Cloud Management ERP MDM CRM Data complexity Wednesday, 6 November, 13
- 59. The
- 60. Zone
- 61. of
- 62. SQL
- 63. Adequacy Social SQL database Requirement of application Geo Performance Salary List Network / Cloud Management ERP MDM CRM Data complexity Wednesday, 6 November, 13
- 64. Configuration
- 66. Configuration
- 68. Configuration
- 70. Configuration
- 72. Enterprise
- 73. Application
- 74. #fails David
- 75. Colebatch
- 78. dc@xnlogic.com
- 83. Enterprise
- 84. Application
- 85. #fails Often CRUD Only • • One screen for each record type UI maps to table structure • ...or rather, is constrained by the table structure David
- 86. Colebatch
- 89. dc@xnlogic.com
- 94. Enterprise
- 95. Application
- 96. #fails Relationships to one-degree • • • “This thing is related to that thing” Slow to traverse relationships Inhibits discovery by serendipity David
- 97. Colebatch
- 100. dc@xnlogic.com
- 105. Configuration
- 107. So
- 108. what’s
- 109. the
- 110. solution? David
- 111. Colebatch
- 114. dc@xnlogic.com
- 119. David
- 120. Colebatch
- 123. dc@xnlogic.com
- 128. Manager/Client:
- 130. “But
- 131. it’s
- 132. new...” • Only 32% of software projects considered successful • • 44% are considered “challenged” 24% never get completed • 50% for project $1mil David
- 133. Colebatch
- 136. dc@xnlogic.com
- 141. Gather Requirements Define Data Model Define Security Constraints Iterate! Develop Business Logic Implement API Implement UI Test Training Acceptance. Go/No Go David
- 142. Colebatch
- 145. dc@xnlogic.com
- 150. Gather Requirements Define Data Model Define Security Constraints Iterate! Develop Business Logic Implement API Implement UI Test Training Acceptance. Go/No Go David
- 151. Colebatch
- 154. dc@xnlogic.com
- 159. Gather Requirements Define Data Model Define Security Constraints Iterate! Develop Business Logic Implement API Implement UI Test Training Acceptance. Go/No Go David
- 160. Colebatch
- 163. dc@xnlogic.com
- 168. So
- 169. what’s
- 170. the
- 171. solution? David
- 172. Colebatch
- 175. dc@xnlogic.com
- 180. David
- 181. Colebatch
- 184. dc@xnlogic.com
- 189. David
- 190. Colebatch
- 193. dc@xnlogic.com
- 198. The
- 199. xnlogic
- 200. framework • • • RESTful API driven application framework Declare your model, define your business logic Framework then produces a domain-specific JSON and xml api David
- 201. Colebatch
- 204. dc@xnlogic.com
- 209. Advanced
- 210. Features • • • • Composable models vs Inheritance Fine-grained security History Graph for temporal queries Multi-tenant: • • One framework, multiple applications Customer segregation David
- 211. Colebatch
- 214. dc@xnlogic.com
- 219. Composable
- 221. Colebatch
- 224. dc@xnlogic.com
- 229. Composable
- 231. Colebatch
- 234. dc@xnlogic.com
- 239. • Composition promotes code reuse (DRY) • Here, color shows the delta between a Person and a Business model (Hypothetical) • User permissions are tied to the “Part” • Parts define properties, relationships, actions and traversals David
- 240. Colebatch
- 243. dc@xnlogic.com
- 248. Simple
- 249. Part
- 250. Definitions module YourApplication module ContactDetails pacer_vertex property :address, type: :text property :lat, type: :numeric property :lon, type: :numeric end end module YourApplication module HasEmployer pacer_vertex to_one :employer end end David
- 251. Colebatch
- 254. dc@xnlogic.com
- 259. RESTful
- 260. API David
- 261. Colebatch
- 264. dc@xnlogic.com
- 269. Self
- 270. Describing,
- 271. Domain
- 272. Specific
- 273. API GET /is [ 'contact_details', 'has_accounts', 'has_employer', 'has_friends', 'corporate_details', 'jurisdiction'] GET /model [ 'person', 'business'] Parts The building blocks of your application Models Composed of Parts David
- 274. Colebatch
- 277. dc@xnlogic.com
- 282. Metadata
- 283. Driven GET /is/contact_details/metadata { update_access: true, create_access: true, delete_access: true, parts: [ 'record', 'contact_details' ], descriptive_parts: [ 'contact_details' ], properties: { name: { name: 'name', label: 'Name', type: 'text', unit: null, default: null, validations: { allow_blank: true }, part: 'record', index: true }, ... Includes: 1)Current-user’s access rights 2)Property definitions 3)Relationship definitions 4)Validation rules 5)Actions/Jobs 6)Queries/Traversals David
- 284. Colebatch
- 287. dc@xnlogic.com
- 292. Built-in
- 294. Colebatch
- 297. dc@xnlogic.com
- 302. URLs
- 303. map
- 304. to
- 305. Traversals GET /model/person/rel/employer [ { meta: { xnid: '/model/business/2028', model_name: 'business', rendered: [ 'record', 'contact_details', ‘has_accounts’, ‘corporate_details’], format: 'partial' }, id: 2028, name: 'Acme Bank', rel: {}, description: 'A very large FI.', created_at: ‘2012-10-02 12:07:31, updated_at: null, address: '88 Fairtrade Blvd., NYC.', lat: '40.755622', lon: '-73.977221', company_url: 'http://www.acme.com', display_name: 'FI - US - ACME' ...}, Returns: 1)All employers of all people David
- 306. Colebatch
- 309. dc@xnlogic.com
- 314. Limitless
- 316. Colebatch
- 319. dc@xnlogic.com
- 324. Limitless
- 326. Colebatch
- 329. dc@xnlogic.com
- 334. Limitless
- 336. Colebatch
- 339. dc@xnlogic.com
- 344. Limitless
- 346. Colebatch
- 349. dc@xnlogic.com
- 354. Limitless
- 356. Colebatch
- 359. dc@xnlogic.com
- 364. So
- 365. What? David
- 366. Colebatch
- 369. dc@xnlogic.com
- 374. So
- 375. What? • • Eliminate “infrastructure” development cycles Bootstrap HTML5 User Interface David
- 376. Colebatch
- 379. dc@xnlogic.com
- 384. So
- 385. What? • • Eliminate “infrastructure” development cycles • Shorter Time To Market Bootstrap HTML5 User Interface David
- 386. Colebatch
- 389. dc@xnlogic.com
- 394. So
- 395. What? • • Eliminate “infrastructure” development cycles • • Shorter Time To Market Bootstrap HTML5 User Interface Software Project Risk Reduction David
- 396. Colebatch
- 399. dc@xnlogic.com
- 404. So
- 405. What? • • Eliminate “infrastructure” development cycles • • • Shorter Time To Market Bootstrap HTML5 User Interface Software Project Risk Reduction Powered by Graph™ - Answer the hard Q’s David
- 406. Colebatch
- 409. dc@xnlogic.com
- 414. Quick
- 415. Example David
- 416. Colebatch
- 419. dc@xnlogic.com
- 424. Questions? David
- 425. Colebatch
- 428. dc@xnlogic.com
- 433. Graph
- 434. Applications
- 435. for
- 436. the
- 437. Enterprise,
- 438. FAST David
- 439. Colebatch
- 446. Wednesday, 6 November, 13
- 448. Colebatch
- 451. dc@xnlogic.com