I've been fiddling with a idea sometime and I want to turn it into a product. I first want to build a MVP. I can't make a decision stack I am going to use. I find it difficult to make the difference between taking too much and too little account of an untenable and scalable 'future'.Do you consider SQL for your data layer or settle for NoSQL solution, or maybe for something like firebase? How...
I find that a language as Go feels really tedious working with SQL, Java on the other end of the spectrum has many options but they feel pretty bulky. Whats your language of choice for a relatively simple CRUD app which uses SQL?
How do you handle recurring and time-based events in your software stack. Would you choose for a self hosted solution (i.e. Celery) or choose a hosted solution?
How would you describe the most ideal situation (university, mayor, extracurricular activities) for a aspiring founder? What are the DO's and DONT's for a student which pursues this type of career?PS: I couldn't fit the question mark.
In terms of scalability, reliability and performance? And what are your thoughts about implementing a graph inside e.g. PostgreSQL or Cassandra?The graph will contain roughly about 150.000 vertexes, around 50.000 of those are highly connect between the other 100.000, expecting around 2.500.000 edges in between. The 100.000 vertex will almost all be updated daily. The graph will be used for OLTP...