kingmotley

5 ms·

1. 1.▲
   by kingmotley 5y ago

   That makes more sense, sorry for the confusion. I don't think your expectation is unrealistic. I haven't run into anything like what you experienced, but my exposure to express under tight memory constraints isn't something
2. 2.▲
   by kingmotley 5y ago

   I would like you to explain how "You better not do some type of async stuff in LINQ, because the system is going to spawn a process for each entry, obliterating your production instance by creating thousands of processes, using a bunch
3. 3.▲
   by kingmotley 5y ago

   The documentation you linked to clearly states that they recommend 4GB of memory and more for larger databases. While it CAN run on 1GB of memory, it is also therefore NOT recommended. You chose to go the route of the unrecommended. Also,
4. 4.▲
   by kingmotley 5y ago

   I would say it sounds unfounded to me. You "jumped" in to a different language, different database, different framework, and you landed up making junior level mistakes. Your explanations of what went wrong show clearly that you s
5. 5.▲
   by kingmotley 5y ago

   dotnet add package EfCore.Cassandra. Then in startup.cs or program.cs, add this to your services: optionsBuilder.UseCassandra("Contact Points=127.0.0.1;", opt => { opt.MigrationsHistoryTable(HistoryRepository.DefaultTableName