StartupsOct 14, 2018
FacebookGoldenGate

Startup db design and setup

Hello, I am working on my startup and gone through initial designs and need to now do db designs and schema definitions, what do folks recommend to start with. I signed up for AWS although now sure how i compares to Azure. Also not being a database guy, what are things I should be aware of so that I don’t encounter issues later on? For folks that have gone through scratch, Can you share your experiences and tips?

Add a comment
Microsoft raDz66 Oct 14, 2018

Think NOSQL vs SQL and the right choice for your app first. Once you decide on the former look at the benchmarks on the two clouds. At this point, Azure vs AWS is really a preference as both clouds are really at parity wrt functionality.

Microsoft raDz66 Oct 14, 2018

Secondly, Does your app target a consumer or the enterprise. If it's the latter Microsoft has a e2e program to get you all the way from supporting your development to funding your go to market.

Facebook GoldenGate OP Oct 14, 2018

My app is consumer focussed, heavy data intensive. Bulk of transactions and constant push pull of data. Also, I am a Product manager although I was a developer a while back so not in touch that much.

New
Crooklyn🔫 Oct 14, 2018

Data-intensive startup. Asks about databases. Good luck.

Uber BossDogg Oct 19, 2018

Lol good one “new”

New
Crooklyn🔫 Oct 14, 2018

Is Google banned when you work at Facebook? You should use MongoDB on a Windows 10 server in your apartment.

Facebook GoldenGate OP Oct 14, 2018

Ever been nice to anyone in your life?

New
Crooklyn🔫 Oct 14, 2018

Yeah. Not to product people who want to launch a data start-up without knowing anything about data and can't be bothered to pick up a book. Let me guess, your start-up is going to be 90% fluff until you find a sucker?

Intuit Fp7kty Oct 14, 2018

Always choose SQL unless you have a compelling reason for nosql.

Apple cho Chang Oct 14, 2018

Why?

Intuit Fp7kty Oct 14, 2018

It enforces you to think about the most appropriate way to structure your data. Nosql is awesome, but I’ve seen people do some nasty stuff with it that I imagine would be difficult to unwind later (like very deeply nested objects).

LinkedIn imlikethat Oct 14, 2018

Do you have access to any legit person in this area as an advisor/mentor? He/she can at least point you in the right direction. On blind you would either get non-productive comments like the ones ridiculing you or seemingly technical comments that you can't necessarily trust.

Facebook GoldenGate OP Oct 14, 2018

Agree. I am currently building an MVP and have two Apple engineers that are expertised in enterprise db, I wanted to seek opinions as folks may have gone through the journey from scratch. Its amazing to see folks ridicule your question when they have nothing to contribute. At least I am trying to do something as opposed to ridiculing anyone. But again there will always be a small subset of barking dogs. I will now focus to find a mentor in this space outside this network.

Splunk iorm72 Oct 14, 2018

Start simple. SQL is simple. Go with postgres which IMO is the best RDBMS out there.