Building the Neo4j Sandbox: AWS, ECS, Docker, Python, Neo4j, ++
•
3 likes•1,431 views
Video: https://www.youtube.com/watch?v=2XbNhAJ9wh0 Try Neo4j Sandbox today: https://neo4j.com/sandbox-v2/ The Neo4j Sandbox is an environment where anyone can get their own instance of Neo4j up and running in seconds, with tutorials and datasets related to their usecase. Since Ryan wanted people to have the freedom to interact with Neo4j with full privileges, he decided to use Docker to provide container-level isolation for the Sandbox. This session will talk about some of the design decisions made and how the architecture was achieved using Docker, EC2 Container Service, Auth0, EC2, Elastic Load Balancers, EC2 AutoScaling Group, AWS Lambda functions, Python, S3, IAM, CloudWatch, SES, FullContact, MaxMind and more. Ryan will also discuss future features and get feedback from users during Q&A.
![(Sandbox)-[:TEACHES]->(GraphDBs)
powered by:](https://image.slidesharecdn.com/sandbox-20170329-170330224526/85/Building-the-Neo4j-Sandbox-AWS-ECS-Docker-Python-Neo4j-1-320.jpg)
![(Sandbox)-[:TEACHES]->(GraphDBs)
Ryan Boyd
@ryguyrg
ryan@neo4j.com](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
Viewers also liked
Viewers also liked (18)
Similar to Building the Neo4j Sandbox: AWS, ECS, Docker, Python, Neo4j, ++
Similar to Building the Neo4j Sandbox: AWS, ECS, Docker, Python, Neo4j, ++ (20)
Recently uploaded
Recently uploaded (20)
Building the Neo4j Sandbox: AWS, ECS, Docker, Python, Neo4j, ++
- 3. @ryguyrg
- 4. Developed Web Apps + APIs for 5 years
- 5. Led Google Developer Relations teams for 8 years
- 6. Wrote O’Reilly book on OAuth 2.0
- 8. WEB! Led DevRel teams for Google Developed web apps + APIs Wrote book on OAuth
- 9. HUH!?!
- 11. “DOWNLOAD” IS A BAD WORD.
- 13. BUT IS IT ACTUALLY BAD?
- 19. ?
- 24. Goals
- 29. Guided Experience *even if better than product
- 30. Fast Time to First Line of Code
- 33. CEO Wants everyone to use the Product
- 34. Marketing Wants to be able to reach users
- 36. Developer Relations Wants to be able to reach users
- 38. $
- 39. $ Fixed Costs Machines ready to serve users Variable Costs More machines with demand
- 40. Low Data Quality
- 41. Low Data Quality Not asking for name, company, country, state, biz email But OAuth2-provided and derived data may be better quality for many fields
- 44. Operational Nightmares Server Maintenance and Security patches, outages, memory/CPU management Scaling Challenges spikes in load, drops in load
- 47. Backend
- 48. EC2 Container Service (ECS) Backend
- 49. AWS Lambda - Serverless Backend
- 50. Backend
- 51. Backend
- 52. Backend Frontend
- 54. Backend Frontend JWT { "email": "ryan.boyd@neotechnology.com", "email_verified": true, "iss": "https://neo4j-sync.auth0.com/", "sub": "google-oauth2|106247252857730863431", "aud": "DxhmiF8TCeznI7Xoi08UyYScLGZnk4ke", "exp": 1490919936, "iat": 1490847936, "nonce": "34" }
- 55. Frontend
- 56. Frontend
- 57. Are We Done with the Tech Stack Yet?!?
- 58. Data Providers { "email": "ryan@ryguy.com", "email_verified": true, "name": "Ryan Boyd", "given_name": "Ryan", "family_name": "Boyd", "picture": "https://lh4.googleusercontent.com/-BET-bMzn99g/AAAAAAAAAAI/AAAAAAAAFEc/h2y8 "gender": "male", "locale": "en", "updated_at": "2017-03-29T23:22:09.262Z", "id": "google-oauth2|113487456102835830811" }
- 59. Data Providers
- 60. Data Providers
- 61. Data Providers
- 62. Data Providers
- 63. Data Providers "organizations": [ { "isPrimary": true, "name": "Neo4j", "startDate": "2015", "title": "Head of Developer Relations, NA", "current": true }, "socialProfiles": [ { "type": "facebook", "typeId": "facebook", "typeName": "Facebook", "url": "https://www.facebook.com/rboyd" }, { "followers": 500, "following": 500, "type": "linkedin", "typeId": "linkedin", "typeName": "LinkedIn", "url": "https://www.linkedin.com/in/ryguyrg", "username": "ryguyrg",
- 64. Data Providers { "city": { "geoname_id": 5331920, "names": { "en": "Burlingame", } }, "continent": { "code": "NA", "geoname_id": 6255149, "names": { "en": "North America", } }, "country": { "iso_code": "US", "geoname_id": 6252001, "names": { "en": "United States", }
- 66. Social Sign-In Launched with: Twitter, GitHub, Google Added after launch: LinkedIn
- 67. Code Snippets
- 70. NGINX Proxy for SSL and those annoying corporate firewalls Neo4j Browser: https://10-0-1-237-32825.neo4jsandbox.com/ Direct Neo4j HTTP: http://54.197.91.106:32825/browser/
- 71. Single Sign On to Neo4j Browser
- 72. E-mail Nurturing
- 73. Architecture
- 76. QUOTAS :-(
- 79. CSS HELL
- 82. More Usecases Data JournalismBYO API Data Enterprise Usecases
- 83. From You Too!
- 85. Sharing with Colleagues and Friends
- 86. Q & A