Blog Post 2


My favorite technology we are using would have to be the Auth0 authentication API. My least favorite technology used at the moment would be GCP Buckets

The Technology I had difficulty learning but now appreciate would be the Google Cloud Platform as a whole. It’s a bit of a step learning curve getting everything setup even for a simple project. And the GCP has so many different technologies and services within it it can be really easy to get overwhelmed and know where to even start. But once you start piecing it together it’s really incredible how easy it is to create really cool, scalable web projects.

If I could change anything it would be how GCP Buckets is implemented, I just feel like it could be more structured, but I think that is sort of the point of it. I would say GCP as a whole had a really step learning curve like I said earlier, it just has so many things going on it can be difficult to determine how to do the things you want to do. I’d say the tech we are using that has the easiest learning curve would be Auth0. It’s a really cool user authentication API that makes it really simple to offer the service of user creation and login without having to implement it ourselves.

If I had to start over I wish we wouldn’t have used GCP Buckets, but since it was a required part of our project due to our project lead using it for data storage that wasn’t possible. I would have liked to use a more structured database like a NoSQL database or a MySQL database.

I would have liked to included React in our tech-stack. As of right now we are just using Vanilla JS for our user interfaces, and while I think it will be sufficient for our purposes I would have liked the opportunity to learn React.

My Favorite tech so far is definitely Auth0, and the way it works is pretty cool. You create an account with them and register your website that you want to have user login/creation for. You need to register the URL’s for redirection and callback so Auth0 knows where to redirect the user after successful login. And the way it works is, you redirect the user to Auth0 -> the user logs in -> the user then gets redirected back to your site, and an authorization token is included. This token basically confirms that the user is authenticated and “logged in” and it includes unique identifiers to tell who your users is for your site’s purposes.

Print Friendly, PDF & Email

Leave a Reply

Your email address will not be published. Required fields are marked *