jadengis

This is obviously a huge mistake by Okta (for the love of God understand how your crypto functions work before you apply them) but at the same time, a crypto function with a maximum input length that also auto-truncates the data sounds like bad API design. You are basically asking for someone to goof up and make a mistake. It's much better to implement these things defensively so that the caller doesn't inadvertently make a mistake. Especially with a hashing algorithm, because there is no way to verify that the result is correct.

Cloud Firestore and MongoDB are pretty similar in general but have a few key differences:

- Firestore supports nested collections, so a document in one collection can have a subcollection that is scoped to that document. This allows for a kind of hierarchical structuring of your data model e.g. carts are a subcollection of users - Firestore has more limitations on the kinds of queries to can make because every query in Firestore has to be backed by an index. This can be a little annoying but the trade off is that query performance doesn't degrade overtime as datasets grow. - Mongo has a pretty robust aggregation framework that Firestore does not have. With Firestore you need to perform aggregations in you application. - Firestore can be interfaced with directly from a frontend app by using their SDK and a set of security rules that enforce the permission your users have. This SDK supports listening for real time updates which is one of the primary use case of Firestore.

Hope that helps!

In this article we will discuss how to translate some advanced fundamentals of SQL into NoSQL in the context of Cloud Firestore.

Hi HN!

With Ezfire, you can write and execute queries for Cloud Firestore and Firebase Realtime Database using the same backend APIs you use in production, securely share connections to your production database and easily collaborate with your team when solving data issues in a way the feels natural for developers.

In the past, we have built and operated apps using the Firebase platform. We always found it challenging to really dive into to the data in my database either when debugging issues or just when we were trying to understand how app was being used. They existing tools just weren't sufficient. We built Ezfire to solve this problem by giving them modern tools and a familiar set of APIs instead of a bunch of complicated menus.

We hope Ezfire makes lives easier for all the Firebase developers out there. We’d love to get your feedback, as well as answering any questions you might have.