I wonder if AWS is a good location to run a VoIP server. VoIP is a real time application that is very prone to jitter, latency and packet loss. I'm concerned about "noisy neighbors" and decreased network performance at AWS.
Does anybody have experience with running a VoIP (e. g. Asterisk) on AWS?
If you're willing to pay, then you can avoid the noisy neighbor problem almost completely by using c3.8xlarge or c4.10xlarge instances. Those instances get their own dedicated 10G NIC. You can use reserved instances to reduce the cost.
But even with smaller instances, AWS network performance is going to be about the same as any VPS provider. The only way to get guaranteed performance is to do Colo, which is expensive.
I sell an application built around VoIP. I dislike running my own servers, so just lately I moved them to AWS.
At first, I used instances that were not very performant, causing some problems. I quickly moved to more powerful instances and since then there have been no problems at all. There is a slight delay, which is normal, since the servers are not in the same country as the users anymore, but the users haven't noticed it at all.
I can't say how well it scales, though. I have a small user-base, so scaling has not been a problem yet. Network performance might become a problem if you have a huge user-base.
Almost any significant round outside of seed would come with liquidation preference. CrunchBase says a total of $20.9 was raised, so if the final sale price was less then $20,900,001.00, there's likely no money left for common stock.
Interesting. I didn't know that. I understand that if expectations are not met there have to be consequences. But leaving the founders of a company with nothing while others earning money feels completely wrong.
I forgot about the debt holders. So if there was any debt (including un-converted convertible notes), the pecking order is:
1) Debt holders
2) Most senior shareholders and their liquidation preference
3) Less senior shareholders and their liquidation preference
...
99) Common stock holders
This is actually to align the founder incentives in shooting for a big exit. Insert any other order of preferences, and the founders have a stronger incentive to flip the company as quickly as possible in order to create a payday for themselves, screwing investors in the process (which also happens to be a very irrational proposal for investors, which is why you rarely see a round on those terms).
Investors don't inherently get screwed in the process of a quick flip if they have common shares. It means the investor is directly aligned with the founders, and makes it harder for the investor to get a return at the expense of the founders.
Investor puts in $1m for 20%.
Founders quick flip for $30m. The investor just made six times his money, and earned a payout fully aligned with the founders. Absolutely nobody got screwed.
The reason investors like liquidation preferences, is so they can improve their odds of getting their money back at least (and yielding the first dollars of return). They aren't aligning their interests with the founders in this case, they're putting their interests in front of the founders, just as debt does. Liquidation preferences are a way of saying: my equity is more important than your equity; you need my money, so I'm going to make sure my money is treated with more importance than your equity.
Liquidation preferences exist solely to protect investors from their own poor choices at the expense of the founders / earlier shareholders.
Liquidation preferences exist to protect against a company raising $10 million for 20% and selling for $5 million, with the founders taking a nice payoff of $4 million and the investor losing all but $1 million.
In that scenario, without liquidation preferences, the interests of the founders and investors aren't aligned--the founders profit while the investors lose money.
So does this mean employees could be owed something in terms of debt (i.e. if they haven't had their benefits paid out fully) or are they what I assume:
In the US you'd have to make a profit to have the tax liability, and if that's the case, the company is unlikely to be going through a fire sale. There's a host of payroll taxes associated with employees, but those get paid as employees get their paychecks, so qualifies under "debt".
See item 1) debt holders. Within the class of debt holders, the tax man and/or employees with salary claims often have special preference amongst creditors in many countries.
Put yourself in the shoes of an investor. Someone asks you for money after their company hasn't been doing that great. You think here is potential, but you think there's a chance you'll lose some/all your money. So you provide the cash with the stipulation that any sale means your cash comes back first.
The alternative is for the company to tank and the founders - who tanked the company - walk away with your money. That is completely wrong.
Founders don't accept deals for money which are bad for them if they don't need it. You need money, you get the terms.
Same goes if you lose a house by default and then go and ask for money for another house. The subsequent mortgage is going to be at terms significantly less desirable than you may have got on your first try.
But they did get something. What they got was more money to keep trying. They didn't have to take the deal, but most likely would have been still left with nothing.
They got something before. They are paying for that now.
>But leaving the founders of a company with nothing while others earning money feels completely wrong.
Why? They founded a company which tanked. They made poor decisions along the way which led to said taking. They did it on someone else's dime. No one made money here, so why shouldn't the investors get some of the investment back?
Isn't the whole point of venture capital that you take on a large risk in return for a large potential payout. VC is called "risk capital" in a number of languages for a reason.
But at some point the risk gets so large that the choice is for you to not get any investment at all, or get one with additional clauses to reduce the risk to levels acceptable to your potential investors.
It's a tradeoff. And sometimes it can work to your benefit. E.g. if you and your potential investor disagrees about the level of risk and/or about the potential size of an exit, you can try to negotiate a multiple liquidation preference in return for less shares.
Yep, you're right, the lesson out of this is "stick to the common stock for as long as possible". I'm aware of at least one company (5 years running, raised a B round with numbers in mid-eight digits), that still had only common stock floating around.
Unfortunately, the only way to afford that luxury is to not actually need the money, but be in high demand for investors to keep pinging you, and relent at some point with "alright, we don't need money, but if y'all agree to X valuation with common stock, we'll take your money".
But the 120k/year he quoted includes bonuses, stock, and salary. Especially in NY, that isn't all that ridiculous. My annual combined salary in Austin, TX is very close to that at a similar age.
That's pretty good for Texas, right? I've heard it's really really cheap down there. Hence, relatively speaking you're making more than me. Who do you work for? Do you think it's possible to get a similar salary in Dallas too? Any companies down there?
How are they a threat? They comply with the NSL and operate as normal, plus the kickbacks that come with a strengthened relationship with the intelligence apparatus.
With the billions in tax breaks and subsidies, I have problems believing there is actually any coercion between the NSA and the biggie tech companies. So I don't see the NSA as a threat to those or any other American internet companies, but rather to everyone else. The NSA are monsters.
Most likely the average HN reader is well aware that dropbox must have access to read your files. But possibly an average joe who doesn't read the TOS and who doesn't think everything through would assume that private storage is private to joe only and that the advertised encryption extends beyond transport to storage.
Not convinced either will last, but Twitter is effectively mashing on a pimple and making it worse. Prediction: this will help Meerkat's brand + hurt Periscope's.
Does anybody have experience with running a VoIP (e. g. Asterisk) on AWS?