Download as PDF, PPTX
More Related Content
Similar to Firebase in action 2021
Firebase in action 2021
- 1. Firebase In Action Tai Duong Headof Development @imbaggaarm Learn, practice and master it! Anh Tuan Development @AnhTuan4198 Hoang Viet Development @HoangViet144
- 2. What is Firebase? Isit something that hot?
- 9.
- 10. Firebase In Action Learn,practice and master it!
- 11. Outline . Introduction ✔ .Why should we use Firebase? . Firebase Authentication . Firebase Realtime Database . Firebase Cloud Functions . Firebase Cloud Storage . Relax Time . Closing
- 12. Why should weuse Firebase? A little bit further about reasons for using Firebase.
- 14. Cheap Is it reallycheap? - 2 plans: Spark and Blaze (3 plans in the past) - Free quota: - Realtime DB: 10 GB read bandwidth (5 M message objects) - Firestore: 20K writes/day, 50K reads/day, 20K deletes/day - Storage: 5 GB (300 KB ~ 16667 images) - Cloud Functions: 2 M invocations - ... See more here: Firebase pricing
- 15. Fast How fast isit? - It is a PaaS - Faster development - Less resource required - Suitable for new projects, small teams
- 16. Good Is it goodenough? - A part of Google Cloud Platform - Host by one of the biggest CDN provider in the world - Developed by Google Engineers - Scales automatically, global edge cache, 99.999% uptime, robust security,...
- 17. Firebase Authentication Learn how touse Firebase Authentication as a professional developer.
- 18. What is it? Identity-as-a-Service -Supports email/password, popular IDPs - Phone number and custom auth, anonymous auth - Leverages industry standards like OAuth 2.0 and OpenID Connect - Provides backend services, easy-to-use SDKs, and ready-made UI libraries
- 20. How does itwork? Behind the screen - Simple flow using Firebase services only - Flow using our main auth system and Firebase services - Flow using Firebase auth system and our resource back-end
- 21. Proprietary + Confidential Simpleflow using Firebase services only Firebase client SDK Email/Password or phone, 3rd IDPs Firebase pre-built UI Build it ourselves 1. Call Login API 2. Send login request Firebase Authentication 3. Repond tokens 4. Save tokens in the device 5. Communicate with Firebase Platform using tokens
- 22. Proprietary + Confidential Flowusing our main auth system and Firebase services Email/Password 1. Send login request Our authentication server Firebase Admin SDK Realtime database with Security Rules Firebase client SDK 2. Call generate token API 3. Respond a custom FB access token (JWT) Our resource server 4. Respond tokens: - Access token - Refresh token - Custom firebase token 5. Login with custom token 6. Call API with custom token 7. Send requests with access token
- 23. Proprietary + Confidential Flowusing Firebase auth system and our resource back-end Firebase client SDK Email/Password or phone, 3rd IDPs 1. Call Login API Firebase Authentication 3. Tokens 4. Save tokens in the device Our server 5. Send login request with firebase token (JWT) Firebase Admin SDK 6. Verify token 7. Response 8. Respond tokens: - Access token - Refresh token 9. Send requests with access token 2. Send login request
- 24. Why? Why we shoulduse it - Robust security - Reasonable price (almost free) - Faster development, less resource required - Easily scaling - ...
- 25. Why? Why we shouldn’tuse it - Data protection - In some cases, it may be slower than using existing frameworks (Django, Express JS, Laravel,...) - Pricing plans may change in the future - Firebase can be stopped (who knows, right? GG has a history of destroying their services) - When we need to fully control and customize our system
- 26. Demo time Now it’stime for practicing. Github repo: https://github.com/dsc-hcmut/fia-web HTTPS: https://github.com/dsc-hcmut/fia-web.git SSH: git@github.com:dsc-hcmut/fia-web.git
- 27. Firebase Realtime Database Deep diveinto Firebase Realtime Database and its use cases.
- 28. What is it? Adistributed NoSQL database hosted in GCP - Realtime Database was the original “Firebase” - Store data in JSON tree - Realtime updates - Offline handling - Presence support
- 30. Realtime DB vsFirestore What are their differences? - A large JSON tree, more suitable for simple data model - 99.95% uptime - Pricing based on data volume - Multiple databases per project - NoSQL, document collections structure, more suitable for complex, hierarchical data model - 99.999% uptime - Pricing based on event counts - Single database per project
- 31. Realtime DB vsFirestore What are their differences? - Presence supported natively - Technically a Firebase product - Suitable for: - Massive updates with small data. - Chat apps - Realtime location apps - Presence supported by ourselves - Technically a Google Cloud product - Suitable for: - Complex data structure, queries, large data volume - Other apps
- 32. How to useit correctly? Suggestions for using Firebase RD as a real developer - Read the document carefully - Learn how to denormalize and flatten data - Index the database, query with offset and limit - Write security rules - Sometime it’s better to read data by using Cloud Functions - Use Firebase extensions to integrate with other great features.
- 33. Please use FirebaseSecurity Rules!
- 34. Why? Why we shoulduse RD (when compared with SQL DB) - Realtime support - Fast development - NoSQL - Affordable pricing - Security - Automatically scaling
- 35. Why? Why we shouldn’tuse RD (when compared with SQL DB) - Not suitable for many kinds of project - Lack of querying features - Data protection - Pricing may change in the future - Google may stop this service in the future
- 36. Use cases Is itonly suitable for chat applications? - Chat applications - IoT applications - Websocket gateway - Using both Firebase RD and our database server, why not? - Or any if you need to release your application as soon as possible
- 37. Websocket gateway An exampleWebsocket gateway architecture - A true workable chat application - Same architecture as Slack, Mattermost, Discord,... (Of course they build their own Websocket gateway) - Better performance, lower cost, higher availability - Suitable for startup projects
- 38. Proprietary + Confidential Flowusing our main auth system and Firebase services Email/Password 1. Send login request Our authentication server Firebase Admin SDK Realtime database with Security Rules Firebase client SDK 2. Call generate token API 3. Respond a custom FB access token (JWT) Our resource server 4. Respond tokens: - Access token - Refresh token - Custom firebase token 5. Login with custom token 6. Call API with custom token 7. Send requests with access token
- 39. Realtime database with SecurityRules Our server Firebase Admin SDK 1. Send message (REST API) with access token Our database 2. Check permission, write to database,... 3. Get channel member list, roles, notification settings,... 4. Call APIs (RD, FCM) Firebase FCM 5.2 Push notification to user devices 5.1 Broadcast NEW_MESSAGE event to channel members with ref: ws/{user_id}/events/ User device Channel member Channel member Channel member Firebase client SDK Logged in with custom token Push notifications Events Events Events Observe changes at: ws/{user_id}/events/
- 41. Security rules - Forref: ws/{user_id}/events/ - All requests from Admin SDK are default allowed (we can restrict if needed) - Write permissions: - user_id == auth.user_id (in our custom token) - Read permissions: - user_id == auth.user_id
- 42. Demo time Now it’stime for practicing. Github repo: https://github.com/dsc-hcmut/fia-web HTTPS: https://github.com/dsc-hcmut/fia-web.git SSH: git@github.com:dsc-hcmut/fia-web.git
- 43. Firebase Cloud Functions A robustserverless architecture. Let’s leverage its power with other Firebase features.
- 44.
- 45.
- 46.
- 47.
- 48.
- 49.
- 50. Why? - Integrates theFirebase platform - Zero maintenance - Keeps your logic private and secure
- 51.
- 52.
- 53.
- 54.
- 55.
- 56.
- 57.
- 58.
- 59.
- 60. When? What can Ido with Cloud Functions? | Firebase (google.com)
- 61. Why? - Integrates theFirebase platform - Zero maintenance - Keeps your logic private and secure
- 62.
- 63. Example Analyze the numberof bad words in messages Github repo: https://github.com/dsc-hcmut/fia-scripts HTTPS: https://github.com/dsc-hcmut/fia-scripts.git SSH: git@github.com:dsc-hcmut/fia-scripts.git
- 64.
- 65.
- 66. Firebase Cloud Storage Good price,strong security, automatically scaling,.. Take advantage of one of the biggest CDN providers in the world.
- 67. What is it? AGoogle Cloud Product (not a Firebase product) - Store and serve media content - Images - Videos - Files - Users created content
- 69. Why should weuse it? Does it have any secret weapons? - Global edge cache - Scales automatically - Never worry about running out of space, it scales to exabytes of data - Work seamlessly with other Firebase products, such as Authentication, Cloud functions - Robust security with Security Rules
- 70. How to useit better? Let’s leverage all features of GCP - Use different buckets if needed - Use Security rules to secure your data - Compress images if needed before uploading to the Cloud Storage - Use different sizes when downloading images for different usages - Use Firebase Extensions or Cloud Functions to resize images
- 71. This “lolrus” hasa Cloud Storage “bucket” that stores “files”. Unfortunately, it didn’t use security rules to protect the contents of the bucket!
- 72. Retrieve data insuitable ways Security is the most important thing - Persistent download URLs (getDownloadUrl()): Public and long-lived, but hard to guess - Signed, short-lived URLs (getSignedUrl()): Public, short-lived, and hard to guess - Public download URLs(makePublic()): Public, persistent, without security
- 73. Demo time Now it’stime for practicing. Github repo: https://github.com/dsc-hcmut/fia-web HTTPS: https://github.com/dsc-hcmut/fia-web.git SSH: git@github.com:dsc-hcmut/fia-web.git
- 74.
- 75. Workshop in a nutshell Ashort summary of the workshop. Where should we go from now?
- 76.
- 77. Thank You For JoiningUs! Tai Duong Head of Development @imbaggaarm Anh Tuan Development @AnhTuan4198 Hoang Viet Development @HoangViet144
- 78.