Podczas codziennej pracy każdy z nas korzysta z różnych baz danych, Każda baza ma zachowania typowe dla siebie. Firestore to nierelacyjna baza od Google, która posiada wiele nietypowych funkcjonalności, wiele ciekawych rozwiązań. W tej prezentacji dowiemy się o paru fajnych zastosowań w Firestore i na co warto uważać przy implementacji tego rozwiązania.

1. Firestore - the Silicon
Valley giant's fiery
database
Mikołaj Glistak

2. Mikołaj Glistak
Node.js Developer @ TSH
Marvel, videos games, cycling.
mikolaj.glistak@tsh.io

3. Quick start with
firestore
2 3
Agenda
1
Live coding Summary

4. What is
firestore?

5. Key capabilities
● Flexibility
● Expressive querying
● Realtime updates
● Offline support
● Designed to scale

7. Frontend connects to database
directly

8. Realtime database

9. out-of-the-box cache

10. Serverless Database

11. Pay as you go

13. Live coding

14. Firestore can be use in a lot of different ways:
● Live chat (Frontend)
● Normal noSQL database (Backend)
● Custom notifications in system (Frontend)
● Easy realtime games (Mobile)
Examples of use

15. Pros & cons
+ Easy prototyping
+ Connected to frontend

16. Pros & cons
- Not easy to optimize
- Connected to frontend
+ Easy prototyping
+ Connected to frontend

17. Pros & cons
- Not easy to optimize
- Connected to frontend
+ Easy prototyping
+ Connected to frontend
+ Firebase Auth support
+ Cool client & server libraries

18. Pros & cons
- Not easy to optimize
- Connected to frontend
- Needs cloud function to backup
- One database per project
+ Easy prototyping
+ Connected to frontend
+ Firebase Auth support
+ Cool client & server libraries

19. Pros & cons
- Not easy to optimize
- Connected to frontend
- Needs cloud function to backup
- One database per project
+ Easy prototyping
+ Connected to frontend
+ Firebase Auth support
+ Cool client & server libraries
+ Cloud functions support (events)
+ Cool usage charts

20. Pros & cons
- Not easy to optimize
- Connected to frontend
- Needs cloud function to backup
- One database per project
- Costs per reads / writes / deletes
- Hidden backup costs
- No details on usage charts
+ Easy prototyping
+ Connected to frontend
+ Firebase Auth support
+ Cool client & server libraries
+ Cloud functions support (events)
+ Cool usage charts

21. Pros & cons
- Not easy to optimize
- Connected to frontend
- Needs cloud function to backup
- One database per project
- Costs per reads / writes / deletes
- Hidden backup costs
- No details on usage charts
- Limited operators
- Indexes (In advanced queries)
+ Easy prototyping
+ Connected to frontend
+ Firebase Auth support
+ Cool client & server libraries
+ Cloud functions support (events)
+ Cool usage charts
+ Automatic indexes
+ Fast

22. ● https://firebase.google.com/docs/firestore
● https://www.youtube.com/watch?v=v_hR4K4auoQ&list=PLl-K7zZEsYLluG5MCVEzXAQ7ACZBCuZgZ
Useful links

23. Dziękuje za uwagę

24. Q&A

25. Dziękuje za uwagę v2