During the night of 30.06.2012 to 01.07.2012 our internalmonitoring systems registered an increase in the level ofIT power usage by approximately one megawatt.
The reason for this huge surge is the additional switchedleap second which can lead to permanent CPU load on Linuxservers.
According to heise.de, various Linux distributions areaffected by this. Further information can be found at:http://www.h-online.com/open/news/item/Leap-second-Linux-can...
In order to reduce CPU load to a normal level again, arestart of the whole system is necessary in many cases.First, a soft reboot via the command line should beattempted. Failing that, you have the option of performinga hardware reset via the Robot administration interface.For this, select menu item "Server" and the "Reset" tabfor the respective server in the administration interface.
Please do not hesitate to contact us, should you have anyqueries.
Hetzner Online AGStuttgarter Str. 191710 Gunzenhausen / Germanyinfo@hetzner.dehttp://www.hetzner.com
During the night of 30.06.2012 to 01.07.2012 our internal monitoring systems registered an increase in the level ofIT power usage by approximately one megawatt.
The reason for this huge surge is the additional switched leap second which can lead to permanent CPU load on Linux servers.
According to heise.de, various Linux distributions are affected by this. Further information can be found at:http://www.h-online.com/open/news/item/Leap-second-Linux-can...
Please do not hesitate to contact us, should you have any queries.
Second is to seek out experts. This is much easier now thanks to sites like HN, StackExchange, et al. They can help you gauge your own knowledge level.
I still think it's weird Facebook would do this.
Code Like a Pythonista: Idiomatic Python (http://python.net/~goodger/projects/pycon/2007/idiomatic/)
Common mistakes and Warts (http://learnpython.pbwiki.com/PythonTricks)
How not to write Python code (http://eikke.com/how-not-to-write-python-code/)
Python gotcha (http://eikke.com/python-gotcha/)
Here's the stack overflow thread I was looking at:http://stackoverflow.com/questions/356161/python-coding-stan...
If you need something longer, the official Java Coding Style is getting a bit old, but Java is probably the language where you're least surprised when you start working at a new company or project.
Other than that, I prefer actual books that don't just focus on indentation, but go beyond that, like Perl Best Practices or Smalltalk With Style.
Tree Style Tabs is always the first addon that I install in a new Firefox, followed closely by All In One Sidebar, It's All Text and Uppity. Then come Pinboard, and adding DDG to the search bar.
I've tried many times to like Chrome, but being a bit faster doesn't make up for less customization, for me.
AWS is an amazing tool and you have a few options here, but the downside is the more options you use to be highly-available (HA), the more expensive AWS gets (as you would imagine).
Your first option is to be HA across a SINGLE region; to do this you make use of the elastic load balancers (ELB) + auto-scaling. You setup auto-scale rules to launch more instances in different availability zones (AZ) either in response to demand or in response to failures (e.g. "always keep at least 3 instances running").
You compliment that with an ELB to load-balance incoming requests automatically across those instances in the different AZs. This is all fairly straight forward through the web console (except auto-scaling is still done via CLI for some reason)
If you want to be HA ACROSS regions you can't just use ELBs anymore, you have some added complexity and an additional AWS feature you will likely want to use: Route 53.
Route 53 is Amazon's DNS service which offers a lot of slick DNS-features like removing dead points from DNS rotation, latency-based routings, etc. There are also something like 29 deployments of Route53 (and CloudFront) around the globe so you'll hopefully never have Route53 become a point of failure for you even disaster strikes.
In this scenario you would setup the HA configuration for a single-region as mentioned above, but you would do it in multiple regions. Put another way, 2+ servers in multiple AZs in each AWS region. Then a Route53 DNS configuration setup to point to each ELB in each region representing those individual pockets of servers.
Ontop of that you would use Route53 to manage all routing of client requests into your entire domain; you can leverage the new "latency-based routing" (effectively why everyone was asking for GeoDNS for years, but even better) and monitor capability to ensure you aren't routing anyone to a dead region.
Here is what I would recommend given the size of your budget and need to stay up in the AWS cloud, in-order of expense:
1. Launch a single instance in a region with acceptable latency that has never had an outage before (e.g. Oregon has never completely gone down but Virginia has -- yes yes I know VA is older, but you understand my point). This solution will be cheaper than multiple instances in any region.
2. Launch multiple instances using the web console, in multiple AZs in US-EAST (cheapest option for multi-instances) and front them with an ELB. You skip any auto-scaling complexity here but you need to keep an eye on your servers. I think ELB fixed the issue where it would effectively route traffic into the void if all the instances in an AZ went down.
OPTIONAL: If you didn't mind spending a few $ more, you could do this strategy in the region that has never gone down for added piece of mind.
3. Launch single instances in multiple REGIONS and front them with Route53. This isn't really a recommended setup as entire regions will disappear if you lose a single instance, BUT I said I would list possibilities in order of price, so there you go. You could mitigate this by setting up auto-scaling policies to replace any dead instances quickly in the off chance you wanted to do exactly this but not babysit the web console all day.
4. Launch multiple instances in each region, across multiple AZs fronted by ELBs and then the entire collection fronted by Route53.
NOTE: The real cost comes from the additional instances and not from Route53 or the ELB; so if you can use smaller instances to help keep costs down (or reserved instances also) that might allow you to provide a larger HA setup.
What about my data?
Yes, yes... this is an issue that someone already touched on (data locality below).
You will have to decide on a single region to hold your data; in this case I would recommend using DB services that aren't based on EC2 and have never experienced outages (or rarely) -- this includes S3, SimpleDB and/or DynamoDB. AWS's MySQL offering (RDS) are just custom EC2 instances with MySQL running on them, so any time EC2 goes down, RDS goes down.
The other DB offerings are all custom and except for SimpleDB a long time ago, have never experienced outages that I am aware of.
Making this choice is all about latency and which DB store you are comfortable with (obviously don't choose SimpleDB if everything you do requires MySQL -- then use RDS); you'll want your data as close to your web tier as possible, so if you are spread across all regions you'll just want to pick a region with the smallest latency to MOST of your customers (typically West coast if you have a lot of Asia/Aus customers and East coast if you have a lot of European customers).
Want to Go to 11?
If you have the money and desperately want to go to 11 with this regional-scale (which I love to do, so I am sharing this) you can combine services like DynamoDB and SQS to effectively create a globally distributed NoSQL datastore with behavior along the lines of:
1. Write operation comes into a region, immediately write it to the local DynamoDB instance, asynchronously queue the write command in SQS and return to the caller.
2. In 1+ additional EC2 instances running daemons, pull messages from SQS in chunk sizes that make sense and re-play them out to the other regions DynamoDB stores; erase the messages when processed or if the processing fails the next dameon to spin up will replay it.
3. On reads, just hit the local DynamoDB in any region and reply; we trust our reconciliation threads to do the work to keep us all in sync eventually.
NOTE: If you prefer to do read-repairs here you can, but it will increase complexity and inter-region communication which all costs money.
The challenges with this approach is that you pull up a lot of DB concerns into your code like conflict resolution, resync'ing entire regions after failure, bringing new regions online and ensuring they are synchronized, diffs, etc.
There is a reason AWS doesn't offer a globally-distributed data store: it is a really hard problem to get right once you make it past the 80% use case.
Your data will determine if this is an option or not; some data allows for certain amounts of inconsistency in which case this strategy is awesome and works great; while other data (e.g. banking data) cannot allow a single wiggle of inconsistency in which case pulling all this DB logic up into the application is a bad idea. Your failure scenarios become catastrophic (e.g. your conflict-resolution logic is wrong and wipes out the balance from an account; or keeps re-filling the balance on an empty account... something bad basically)
It is all a trade-off though; if you managed your own Cassandra cluster though, Cassandra does all this and much more for you automatically; but then you just put your time into Cassandra administration instead of developing the logic around DynamoDB (or SimpleDB, or MySQL, or whatever); just pick which devil you feel more comfortable with.
I am not aware of a services company yet that offers cross-region AWS datastore deployments yet; Datastax and Iris Couch will setup things for that like you via a consulting/custom arrangement, but there isn't a dashboard for launching something like that automatically.
Hope that helped (and didn't bring you to tears of boredom)
I'm in one of the us-east zones and I haven't had a failure in at least a year. They retired one machine I was using and dealing with that was as simple as starting and stopping -- at a time I chose.
With five zones in U.S. East, the probability of a zone failure affecting a single zone systems is 1 in 5.
If you're a busybody who spreads your system across five zones, the probability of a failure affecting you becomes 1.
You're spending more money, and dealing with a lot more complexity, all to increase the probability that hardware failures will affect you.
Now, you're hoping that a zone-distributed system will be able to recover from failures, but that's tricky to do and it's quite unlikely that this will work if you haven't tested it. Add the fact that all the other "cool kids" will be trying to recover their systems at this time and make AMZN's control plane go down.
In the meantime, with probability 4/5 I'm sleeping through the disaster and the first time I hear about it is on hacker news.
Sorry to be fatalist, but it's a hard problem. This last outage was more than just an AZ failure. Region-wide API usage was affected, so operations like static IP reassignment and ELB changes were not taking effect. This means you are hanging out in the wind should there be something unusual that requires manual intervention (as was the case with us).
Route 53 is a good service but I don't know how its control plane works, and it could be that problems in a single region would disable the ability to update DNS records (I would guess that DNS reads are a lot more available than writes). And in any case DNS is not a very good failover mechanism due to upstream caching.
Unless your business model requires higher reliability than Instagram, Netflix, and Pinterest, I'd suggest going multi-AZ, crossing your fingers, and doing everything else right.
Anyhow, sorry I don't have a simple answer - I'm not sure a simple answer exists.
1. Use Rightscale. You can get away with the free edition, but for $500/month the basic paid edition will allow you access to arrays and all the excellent scripts available on the marketplace.
2. The front end. I would strongly suggest moving away from ELB. We are using it and are about to get rid of it. The main problem is what exactly happened last night. If a whole AZ goes down, the ELB for that zone can get screwed and the DNS was not updating the CNAME to remove the bad zone. Instead of ELB, we have our own LB solution we are going to roll out that will use Rightscale server arrays and will handle the updating of the DNS names itself. We also aren't going to use Route53, because we learned last night that the API for that can go down and you can get stuck with bad DNS records.
3. Application servers. Use at least 3 AZ and have them evenly spaced. This is easy to do in Rightscale with sever arrays. Make sure your voting ration for scaling isn't 50% because you might not scale correctly if you loose 2 AZ. Keep the vote to 30% and you will be happy (if one zone votes to grow, let it grow).
4. Database. This is the fun one. We have been using MongoDB with pretty good success. Our multi-shard DB has 3 servers per replica set and has them distributed equally between AZs. We use 4 EBS drive RAID-0 drives for storage which have had problems in the past due to the outages that EBS sometimes has. Our best bet has been a watcher process that will kill the mongod process if there's any problems writing to the drive array. By doing this, the replica set will automatically failover to the next server and we won't get stuck with a primary node that can't write back to disk. For backups, we just freeze the writes on the secondaries and do EBS snapshots even 15 minutes. Rightscale has some great EBS tools for managing this for you. If you loose a server, we can deploy a new server in a matter of minutes and it will rebuild the RAID array from the last backup so we have a warm spare.
5. Monitor, monitor, monitor. Rightscale has some great tools for monitoring everything. Use them, and use more monitoring on other infrastructure (ie Pingdom)
Doing something like this will cost a lot more that just sticking to a single AZ, but you should be able to survive one, if not two complete datacenter outages.
I don't think they show how to do ELB across Regions, or diversity against single-ELB problems (although I haven't seen ELB fail yet). You'd probably have to build this yourself.
PHPFog are on AWS and I pay them to make sure they have the redundancy worked out. If they don't, I would yell at them until I got some money back.
I am considering configuring RDS for Multi A-Z, but need to research it a little more first. From what I can tell you just click a button to turn it on, but there were a lot of people complaining yesterday that the fail-over didn't work at all when it was supposed to.
I also have a bunch of EC2 VMs that do back-end processing and have a load of CRON jobs on them that need to run once every 24 hours. If these go down for a couple of hours then there is no noticeable impact to my customers, they can still log into my service and access their historical data.
I have considered spreading across multiple regions etc but at the end of the day it's just too expensive for the small increase in reliability.
1) Has AutoScaling Groups & Elastic Load Balancers in two regions (and only two availability zones; let's keep front-end instances in the same AZ as your local/region-specific DB)
2) Has Databases in two regions and uses Master Master replication
3) Instances talk to their local DB. If they detect their local DB is down, they failover to the remote DB (ie, the far region). If they failover, they notify you.
4) DNS does geographic load balancing (pre-ELB). You'll need to use a provider like DynDNS or UltraDNS to give you Geo Load Balancing & Failover. Or, you could pair a monitoring service like CatchPoint with Route53
5) Application caching (Memcache, Redis, etc). Let's not put more load on the DB's than necessary.
That's a good start, at least.
Marketing and selling software to enterprises is the most dysfunctional cycle of decision making you will ever see in business. In almost all cases the individuals in the business who actually derive value from the technology are entirely disconnected from those who make the purchasing decisions. Many times those purchasing decisions are made based on "perceived" synergies with other software systems already owned from the same vendor, having never been vetted by the actually consumer in the business. Enterprises represent a huge market to be served by well designed/functional applications. Keep in mind that most Enterprise SW contracts have customers paying yearly maintenance charges that are 20% of the original license cost and sometimes more...
The thing to understand in selling into this market is you need to adapt your "logical" marketing and sales strategy to the way enterprises buy. I say adapt b/c you can't make or help a dysfunctional buyer behave differently. These companies like centralizing technology decisions, large multi-year commitments and have complex IT accounting considerations. You need to be aware of their existing legacy infrastructures and have a story of how you "play nice". You need to have partnerships with existing large Enterprise SW companies (IBM, HP, Microsoft, Oracle,etc) and you need to have Rolex wearing sales guys who have the connections and can get deals done - http://techcrunch.com/2010/11/13/new-enterprise-customer/
If you do all that, just moderately well, a large SW company would swoop you up really fast. They can't innovate new marketable products worth crap, all they do is buy. And although we hear about some of those acquisitions there are many, many more that don't get as much press...
However in contrast to the approach above I have been whiteness to a handfull of startup business models that have done really well at infiltrating the enterprise based on their distribution and user engagement model. Take Yammer for example, their model allowed for people in large companies to start using it (for free) without having to get any approval from their IT departments. I had a CIO friend of mine who never heard of Yammer until I mentioned and showed him where over 100 of his company employees were already active on it. Large companies have to worry about compliance, document retention, etc. His first reaction was to block it via the firewall, but then he was smart enough to see it as an opportunity to invest in a technology that had actually been proven to deliver value by people within his own company. Software or services that can get into the enterprise like a cockroach, breed and spread under the radar have a really good chance of getting a CIO's attention in a good way - it's an opportunity for them to invest in a solution that works and guarantees that their business will get value since its already been proven on an small scale.
My first piece of advice is to build up your size and trustworthiness as much as possible. Large companies won't buy from you if you have no standing in the market. That's what you need most, after you have quality software to sell of course.
I'd recommend starting with smaller companies and building up from thereā"the long tail contains a huge untapped market that you can take advantage of and build up your size.
Next, know your domain exceedingly well. Don't show flashy software, solve problems. Find out what the true problems are with their current software, and solve those. Unfortunately, their problem is NOT that their users don't like using it (well, it's a problem, but not the top problem). The top problem is likely that it isn't fully capturing their process, or it misses certain savings or benefits to the bottom line that it should make obvious. Business problems are the real problems, never forget that.
Don't be afraid of investment. Use it to grow when you need to, because your small size will be your biggest downside. Even through all that, never forget that your software quality holds up the rest of your business in the end; you must balance all these factors at once.
And lastly, buy a really sharp looking suit. Sorry.
New school: Self-serve sales winning grass roots support from front line workers. Rewards: high customer loyalty, quick sales cycles, quick feedback, and lower sales costs:
A good general trick is to build something that solves some portion of an enterprise's need, make it free to try out and cheap to use at work. There are a huge number of people out there that can pay some nominal amount for a service and expense it, it's just a matter of finding some need people with that level of autonomy have and getting them to pay you to fix it. Easy, right?
I wouldn't start by trying to navigate the maze, just avoid it altogether until you have a compelling reason to take that burden on.
Note: I have no affiliation with Acceleprise
I think if you don't have the sales rolodex to sell traditional enterprise software going freemium or low cost SaaS is the way to go. Or to team up with some one who can sell into enterprises. You may be able to learn the ropes as you go but that is unlikely. If you look at the background of a lot of the top enterprise software entrepreneurs, you will see that they have worked at other enterprise software companies previously.
Like anything, it is difficult to give a sweeping answer. There are a lot of great opportunities in enterprise software that are worth pursuing. The "hassle" of selling can be reduced by have more consumerized enterprise software but selling will be a big issue. Plus it'll be more tricky as you attempt to sell to larger organizations.
But I don't think that should be a deterrent to building an enterprise software startup--there's room for disruption, and room for good software, good people, and good decisions. There are good organizations out there to work with.
Smart startups can beat the big entrenched code.
That said my co-founder is a great salesman (I'm the techinical co-founder), and having a sales team is high on my priority list.
Instead, look at what Yammer has done with a bottoms-up, freemium customer acquisition approach.
The sales cycle can be/is excruciatingly long. Certain companies that signed on took 1-2 years to get on board after initial engagement.
You need to partner up/find someone who has the deep contacts/relationships in the big cos that would be your clients.
You need to prove to them that it will be cheaper (including the cost of switching, training, etc...), Reduce Risk, and allow them to "reallocate resources."
Inertia is very strong at large organizations. Building a product that directly competes with an entrenched competitor sounds like a very risky endeavor.
But, as dayjobs go, the one I have isn't too bad, and it pays the bills while we work on bootstrapping the startup. So it's kind of a mixed bag. Probably the more troubling part is the sense of the "opportunity cost" of every hour I spend playing code monkey for somebody else, and thinking about the value we could be creating in that hour, and what it could mean to the startup. When I think about that, I find myself getting pretty frustrated. But, I like the people I work with and what-not. And the travel is an opportunity to meet some new people, explore new cities, etc. But, again with the opportunity cost... and travel wears on you in a way as well.
I guess that's a lot of words to say "I have mixed feelings about my dayjob, but it suffices while I work on the startup." :-)
I've given myself 9 more months to replace my salary with consulting and product revenue (hopefully more of the latter). I have dependents, so I have to plot my escape from the cubicle with care.
A lot of us will be interested and happy in our jobs, but we will also have the yearnings to have a crack at entrepreneurship ourselves.
This definetly gives me a bit of an unsettled feeling, and I need to get it out of my system before I can really accept full time employment with 100% satisfaction.
The only thing that would entice me to move would be a job abroad: my family and I are planning a move to New Zealand or Australia in the mid-term future and it would be a fantastic stroke of luck to get a job offer now that would let me work from one of those countries.
I work in an odd environment. It is an academic/research institution, but my role is a standard IT position. I am primarily expected to do system administration tasks and small data management assignments. In general, development is frowned upon. There seems to be a ceiling in opportunity here due to both my "lower" credential (MS rather than PhD) and perception of what my role is by outsiders.
From a more general perspective, I made a critical error when entering the job market at the end of the first Internet boom (early 2000s). I did not take a development job, but rather a test role at a large IT company. It took me several years at that big IT company to realize that this colored perception of my skills and limited internal opportunities despite a MS in CS and significant programming work on the side.
I left for another company where my job role was related to db skills I had picked up but was a greenfield project. That was enjoyable and a learning experience, but the project was cancelled and the entire team laid off in the early days of the financial crisis.
I landed on my feet in my current role. The role has turned out to be quite different that originally pitched to me, but I have a senior title and pay level. The job just doesn't provide much in the way of personal growth.
For family and lifestyle reasons, I will not leave for at least a year. I have been developing some interest in statistics, modeling, and machine learning. While I would prefer not to simply seek another credential, my employer would probably allow me to obtain a MS in statistics at their expense. Perhaps this would lead to more interesting and challenging work, but to be completely honest with myself, my current role is where many people with that background windup anyway.
To somewhat worsen matters, I am often much more attracted to niche technologies (APL,KDB+,J,Common Lisp, Clojure, Ruby) than the market in my area seems to offer employment opportunties for. I probably need to consider re-entering the Java enterprise programming world and not be a prima-donna about programming language.
But early lack of good management and now a chronic lack of resources has turned it into a stressful drag. I'm pretty much angry at everybody all the time now and it's not good on my health or well being.
Looking to move soon, but waiting for company to sell first (imminent). Probably wanting to move to the West Coast -- Seattle or Bay Area next. Probably end of the year is my goal.
We work in a cool office with the other teams and the community is amazing. I absolutely love it. That feeling where you just love coming in and working and spending time with everyone. This helps our product but also improves the quality of life. I do remote work for two other companies to help with living expenses, and the I still like that but it's nothing compared to being a cofounder and getting to do the things that come along with that.
Note: I'm 18, and just one year out of high school so I have some flexibility and can handle a decent bit.
That said, consulting fits my lifestyle well. I get on a project, complete it, and then am done and can pursue some of my other interests (music, poetry, human languages, travel) with a minimum of interference. As a long term solution I think I would kill myself if I had to keep doing this forever, but as a solution to make money for the last couple years it hasn't been terrible.
As of now, however, I am simply unhappy and seeking the next best thing. Creating my own company or joining a fledging startup has always been of interest, but my lifestyle doesn't allow a 60hr/week commitment as of right now.
Happy at a 9-17 job which involves Linux, network, concurrency and C++ and is close to the metal yet still involves a huge set of features. This combination makes it challenging.
Industry that I work with: Semi-happy
Billing rate: Happy
Working for large corporate clients doing challenging but repetitive tasks: Not happy
Bottomline is that I have the "bootstrap a company" itch that I am looking to scratch asap.
Looking into moving to a developed nation.
Couldn't be happier!
Find something that you or someone in your life use--or would use if it just did XYZ. Work on that.
If you have a certain skill set that you're looking to hone, tell us about that and maybe someone could offer suggestions.
I am trying to develop an app/site dedicated to matha matics for kids under 10.
do you like?
Tons of different benchmarks with source code and very comprehensive data for legacy and contemporary hardware.They're free for personal use only. I'm sure you can contact him if you have something commercial in mind.
If you just want to do the occasional comparison, AnandTech has a great Bench page: http://www.anandtech.com/bench/CPU/2
Pick a small(ish) project and go at it in both frameworks. You've said that you have friends who know both, and you've already got a handle on web dev through PHP, so maybe Rails one weekend, and Django the next. Now you know which one you like the best, rather than relying on other peoples' opinions.
You have one really good argument for going with Django: your friends use it. You can ask them tips, talk about it, and they certainly help you in the right direction.
Aside from that, I recommend you to try the Django tutorial, shouldn't take you more than a couple of hours https://docs.djangoproject.com/en/dev/intro/tutorial01/
Also, the small webserver bundled with Django will restart automatically whenever you change a file.
If I had to give my opinion between Ruby or Python; I would say Python, as it is multi-disciplinary. Python can be used for everything from website to high performance computing and have great communities backing them up allowing you to be a more fluid and interesting engineer; Whereas Ruby (and its defacto framework, Rails) tends to be geared towards just web development. Just my 2 cents.
Python while a nice language that I have tried, I absolutely hate the indentation, I hate to have to write code and care about its indentation, I prefer to write my code without caring about it and let my editor format it for me when I'm done or need to read it.
As for Ruby while I can't talk much about the language, the comunity itself kind of scares me, I have the idea that they are some sort of zealots who attack anyone that doesn't use Ruby. (sorry Ruby guys that's the feeling I have), the little I know about the language is that I don't like the syntax much but I am a C like syntax lover.
Now for PHP one of my loved languages (Java and C++ are others), I like the syntax, I like to have braces on my code makes it easy for me to read, but I guess on how much you are used to it, there are some nice libraries too, but some are heavy (Zend is one of them, does a lot but it's heavy), a lot of things that I do are done in PHP, while it may not be the fastest code running, it's one of the fastest to write.
Once again beware, this reflects my way of viewing the languages.
How much value does another similar backend language give?
My thoughts on this would be: Not to much. I would rather look for something that makes you a more interesting engineer. You could e.g. learn to make android apps. That would make you a quite valuable person being able to code mobile frontend and a backend service. Or a backend language/framework that is far different and let's you solve problems that you run into with PHP on high traffic websites. Some companies started using Scala for high performance parts of their service. Or get a good understanding of Apache Lucene a search engine.
But something that is more different from PHP and will make you a more interesting engineer.
There are no downsides to knowing all of these web frameworks, eventually you will find yourself in a position where company X only wants Ruby, or company Y only writes python.
We have a good roadmap of solutions to provide you everything you need to run business. Analytics and a few other useful integrations based on customer inputs is in the works. We are still in private beta working with a short list of customers whom we are working with closely (though we are unable to serve everyone immediately as some of the payment integrations are due to be completed by July / August).
We have integrations readily available with BraintreePayments (US), Samurai (not sure if they still do underwrite new accounts and we did this earlier), WorldPay (Singapore). Authorize.net will be ready in another week.
And we support multiple payment gateway integration. We do not have a vault to store card with us and we store in the respective payment gateway.
Here is the link to our API docs: https://apidocs.chargebee.com/
I am one of the founders and will be happy to help. :)
2.9% feels expensive, but when you realize you don't have to set up any subscriber / coupon code / plan configuration logic, each charge seems a lot less scary.
It's also nice that their pricing is all flat-fee per-transaction.
So, my feedback: it sucks until you implement login that does not rely on a third party that is known for its questionable privacy practices.
After you do that, I would definitely check it out.Well done by the way. "Finishing" stuff is hard and you have launched!
I do have some ideas around guiding the user through the initial experience outside of the initial overlay and get the immediately involved with interacting with others. I think opening up the lines of communication between the users immediately is key.
With regards to the Facebook login I understand your point, hell I've said it myself about other sites, but in this case the entire experience is based on the data from your Facebook profile. It encourages honesty about who you really are and makes it so it is not another profile for you to manage. Without the ability to use the Facebook data you wouldn't be able to have much of an experience. I understand that a percentage will walk away from the site due to that but I'm going to have to focus on the millions of people who do use their Facebook account on a regular basis to login to a third party site.
As for your FaceToFriend site... It is very difficult to figure out exactly what to do after logging in. You need to direct the user (especially a new user) to the key feature/areas. If the "I Want To Talk About..." search box is where you go to get rolling, you have lost already.
1. Are you targeting the iBooks market, or are you targeting the iBooks market? That is: are you competition to Apple, or a potential success story for them?
2. Apple meets interesting companies who are in interesting fields regularly. Biz Dev is a broad title. It can mean any of the following:
i. Hey let's be friends!ii. This is a market we're going to highlight in the next keynote and you might fit in well.iii. This is a market we are keen to exploit more and you're potentially competition.iv. We want to acquire you.v. We want to fuck you, hard.
If you're not sure which of those it's going to be you need to take a long look at Apple's objectives with iBooks and education and work out where you sit on their radar.
3. Don't give anything away that Apple couldn't already have reasonably worked out. Talk about the size of your team and your experience in this market, but don't talk about investment or investors. If they ask specifically then just politely say that its' confidential, and that you're sure someone from Apple can understand that.
4. Be passionate about the public side of your roadmap. Discuss the key problems and the solution you have to them. Have answers to the challenges you're likely to face (I guess traction is one).
Don't ask about Apple's plans because they won't tell you anything. However, do think about things that Apple could do that would help you get into this market and really open it up. Frame some questions around that if you can.
Sorry this is a little broad. I don't think you're naive enough to be expecting an acquisition or something, but you should also be prepared for the fact that they will probably speak to 100 companies like you every week, just so they have you on file.
I know that CentOS/RHEL 6 was affected, but CentOS/RHEL 5.5 (kernel 2.6.18) was not.
So I guess it's just a coincidence, a bug was introduced in a code path that's rarely executed and so lay dormant for some time, gaining more and more victims as time went by and people adopted kernels containing said bug.
The overall outcome was a third of the class ended up either getting acqui-hired or taking additional investment, a third is still bootstrapping, and everyone else scaled things down to a side business or just faded away.
But then things started to catch up. And we know the rest. Question is will history repeat itself this time too? Will Android continue to improve over iOS and its high adoption rate turn it into the only mobile OS that matters, like how Windows was? I believe Apple has its strategy to prevent it from happening. That might be why it's pricing its tablets so strategically.
Ultimately everyone will get the answer, over time. But whoever can predict the future best can make the most profit out of it. Specially we, the software developers.
So for example, show that for every signup you know:1. Where your users come from (e.g. referer)2. Where your users are from (e.g. geo location based on ip)3. User Agent, Browser, Mobile vs. Desktopetc...
This information is not only "cool to know" but also useful to understand who your potential customers are.
A few more things. In your "sales pitch", you mention your competitors (e.g. LaunchRock/Unbounce). I wouldn't suggest advertising for your competitor, and loosing potential customers to them, especially if you're value proposition is weak.
Finally, I wouldn't suggest your "call to action" to be to see pricing, that's also a turnoff. Instead, maybe you ask for emails for people interesting who want to use the beta when it's ready :P