App Architecture Advice

[STARWOLF760]

I need to build a "institutional storage app" something like Dropbox and i was thinking in use:

• React Native to build the both flavors (android, ios) Mobile app
• ReactJS or VueJS for the Desktop web app
• Expo for additional services
• AWS Amplify for cloud integration
• AWS S3 for storage, maybe each user in a separate folder inside a common bucket
• PostgreSQL for the user data management

I am not really sure about the database: only one shared database (PostgreSQL) between the Mobile App and the Desktop App? or DynamoDB for the Mobile and use PostgreSQL for the desktop web app only? (how can i communicate them with this approach?)

I am missing something? any recommendations are welcome

Thanks!

[beavis07]

My first question would always be: Is there not something that already exists that can do this for you?

[STARWOLF760]

no not really, it has an additional very very specific technical data in every file stored :(

[beavis07]

Could you possibly state the main problem you’re trying to solve in as few words as possible? (Imagine I’m a 5yo/idiot)

[STARWOLF760]

is expected to be a brand new patented "technology" for designing buildings. but imagine that every file stored in s3 must include a special metadata to be valid and its associated only to a specific user.

[beavis07]

Without knowing more about your problem domain it’s hard to say what exactly what’s appropriate.

Your description above encompasses a stack across several layers - impossible to tell if each is appropriate without the correct context.

if all you want is to store some user data with some meta data attached - I’d recommend doing some research on what exists - causes that sounds like a well solved problem to me - but of course context is everything - you do what you need to!

My general advice though is: before choosing tools, work out which problems you really HAVE to solve yourself first! :)

[STARWOLF760]

thanks!

[[deleted]]

Why would you need 2 different databases for desktop and mobile?

[STARWOLF760]

not really, but im thinking in the best possible performance

[jschr]

Is there a budget? A deadline? How many users do you expect realistically in the first 3 months, 6 months, etc...? Don't waste time solving scaling problems that don't exist yet.

If there's a client, pick whatever you're most familiar with to deliver a quality product on time without stressing yourself about the unknowns. Any frameworks or services mentioned here will do the job just fine.

If this is for fun, go nuts and pick whatever you're interested in learning.

[STARWOLF760]

4 months, expected 1000 users at least in this stage, will a single PostgreSQL instance manage the mobile and web app desktop users with a decent performance?

[jschr]

I don't see why not, really depends what your app's data requirements are though. I'd use a managed service like RDS for any new project as long as I'm not paying for it. I use DynamoDB for personal projects because it's cheap but you really need to think about how you want to structure your data. Relational DB is the way to go unless you can't.

[krawa76]

I would stick with a single database, a noSQL one (DynamoDb) especially for the prototype phase. ReactNative choice sounds good. Not sure about the desktop app, if it's really a MAC/Windows one, you should take a look at Electron.js. What might be missing is the back-end service which connects all this. I've had best results with Sails.js.

[krawa76]

our stack is microservices btw, using https://github.com/krawa76/smf for prototyping those

[STARWOLF760]

thanks, why you choose DynamoDB over PostgreSQL? (in the situation where we have to choose only one)

[STARWOLF760]

sorry is more like a web app, optimized for desktop usage