Architecture Advice for commercial use

[gusgonnet]

@StngBo

But the simplicity of the simple auth approach seems ideal to quickly develop our MVP get some customers and prove out it’s value. This is particularly attractive as we essentially have one developer to build/maintain entire stack.

Hi, it may not be all roses and sunflowers in the land of simple auth.
There may be few things that can cost you even more than in double legged auth, as the reset passwod flow emails as discused some time ago here (to which Particle provided a solution):

Stop using the simple authentication method for Particle products?

Hi, Recently there’s been a Deprecation of Sending Password Reset Emails email sent from Particle. I am wondering if this method here: [image] has any potential use in real life, considering that once a customer is created there is no way to reset their password. Granted, one can set their password, but for that one would need the auth key of the customer that may not be available anymore (if the customer reinstalled my product’s app, for instance). Consider that one of the advantages of s…

If that is not an issue for your MVP, then the better! I am not trying to stop you, just giving you the info. As a reference, I found that issue out only once I was deep into the simple auth for one product, and then in all subsequent products I used double legged auth and I do not recall it being a lot more work.

Best,
Gustavo.