1,230 karma · joined April 30, 2009
My point was just that it doesn't have to cost over $1k on Amazon to run a combination of services which apparently CAN run in a private lab for $5/mo, however that is calculated. I can't run my full stack even without load (due to memory commit) on my 32GB, 3 year old Xeon workstation, and that would cost a lot more than $5/mo at any provider I am aware of.
And yes, bandwidth costs can be brutal, especially if you try to build a hybrid solution that uses heavy services that live outside of AWS.
That said, the above comment didn't get into enough detail to get an accurate read on their bandwidth or CPU/Memory/Storage utilization, but if they can run it in a lab for $5/mo (which I doubt, since that barely covers power), then it can't be much, so I think it's fair to assume it's at least back-of-the-napkin similar scale.
* AWS MSK (Kafka server) with redundant instances across 3 AZs
* Aurora Posgres instance with redundancy across 3 AZs
* Multiple Lambdas for incoming messages from MQTT to Kafka
* IoT/MQTT and about a dozen iot devices sending telemetry continuously (every second)
* 20+ services with nearly 40 tasks, running on ECS
* All the supporting route53, certificates, VPCs etc. for the above
* A bunch of miscellaneous stuff I've forgotten that's used by other developers.
* All deployed via TF
_THAT_ all costs well under a grand. You're doing it wrong.
I'll also ask (since nobody else has answered, I may as well ask you as well):
1. Are the customers actually being restored from backups (and additionally, by a standard process)?
2. Will the recovery also include our integrations, API keys, configuration and customization?
1. They can confirm that they have backups of our data (about a thousand stories, substantial confluence, opsgenie history, and three service desks).
2. Will our integrations, configuration, and customizations also be recovered, or will we need to rebuild those once our data is recovered?
I have received no response, and no human is even willing to acknowledge those questions. The service desk staff ignore them as if I never asked. Repeatedly.
Also, I've been asking around, and haven't been able to find a single story from somebody that can confirm that they were down, who has had their data recovered.
Worse, outside of "we have rebuilt functionality for over 35% of the users", I haven't seen any reports from the people who have ostensibly been recovered.
Next, their published RTO is 6 hours, so obviously they must have done something that completely demolished their ability to use their standard recovery methods: https://www.atlassian.com/trust/security/data-management
Finally, there have been some hints that this is related to the decommissioning of a plugin product Atlassian recently acquired (Insight asset management) which is only really useful to large organizations. I suspect that the "0.18% impacted" number is relative to ALL users of Atlassian, including free/limited accounts, and that the percentage of large/serious organizations who are impacted (and who would have a use for an asset management product), is much higher.
"Now that we've established unstoppability as a net new feature, I’ll make my most speculative and contentious proposition: Hyperstructures can be simultaneously free forever to utilize and extremely valuable to own. This is possible because of their unstoppability. There is no cost to maintain and keep the protocol operational forever."
You heard it here first folks. The code maintains itself, forever. This is obviously naively optimistic at best.
Further "free forever to utilize": Servers are free now? Switches, networking, power? There are costs, even if they aren't high. At best those costs are externalized to stakeholders beyond the majority of the user-base.
Every time I read about one of these "unstoppable systems" which avoid the existing financial system, I find myself wondering if the theoretical freedom that grants is worth the risks it imposes.
Yes, Catia was a PITA to use and support, but it was productive in the right hands. PTC Pro/E was also a PITA to use, but very productive for experts. His outright dismissal of Solidworks is hard to reconcile with my personal experience using it to design components over the last 20+ years. These workflows might be different from his preference, but that doesn't make them invalid.
The referenced article about the failed promise of parametric modelling does have a good point though, although I don't think it's fully expressed: modification of an existing design in parametric CAD feels like it's a lot more difficult (and likely to blow up) than a software project of similar complexity. Perhaps this is inherent complexity? I'm not sure, but I do find that it's easy to get caught in a trap of endless circular revisions on related parts for what feels like a simple design change sometimes.
If on the other hand, you have multiple devs, committing changes, and applying them, then you need something like TF to ensure that the applies are consistent, ordered, and auditable.
For personal use? You don't need TF cloud, but the problems it solves get obvious as you scale up.
aws iam list-policies
An error occurred (503) when calling the ListPolicies operation (reached max retries: 2): Service UnavailableMaybe not, but how likely is it that they'll continue funding more studies if you come back with results that don't support more beef consumption?
Sorry, don't mean to be overly cynical, but <gestures around at basically everything>.
You might have been able to improve some small aspect of the mobile demo that would have prevented the crash (ie: error handling on that field), but your C-team was obviously playing Russian roulette, and if the demo hadn't blown up, then attempting to productize it almost certainly would have.
In a way, you should feel better about the outcome you got; your CTO was obviously trying to bluff the investors that there was more product maturity than actually existed. If he had succeeded, he would have burned through a bunch of other peoples' money, and the outcome would have still been failure.
They've been proven to discriminate, in a court of law. I'd give this new lawsuit the benefit of the doubt.
People will believe feelings if they can't figure out the truth, sure, but that doesn't mean we have to tolerate fantasy over fact, and we shouldn't allow those people to make policy decisions. I mean, clearly we HAVE, but we shouldn't.
Too bad they only traded out 684BTC. Hope they held.
Also, I am still not sure if this is a disclosure, performance art, or extremely dry comedy, but it certainly covered all the bases.
The post you replied to was about change for change's (and profit's) sake, to which you responded that that was the case for disc brakes, along with calling them stupid for racing.
Again, if you prefer them, aesthetically or otherwise, that's fine. They're not stupid though, or are they a money grab.
There is a lot of fud about discs in the road-biking circles, but it doesn't really hold up to scrutiny.
If you have rim brakes, and you like them, then great! Don't malign them because you dislike change though.
I am not saying that Google is going to kill core product offerings like K8S... what I am saying is that they lack focus, and change direction without regard for their customers. That, coupled with their famously bad support means that I can't sleep at night with the confidence that I can build a complex product on top of their offering. I'll always be worrying that I have to rip out or re-architect large parts of my code to deal with their lack of product stability.
As for the legal warning, I feel like their lawyers are about as competent as their web designers in that regard.
But, that all said, is this _really_ the hill you want to die on? They can be wrong and still cost you a fortune.
Is it really not cool to wish that developers would get compensated for their time if their work is valuable?
I understand that the developer chose the license and distribution model, but if they hadn't chosen this model, then the community would have settled on whatever the best solution was that was permissive enough that they didn't have to pay for it. Passion projects in OS are a race to the bottom compensation-wise, due to dynamics outside of the control of the developers building them.
The description sounds too similar to be a coincident. Not saying it's the same person, but the same pattern that's described in the article (which was apparently repeated at a bunch of different companies as a standard practice).
Every time I read about one of these projects, I am at once SUPER THANKFUL for the time that this person puts in, to improve a project that I depend upon daily, but also somewhat incensed that there are thousands of large corporations that have a dependency on this stuff that they aren't giving back any support for.
link rel: https://curl.se/donation.html
I am not a Curl contributor, or related to the project, but I do donate.