😊

AWS Amplify?

This is how I stomach any of these videos

Where as all other videos on KZfaq you can play at 2x speed, here you have to slow down. Bravo to this educator who’s really good at delivering value.

lol 😂 being a mexican but still listening at 1x... Can you do the same with spanish, hdlv? 😂

All his videos like this 😢

Haha, it wasn't too severe to rerecord, but I knew somebody would notice

You prolly dont care but does anyone know a method to get back into an instagram account..? I somehow forgot the password. I appreciate any help you can offer me.

@Graham Bodie Instablaster ;)

@Victor Diego i really appreciate your reply. I got to the site thru google and Im waiting for the hacking stuff atm. Seems to take a while so I will reply here later with my results.

@Victor Diego it worked and I actually got access to my account again. I am so happy:D Thanks so much you really help me out!

@Graham Bodie glad I could help :D

Jeff Fireship =))) wow! That's a pirate name if I ever heard one!

That is a good point, thank you!

It looks just like mine, "One Dark Pro" - Ironically the color scheme used in Atom.

gotta use functions to manage everything or you would write complicated rules and use transactions.

Use anything besides transactions is a really bad idea.

I guess it only looks this way because you are looking from the perspective of a RDBMS user. Relational data is easy with SQL if you allow joins. These DBs are made for storing relations between data. Document DBs are way simpler. For me document based DBs really shine in the one db query per application screen use case which makes it super easy to fetch all the data you need in one go without thinking too much about Object Relational Mapping and Joins. This makes it easy for application development because you define your db documents to fit your application and not define the db structure separate from your application. This gives you a lot of flexibility and might save dev time because you don’t have to think about strict schemas. Personally I like to think of it similar to typed vs. untyped languages. One is more flexible and you might accidentally shoot yourself in the foot with stupid errors the type system would have found, the other gives you more safety but you might build too many abstractions just too satisfy your type system and now everything is more complicated.

That would work if they were nested in subcollections, but all the docs are in the same root collection in this case, so they can be read with a single query.

MySQL for Life!

Not really scalable though :( I heard it was pretty slow once your queries become complicated enough

@@martonkardos8094 prolly, but I doubt the usual hobbyist/small bussines will hit that ceiling

@@joonaskali2337 yeah sure thing, I mean I never hit it personally, just heard it from a friend who was working for a large company

I guess it depends on what you mean by N-tier? I view Firebase as a platform that helps follow the multi-tier app pattern by separating your DB, backend, and client libraries.

It's about firestore specifically. There are some paralells to mongodb tho.

@@Fireship thanks

If you have a computed value, like a user's lifetime game points or something, you can use cloud functions to aggregate the value to a single doc.

You can use in-memory cache services like redis, elasticcahce etc. If you are using any API Gateway, they usually have the feature for caching API responses for certain amount of time. Eg. All API requests to a particular url with same params can be cached for 5 mins.

Yeah I'd be really nice if there was a Discord community dedicated to Fireship.io

I am considering it. Slack is already established, so migrating might be hard.

It's possible to do a WHERE query with the IN operator, but this has a hard limit of 30 items in the comparison array (documentation: firebase.google.com/docs/firestore/query-data/queries#in_not-in_and_array-contains-any). But using the example in the video, I think the idea is that reading 3 documents is preferable to reading all documents and then still having to find the relevant documents in the client-side code.

Hey Aaron, there's a video named "Behind the Scenes: How I make the Videos" from Jeff. I think he explains everything over there. Check it out from his channel. If you are asking for the tools, check out "7 Amazing Developer Tools that you're not using yet" from Jeff as well. Good luck!

Since no one has answered it yet, here you go: That's a bad db design, sql or not. You instead embed document id to refrence same data over all references just like foreign keys. Only thing about no sql is, the data structure of document is not predefined and can have various data. But you can always use best practices from other data modelling and apply it here to make life easier.

@@MaulikParmar210 not really, check the google documentation, it's best practice to duplicate a portion of the data so u would only need one query to access the information, modern databases are optimized for reads since they occur 1000s of times more often than writes. However, everything comes with tradeoffs, you would need to update every place when you are making a change, nothing is perfect.

@@marcosraul4132 excuse me but google isnt the only data store vendor in market. And whole point is there are trade-offs between different design patterns and one can only understand it if they have implemented it in first place. Well there are also ACID compliant data stores available where you really do not need to duplicate data for high availability. Thus if you need to, you are likely compromising on some factor. Either om technology level or standard practice level. And it has nothing to do with Google's bigtable, any other traditional or widecolumn datastore they use. DHL produces about 1TB of consignment data daily and still returns any query within 300ms in distributed cluster across multiple regions, ever wondered why? Plus they don't duplicate that much data, considering the volume! Ofc there are multiple examples like these but people should get the point that there are problem specific solutions rather than solutions that solves general problems(because they are specific!) when it comes to big data.

@@MaulikParmar210 i agree with u that there are always tradeoffs, however, since this is a google product, designed, maintained, and used extensively by google, their documentation should be your main source of truth. If u want to explore with other architectures for firestore, u would end up repeating the learning process that they already went through, to ultimately reach the same conclusion or settle with an underperforming db.

@@marcosraul4132 when you scale you stop using firestore, that's simple and more productive at large level. Firestore allows untrained devs and most importantly managed access to datastore. Most devs who use it don't have skilled infrastructure devs or lack in one or other architectural implementations. Simply put they have to migrate at certain thresold if they want to grow. If anyone relies on 3rd party proprietary infrastructure, it's their loss in terms of being vendor locked for lifetime. Since this is google product you are bound to what it does and that is why exactly you should know the alternatives as well if you are serious about future of the software you are building. Source of truth remains same, firestore can't do it doesn't mean others can't and if you need it you have very good reason to explore and build software with industry standards.

Google is your friend... that leads you to StackOverflow. Try this - stackoverflow.com/questions/57889195/analog-of-promise-all-in-dart

I have a document called group, which has a list of user Ids/a collection of user documents (containing user profile pic urls, names, etc) is there any way in realtime to join them? (i.e. inject the user details into the group)

You can now use the IN clause in firestore

@@phasaoh4540 I think this person wanted something like a string-contains but that doesn't exist in firebase. 'in' checks if a field is equal to one of the values in the provided array.

The man does not exist!

🥇

For bodyguards, by bodyguards

you can use youtube setting to slow it down bro