This is the correct answer. I (and many others) used to work near there. That mall wasn’t very useful and located on the edge of Union Square and a rough neighborhood. Reduce foot traffic from office dwellers by 50% and you basically kill Union Square retail. Drop tourism by however much that’s fallen and that’s the end of your mall. The dystopian takes are overblown, but the city needs a plan for a world with fewer people working along Market Street.
A lot of this discussion reminds me of this talk:"Netflix built its own monitoring system - and why you probably shouldn't"
(https://www.infoq.com/presentations/netflix-monitoring-syste...) where Roy Rappport describes Netflix as a "monitoring system that happens to stream movies"
As someone who spent a few years at New Relic and Lacework, I can also say that pricing observability fairly is crazy hard when you account for different architectures, usage pricing, and the humans experience the value.
+1 Amazon has always been a "lower margin" business. One argument for why and how AWS beat all the tech vendors to the punch was that everyone else had businesses build on higher margins (Google, MSFT, Oracle, VMware, etc). Now that AWS delivers most of Amazon's current profit, it will be interesting to see if Jassy asks for more margin out of them or tries to find it in other parts of the business.
This is a good point. Expecting developers to understand how to configure service to service IAM permissions and all the other nuances of AWS infrastructure is a fool's errand. Also one of the reasons we started Stackery.
The issues highlighted in this thread around the need to develop locally against cloud resources while dealing with a litany of dependencies are one of the things we are trying to solve at Stackery.
This is, unlike most plugs, actually not bad; the tool looks neat. But I am not your audience. I already have a strong grasp of AWS offerings and tools and know exactly what I want; what I don't have is the inclination to do it for development. If I did, I have Pulumi when I need to build cloud infrastructure and I'm allergic to visual tools at pretty much every level that isn't literally making a GUI.
The problem that I have, and it is probably intractable is 1) I don't want to manage developers YOLOing dev stuff around at work and having a gigantic bill show up because a developer randomed something expensive and didn't know/didn't care to monitor it, and 2) I don't want to deal with the expense or the slowness (of deploys and redeploys, and that includes the AWS resources--ever gone "ugh, I need to burn this down and start fresh" on a dev environment in AWS? it takes forever) of using AWS for development on personal projects.
Thanks for replying with your initial reaction. It's good to get your perspective.
Visual tools:
If you are proficient at writing CFN templates or have found another tool to do that, cool. FWIW, our customers tell us they find the visualization useful when onboarding other engineers onto a project and then when they have a split screen between the template and the visualization to see how the CFN template is built.
Yoloing Developers:
Heh. I'm stealing that phrase. But seriously, this is a common concern and a reason why managing accounts and namespacing for dev/test/staging/prod environments is a big deal. (plug - we do that too) At AWS dev managers get daily reports on the cost of each developer's accounts. While serverless tends to be much cheaper for dev environments than containers or EC2 instances, there are indeed ways to run costs up.
Deploying and redeploying:
That's precisely why our CLI enables development against live cloud resources. When you use stackery local invoke, it assumes the function’s IAM role and fetches the function’s env var values. This enables rapid, and accurate, local function development. On the infrastructure side, it's common for our users to make up to 5 or more changes to their architecture in a day. The more you can do with the building blocks, the less code you need.
Say more sir. I like the non-toxic spin, pricing seems good, and yet, by the bios on your "about us" page it seems like you are very marketing oriented. That's fine, but perhaps enlighten the mass here on how you struggle or over come some of the objections raised above? Personally, I despite mattress retailers, but I also want to lie down on the thing before I commit to spending 30% of my life on it.
Two outstanding questions:
1. Can we be done with the advertizing business models please?
2. How much did the Facebook IPO really shift the private equity market?
