Twilio and Phaxio just had a fax based conversation live on youtube
HN user
jnankin
PCI compliance does require this.
still degraded performance!!
Yep, seeing this too across multiple machines!
See this Asana post on how they do it: http://eng.asana.com/2014/02/scaling-asana-com/
This still requires Statamic, PHP, and AWS Elastic Beanstalk. That would appear to be expensive for just a simple static site.
Phaxio co-founder here. Thanks for the write up, Pete! Really great to see the product we've been bootstrapping for 3 years on the front page of HN. We're devoted to making developer faxing as easy as possible. If you have any comments or questions about the service, feel free to contact me directly at josh at phaxio dot com.
what i dont understand is, why would any one want to START with a VM that has some one elses data on it? Forget people wanting their data scrubbed on delete.
i'm a PHP developer. just clicked on the comments to see the usual negative PHP wrath... this time there are no comments at all. not sure which is worse :)
console and SES are working for me now (2:41 CST)
SES is back for me and working
i assume this is similar to what flynn.io will be?
How does your product differ from RightScale, Scalr, or OpDemand?
I can tell you for a fact that this is not true when you're dealing with enterprises or software that is vital for the operation of your business. These types of customers demand to have products hosted internally.
That's what we do at Phaxio: api.phaxio.com api.phaxio.co. We added the 'co' ever since the Zerigo DNS fiasco last year.
Oops, 1 is directly mentioned in the talk.
what happens if 1 shard contains a whole slew of large companies (macy's, gap, etc), or over time users on one shard grow to the point that they cannot be contained within one physical machine? Are they just assuming that this will be very unlikely?
2 questions: 1) What do they do with the Pinterest-generated ID? Do they store it with each row in addition to the local ID? 2) Why randomly select a shard? Shouldn't you do this based on DB size across all boxes, or at least based on physical space left across all boxes?
Perhaps. Or have multiple domains and DNS providers and point both status subdomains to statuspage. (We created status.phaxio.com and status.phaxio.co after the whole Zerigo fiasco last year. co is on zerigo, com is on Route53 )
Interested to know what people think about the market for something like this. While it definitely serves a purpose, is this something that is sustainable and that people will pay money for (vs building it once, and setting it up internally)?
Not being skeptical, just wondering what people think... I've had ideas similar to this, but am still trying to figure out the threshold for payment on things that companies fully need but can justify building internally.
dwight schrute http://www.youtube.com/watch?v=ut-_M1Tib2s
Yeah, also let me add the requirement that it can't break the bank. I can't spend 1k on a chair. Perhaps something more in the 120 or less range.
I'm getting 500s from the API...
I think part of this is the fact that there are a myriad of functions that are just "baked in" to the language, making it a little chaotic. Sometimes it seems like some PHP contributer needed some function and just decided to add it to the language. (Examples: rsort, sort, http_build_query, rawurldecode, urldecode, etc.)
There should be Util or Helper libraries that do that, and in a much more organized way. On the flip side, these commonly used functions are written in C, so they're most likely faster than if you were to write your own in php or load a library.
Either way, I love PHP and use Symfony for all of my projects. PHP/Symfony is pretty much like rails but without the cracked out ruby syntax.