Actually the most successful parimutuel syndicates and HNWI bet programmatically through API’s. They consistently win and they do not make their money from picking a single winner. They bet on exotic bets that have much higher odds and are easier to box. For instance picking two winners or order of the first three horses.
Source: I worked on those APIs to integrate with 20+ exchanges over three companies and 10 years. The syndicates and HNWIs were always the same people over that decade.
The most successful such syndicate in the world is run by a purported billionaire by the name of Zeljko Ranogajec. He made most of his money beating horse racing. Here’s a fascinating article on him and his exploits:
That sounds fascinating. I don’t suppose you have a blog, or any other write up about that world?
Even perhaps a link to one of these betting APIs, if they’re generally available to the public?
Betfair API is 100% free for customers with a lot of code examples in various languages.
Tabcorps TABStudio - http://studio.tab.com.au/ (You need to register as a tabcorp customer but it's "free"). Its basically a JSON REST API
NZ TAB have their batch mode, at filebet.tab.co.nz, which is nothing more than a file upload system.
The ATG, and the other Scandinavian totes provide coupon upload systems (where you generate a coupon file with your selections in it, using third party software), but if you win they will end up banning you.
Most providers keep their APIs hidden or require signing NDAs or other types of contracts, I'm referring to companies like Amtote, Churchill Downs, PMU, BetFred, PGI, LeTurf etc
Usually they're quite surprised when you contact them about doing "integration work", a lot of the APIs are designed for retailer shops to integrate with. For example, I've done some integration work with BetFred, where my client never wants to cancel a bet (placed at the last possible moment), however in order to pass their integration tests, I have to fully support cancelling a wager, just like any retail shop would.
On a side note, I have used (at least one of) the APIs shaunray was referring to that he had worked on.
not horse racing, but there's also a book by Steven Skiena titled "Calculated Bets: Computers, Gambling, and Mathematical Modeling to Win" -- it's about the author's interest in betting on jai-alai matches. there's a bit of stuff about parimutuel betting & understanding how the structure of jai-alai round robin tournaments can produce pretty unusual odds in some scenarios, which can be exploited.
technologically the book is a couple of decades out of date, but it's probably worth a read.
Hi OP, I am the person that made the most recent changes to the AWS Labs refarch. I had been working on a golang version and wanted to clean up the python one. Sunil the original author used the AMPLABS benchmark to calculate the results table. I was planning on updating it with the 1 and 5 node test. Would be happy to include Corral as well.
Hi! Pywren project lead here, we're working on more and more fun HPC-style projects! We're also interested in expanding to more and more backends, so please feel free to reach out if there's something you'd like to see.
I meant more like the opposite, where you can do parallel computing in a cluster by using a simple serverless FaaS paradigm. The idea is to remove the headache of manually setting up an MPI cluster, worrying about MPI communications, etc.
Beacause these types of services go to great effort to keep their repuation high on email services. You use these services so your 1000's emails get delivered instead of being rated as spam or being blacklisted.
My self-run mail server I set up before I had any sysadmin knowledge also has high reputation, isn’t on any blacklist, and successfully is rated non-spam by Gmail, Yahoo, Outlook and all others.
Is there something special why you’d need to pay for a product such as mailgun, and not just something like the ISPmail guide suggests?
Both for small bootstrapped projects, and for larger companies it should be cheaper to just run it yourself.
> My self-run mail server I set up before I had any sysadmin knowledge also has high reputation, isn’t on any blacklist, and successfully is rated non-spam by Gmail, Yahoo, Outlook and all others.
That is most definitely not the norm. Entire ISPs get blacklisted on a regular basis, working around that is difficult.
There are a lot of hurdles to hosting an email service, and some of them are geographic, and out of your immediate control.
If things are difficult... Why wouldn't you pay to make the hassles go away all together?
Hm, I’ve just never actually seen that. I started out with the ispmail guide plus SPF/DKIM/DMARC tutorial from linode and DO, and applies those on my cheap server. Just worked, never had issues (and this is the fifth server already, previously I’ve been with OVH, Hetzner, Online.net and KimSufi).
It’s just, I can’t believe that it’s just luck that I never had these issues. Is it luck? Is it because people try configuring email without such tutorials (which actually would be quite complicated)? Is it because people with no devops experience try it?
On the other hand, if a devops engineer can set it up in a day, it’ll cost you ~270€ (taking a usual European salary for such a person), which would you get 27000 emails with this service. So it might actually be worth it.
I’m curious what sort of email you’re sending and at what volume. Depending on the use case, it may be easy to start clean, but if you’re sending millions of emails a day, you may find it difficult to keep that clean reputation.
It’s certainly not impossible but takes more work as you scale up. I think that’s part of the attraction of these services. Pay for it to be their problem (in theory anyway) :)
