You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm looking at using Userbase instead of Memberstack or Webflow for user admin. I'll build the back end myself and possibly use Webflow for front end. Userbase will be the intermediary layer between the back end and my datbases. The reasons are:
I am using low cost freelancers and rather than having them hand code my security, I'd prefer something trusted/vetted that they can plug in.
I'd like data to be encrypted without having to implement the encryption myself (or using my low cost freelancers)
I'm considering using Webflow for the front-end which would be very simple to use with Userbase I believe.
My use case is very simple. I have 2 databases: info and users.
i. a user lands on my site and inputs some data. this creates a new record in the users database.
ii. I run API queries and cross reference the results with data in my info database.
iii. I return the results of the API queries, enriched with additional data from my info database and shower this to the user on a page in their browser.
iv. in the background, i save the user info and API query results in the users table.
My questions are:
Is Userbase likely to be a good fit? Will I need to hack/mod any elements of it based on my use cases?
My understanding is that Userbase will create a DynamoDB database on AWS and provide a handy API for CRUD operations to be performed easily. Is this correct?
Are there any features of Userbase you'd highlight especially for my use case?
Thank you :)
The text was updated successfully, but these errors were encountered:
iamarealperson1
changed the title
Noob questions (not that technical)
Noob questions on use case (not that technical)
Apr 12, 2021
I'm looking at using Userbase instead of Memberstack or Webflow for user admin. I'll build the back end myself and possibly use Webflow for front end. Userbase will be the intermediary layer between the back end and my datbases. The reasons are:
i. a user lands on my site and inputs some data. this creates a new record in the users database.
ii. I run API queries and cross reference the results with data in my info database.
iii. I return the results of the API queries, enriched with additional data from my info database and shower this to the user on a page in their browser.
iv. in the background, i save the user info and API query results in the users table.
My questions are:
Thank you :)
The text was updated successfully, but these errors were encountered: