151–160 of 178 posts
Earlier quoted context omitted.
Social networks are also write-heavy so probably not a good fit for SQLite anyways, right?
Social networks have a lot of lurkers who mostly read so I'm not sure about the balance of reads vs writes.
"Solutions such as Kubernetes tout the benefits of zero-downtime deployments but ignore that their inherent complexity causes availability issues." This is completely accurate. I've seen several teams do kubernetes, only to both spend 50% of their dev time on ops, AND cause outages due to kubernetes complexity. They do this all while boasting about zero downtime deployments. It's comical really.
Naturally it spreads like cancer. Non k8s native infrastructure is now abandon-ware. All that tech built over the last ten years is no longer seeing investment. Unfortunately, it solves real problems and rather well. Now a candidate to be reinvented and under the guise of reducing complexity it instead throws the users under the bus and actually does the opposite while costing a fortune.
When you step back and see: bare metals, vms, docker, k8s, stack of k8s plugins and tools, on prem and multi cloud all running concurrently... the IT team is really great at creating work and justifying their existence. Management needs to stop padding them on their back and hold them accountable for the mess they're generating.
It easy for me to complain, I guess, I'm not smart enough to understand how to kill this hydra. But I care about users and their experience and so maybe that's what's missing from this new frontier.
Regarding SQLite's performance, some things I've found very useful: Use WAL mode (writers don't block readers): PRAGMA journal_mode = 'WAL' Use memory as temporary storage: PRAGMA temp_store = 2 Faster synchronization that still keeps the data safe: PRAGMA synchronous = 1 Increase cache size (in this case to 64MB), the default is 2MB PRAGMA cache_size = -64000 Lastly, use a modern version of SQLite. Many default inst…
For us, the biggest thing would be that it can't be used if the database is on a network drive relative to the host process.
Is there a way to backup encrtypted? This would be a killier feature!
Earlier quoted context omitted.
$200k/mo is remarkable for a "side" business! Can you share more of your story?
Sounds like it's https://cravecookie.com/ – so my guess is it's $200k/mo in revenue, not profit... but that's still seriously impressive, assuming at least decent margins!
Is making the project closed to contributing part of that plan?
How did you decide on GPLv3 liscense?
Earlier quoted context omitted.
Sounds like it's https://cravecookie.com/ – so my guess is it's $200k/mo in revenue, not profit... but that's still seriously impressive, assuming at least decent margins!
That’s about 60k cookies per month, or about 1 cookie every 50 seconds.
Earlier quoted context omitted.
Well then you just need multiple Kubernetes clusters for redundancy :-) :-) From another thread on the home page right now: The current trend goes to multi-cluster environments, because it's way too easy to destroy a single k8s cluster due to bugs, updates or human mistake. Just like it's not an very unlikely event to kill a single host in the network e.g. due to updates/maintenance. For instance, we had several outa…
This reads like a bad joke. Where did the KISS principle go?