biermic

The coding part of building a SaaS is the easier one. Get a job and build on the side

Nope, we just decided to migrate to S3

I've integrated it into two projects. Users loved it.

Back in 2006 my blog got me a girlfriend. I think exposure in any way is beneficial.

I don't, they'd probably rather sell what is left.

2 things to add:

- I'd decouple the database writes with a message queue.

- Make sure that table is partitioned if you haven't. TimescaleDB's hyper tables are a good compromise here if you are already using Postgres..

A lot of things but not really much at the same time

AWS thought us that one cannot trust status pages

Could you reduce to 24 hrs per week? That would be 3 full days out of 7.

That sounds like a wonderful lifestyle!

Maybe something more basic. Like GOTO's

Maybe a proper debugger?

Redshift COPY from s3 is also affected.

  -----------------------------------------------
  error:  No response body.
  code:      30000
  context:   
  query:     1154965
  location:  xen_aws_credentials_mgr.cpp:403
  process:   padbmaster [pid=15893]
  -----------------------------------------------

I have one running with a ~5TB big unpartitioned table. Adding ~9M rows per day, with significant read load via 2 replicas. Works just fine on a 32 GB memory RDS instance. There is another table half the amount of rows and I join the two 1000s of times a day.

Took a bit of fiddling around to have things run stable. Currently migrating to Redshift, which has stellar performance but comes with its own problems.