trilobyte wrote:You're missing a couple fundamental things.
1) The BMOrg doesn't handle the ticketing for the event.
2) Nobody asked you.
I'm kidding, though seriously nobody was asking about how to increase capacity. Stay tuned for the FAQ regarding the changes to the ticket policy, it's coming soon. If you've got technical advice or suggestions for InTicketing (assuming that's who will handle ticketing this year), you may want to reach out to them via their site.
Zakolantern wrote:Either I'm missing a very fundamental concept, or in the last few years, services have grown mature to completely solve the issue of huge spikes in website traffic / server load. Led by Amazon.com's EC2 ( http://aws.amazon.com/ec2/ ) , but including tons of other offerings, from companies like GoGrid, Rackspace, Joyent, etc, it's now very easy to rent very temporary, very inexpensive, dynamic server instances in what's become known as Infrastructure-as-a-Service (IaaS).
I see no major cost or other practical reason why Burning Man should have its servers go down even if it experiences 10,000x its normal website traffic when it releases tickets.
Do others agree with this, or see a problem with what I'm proposing?
MyDearFriend wrote:I can't believe I'm taking shit from a meat-cake-with-teeth. :lol:
trilobyte wrote: If you've got technical advice or suggestions for InTicketing (assuming that's who will handle ticketing this year), you may want to reach out to them via their site.
jkisha wrote:trilobyte wrote: If you've got technical advice or suggestions for InTicketing (assuming that's who will handle ticketing this year), you may want to reach out to them via their site.
The only advice I have for anybody about InTicketing is that BMORG should have dumped them two years ago.
igor47 wrote:There are lots of solutions to horizontally scaling a ticket-selling app, and most of them are pretty easy. InTicket is just kinda bad at technology, which is consistent with BMOrg being generally really bad at technology (exhibit 1: BM rideshare; exhibit 2: the forms site for theme camps/MVs; exhibit 3: the playa registration system; etc....).
I just checked inticketing's website. They want help with their site so much that their 'jobs' link is a redirect loop which just ends up giving you a browser error. I sent them a message anyway, but I'm not holding my breath.
portaplaya wrote:I dont' think that Burning Man is saying that web server demand isn't solved.
I think they are saying that last year's first day of ticket sales indicates that all of the tickets will sell out in day-one. And without some system to fairly distribute the buying opportunities within that one day, the perception of hideous unfairness will be a dark taint.
A lottery allows them to do that more fairly, and also functions as a workaround from any mishaps that web technology might run into.
Burning Man said they were creating a new process because: "2011 provided two compelling reasons to change how tickets are sold: a challenging ticket launch day, and then, our first-ever sold-out event." I feel that this is different than saying "we can't handle web server demand."
stretch80 wrote:Only 27,000ish tickets of the 50,000 sold in the first day and then it took over 5 months to sell the rest. I doubt they expect to have 50000+ people try and get tickets on the first day.
Users browsing this forum: No registered users and 2 guests