mperham

40 ms·

481.
by mperham 9y ago
Link is from 2006.
482.
by mperham 9y ago
My business is based on OSS; people are used to no support. I've tried to guide my customers to open issues and stackoverflow questions to get a response from the community. This makes for a nice historical archive that others can sea
483.
by mperham 9y ago
AMA!
484.
by mperham 9y ago
For those who don't know (including me), Wallaroo appears to be a competitor to and/or similar to Kafka: high-throughput stream processing. If I'm incorrect, please let me know!
485.
by mperham 9y ago
24. VALUE is 40 bytes and needs two 8-byte elements.
486.
Happy 6th birthday, Sidekiq(mikeperham.com)
1 points by mperham 9y ago|0 comments
487.
Faktory 0.7.0 – background jobs for all languages(mikeperham.com)
1 points by mperham 9y ago|0 comments
488.
by mperham 9y ago
Let's be clear here. We're not talking about where to eat lunch or controversial scientific theories, a la Galileo or Darwin. We're talking about "is race X smarter than race Y", "is gender X smarter than Y&q
489.
by mperham 9y ago
> Even electric motorcycles with 30-40 bhp rely on water cooling, let alone a car 20 times the weight. FYI my Zero SR motorcycle, which has 70+hp, uses passive cooling only.
490.
by mperham 9y ago
Background jobs are specialized messages. You can build a decent job system on top of a message queue but you'll lose the specifics. For instance, Rabbit and Kafka won't give you the built in retry system with error tracking and
491.
by mperham 9y ago
https://github.com/contribsys/faktory/issues/new
492.
by mperham 9y ago
Sidekiq is Ruby only. That won't support one of my key goals with Faktory: polyglot. Background jobs can benefit applications written in many languages. There's many different tools and many different users. No one choice is ap
493.
by mperham 9y ago
Sidekiq is not a server, it's a Ruby worker process. Redis is the server and I can't build a fast, easy to use embedded queue system on top of Redis.
494.
by mperham 9y ago
It supports backup and restore today but RocksDB doesn't have a replication story at the moment. Side note: Resque will lose jobs if it crashes, it doesn't use RPOPLPUSH. I hope you'll take another look at Faktory in a few m
495.
by mperham 9y ago
For those of you pointing out flaws, remember you are picking apart a pre-1.0, just launched project. We're all hackers and startup people right? Think MVP, no one can ship a perfect system completely finished.
496.
Faktory, a new background job system(mikeperham.com)
194 points by mperham 9y ago|53 comments
497.
by mperham 9y ago
Sure, no one's ever bought Tableau along with a Windows Server license to solve their data warehouse analytics needs.
498.
by mperham 9y ago
Yep, that agrees with one rule I've found very helpful in my Sidekiq project: All free/OSS work/discussion is done in public. Never private email, never Slack. Always open an issue. Security issues are the exception here.
499.
by mperham 9y ago
So they aren't confused with "Pants Maker"?
500.
by mperham 9y ago
Every (hetero) marriage.
501.
by mperham 9y ago
Thanks for the mention!
502.
by mperham 9y ago
> is to have free and easy access to __accurate__ information. As we've learned recently, politicized or partisan info ("fake news") can flood and disrupt our decision-making.
503.
by mperham 9y ago
Another pro-tip: you can install the Stripe iOS app and get realtime payment success/failure notifications. Not good if you have 10,000+ customers but useful if you have <1000 customers.
504.
by mperham 9y ago
If you are going to build and maintain a project, you are already taking on a second job. The difference is whether you make $0 or >$0. You should not monetize if the problem your OSS is solving is not a problem you care about. You hav
505.
by mperham 9y ago
As always, the answer to all articles titled with a question is "No".
506.
by mperham 9y ago
My business is built on CGI scripts for processing automated webhooks. There's several non-trivial benefits: 1. Nothing running 24/7. No services to monitor, very light on memory. 2. Immune to memory leaks and bloat. Guar
507.
Monitoring Redis(mikeperham.com)
2 points by mperham 10y ago|0 comments
508.
by mperham 10y ago
Yikes, that's even worse. init.d is a tire fire. As someone who maintains software that uses Redis heavily, I view 3.0 as somewhat recent and very usable for most. There hasn't been significant functional changes in Redis since
509.
by mperham 10y ago
I disagree with the redis quickstart guide - making the user download a tarball, compile source and install systemd service scripts is ridiculous. As long as the Redis version is somewhat recent, they should install straight from the distr
510.
Redundancy does not imply fault tolerance(blog.acolyer.org)
6 points by mperham 10y ago|1 comments

More ›