171–180 of 334 posts
I'd argue that just about every infrastructure that looks like this benefits from Kubernetes (that you're not setting up and managing), and that's a lot of them. The biggest problem is that not enough people have boiled down Kubernetes enough to look like heroku yet. Google Cloud Run is possibly the best example of what Kubernetes can look like/run like -- it runs on (probably a relatively heavily modified) KNative,…
Earlier quoted context omitted.
That's right, I'm exaggerating. At current rates I'll hit that limit at 7.5MM pageviews/month. I've also paid for extra builds once or twice in the past (automatically charges a few dollars when you cross the build time limit), and I pay them $9/mo for analytics.
Are you happy with their analytics? I have no experience with website analytics but I find their offering a bit too minimalistic. I wish for the following features: - Break down page views into unique visiters for all views (per site, per country etc.). (or some other comparison between those). - Don't lose the history after 30 days. - Export to .xlsx
Earlier quoted context omitted.
... a decade later: Real cloud vendor lock-in is when you have decades of code written against a [cloud vendor] and you're getting charged outrageous [cloud] rates and it would also cost a fortune migrate.[sic]
If anything, vendor lock-in is consistently underblown .
One thing I like to talk about to Cs is their strategy on capex vs opex, because honestly that determines quite a lot, but is often something engineers dont think about.
Earlier quoted context omitted.
People here underestimate google app engine a lot. But I doubt if there is better one person Saas service out there.
If you haven't checked out App Engine in a while, you really should. Especially check out the App Engine "Flexible" editions, which make it really easy to run on App Engine withOUT getting locked in. I run a NodeJS GraphQL server in App Engine Flexible, and it is basically just like running it in a Docker container. It's also pretty trivial to run in Google Cloud Run if I so desired, there is even a tool to assist: h…
I am also a one-man SaaS (though not a successful one). The following tends to be my stack (on Google Cloud, if you will): - Cloud Run (serverless containers) - Cloud SQL (via proxy) - Cloud Monitoring & Logging (formerly Stackdriver) - Compute Engine (if necessary, e.g. websockets) - Cloud Build for GitOps (deploy on push) It's clean and simple (to me). Billing is in one place, nicely separated by projects. Monitori…
Good article. My comment might be off topic in which case, please ignore. If you have a one-person SaaS company, how do you get past customers’ resistance to a single point of failure, namely you? Do you pretend you’re not just one person? Do you only have customers who could handle losing the service when you, say, run away to meditate on the mountaintop? (Or get run over by a beer truck, or whatever.) Is there some…
I've made a living running one-person SaaS sites for over 20 years, many of them in the same space as OP (analytics stuff). I can't recall a customer ever asking how many employees there are. It just doesn't come up. I don't think small business customers care. Maybe it matters for more enterprise salesy type businesses.
My infrastructure is $2,800/year. There are two Servers load balanced with DNS. Each Server has 3 jails (Nginx, App, DB) and 2 NICs The internal NIC is for replicating the DB, and for the App Servers to target the Primary one. Diagram and Configs: https://blog.uidrafter.com/engineering/freebsd-jails-network...
Earlier quoted context omitted.
Are you still with them? If yes, would love to hear why. Otherwise, what made you jump?
I still use GCP, but I avoid locking myself into their proprietary infrastructure when I'm writing new stuff. I feel like Google is far too cavalier about deprecating services and forcing their customers to do migration work. It is hard to replace GCP's managed datastores because I really don't want to maintain my own database server (even if it's a managed service that someone else upgrades for me). So I've stuck to…
Having worked with quite a few ex-Googlers this is a pretty standard Google engineering pattern.
Earlier quoted context omitted.
If your frontend is on CDN, how are you handling auth? Do you use Firebase for that?
I oversimplified a bit. I have a low-traffic "admin" interface that's rendered server-side. The people using that are my direct customers and are the only authenticated users (they auth in a traditional in-app way). I also have a high(er)-traffic frontend on a CDN which is used by their customers. User writes there are purchases/payments handled by third(fourth?)-party SaaS.
My current employers still haven’t learned this lesson and think caching fixes everything.
Earlier quoted context omitted.
Document everything in excruciating detail - I go so far as to record all the commands I run; and when complete o destroy the machine and start again (or use a separate system) and verify that I accurately recorded every step. You can add additional text about why you did certain things - and then store the data in a wiki or checked into git or similar so you can find it when you need it.
What is your system for keeping all of these notes. Do you just have a git repo for everything?