...and all Marakana's videos have disappeared from the net.
I have many links to videos from JAXConf2013, the SF Java User Group, the 2012 Northeast Scala Symposium, etc. and they now all redirect to https://marakana.com/ - a single page announcing their acquisition by Twitter.
Fair enough - I had considered that to be on the axis since it's the minimum value, and thus not a tick, but visually it certainly is represented as a tick.
At any rate, the point I was trying to make is that they clearly expect you to throw a lot of hardware at these systems.
Sure, but a lot of projects LIKE this have an open source project for those people NOT in the enterprise, and who probably won't be running more than 8-24 cores or so.
On a related note, changing the amount of RAM seems to only change the amount of RAM, not any of the other numbers. I guess that's their point, but I would rather they just SAY that than make me try a bunch of options to show that RAM doesn't matter. :|
I think the "half an hour" bit is significant. If someone complained that they tried to learn Prolog and gave up after half an hour they wouldn't get much sympathy from me.
Nice presentation. In the description of back end modules, you mention payments as a future capability. What kind of payment service would you be able to work with? (I don't see how you could handle card details in the Hoodie architecture). Thanks.
we definitely won't send any credit card information to a hoodie server. Instead we use a service like stripe, but then receive the payment notifications or errors, which lets us notify the user if payment worked or not.
A good solution should also minimise movement, to conserve energy and reduce mechanical wear. And part of the orbit is in darkness - the criteria would be different there (not optimising illumination, but needing to be ready for the return to daylight).
If you have to do this, you could check that the published time was >= the time at which you started the test, and <= the time at which you are doing the check.
