Persisting Data: Databases

January 21, 2017
About Me
Organizer of CODE Norman
twitter: @bchirgwin
linkedin: linkedin.com/in/bchirgwin
Senior Software Engineer at Iteris


Workshop Expectations
- Pragmatic Approach
- Get out of it what you put into it
- Workshop
- Homework
- Available for additional help
- Most Thursday evenings
- Other times on request
Workshops
Git & GitHub - September 17NodeJS & Javascript - October 8NodeJS & Javascript Part II November 19- Persisting Data: Databases - January 21
- AngularJS Front-end Development - February
- End to End Testing - March
- Review open source projects - April
- Code Norman Open Source Project Kickoff - May
News
- Node Interactive
- javscript30.com
Don't be afraid to fail
Experiment
- Wright Brothers
- Thomas Edison
- Albert Einstein



Practice, Practice, Practice
- Programming Katas
- Short exercise of about 30 minutes
- Repeat with several ideas
- CodeKata
- Project Euler
- CodeWars
- CodeKatas.org
Databases
-
NoSQL
- MongoDB, Redis, Firebase, CouchDB, Riak
- Relational
- SQL Server, MySQL, Postgress, Oracle
- OODB (Object-Oriented Database)
- db4objects, Versant Object Database
- Graph Database
- Neo4j
No SQL
- Not Only SQL
- Key, Value
- Document Based
- JSON - BSON
Relational
- Tables, fields, datatype
- Rows, Columns
- SELECT, INSERT, UPDATE, DELETE
- JOINS
- Agreggate
- Min, Max, Sum, Avg, Count
OODB
- Object, Class of Objects
- Data and Methods
- Object Extensibility
Graph DB
- Nodes, Edges, Properties
- Connections between data
- Brian -> married -> TerriĀ
- Brian -> brother -> Mark
Firebase
- Features
- Analytics
- Cloud (google)
- No SQL DB
- Realtime
- Offline
- Accessible directly from mobile or web

Firebase

Firebase
Firebase
- Not Only SQL
Raffle
- JetBrains IDE

WebStorm
PhpStorm
PyCharm
RubyMine
AppCode
CLion
DataGrip
Rider
IntelliJ IDEA
Persisting Data: Databases
By Brian Chirgwin
Persisting Data: Databases
- 887