61–70 of 355 posts
Reminded me of these similar threads I read a while earlier: Azure: https://web.archive.org/web/20190321175020/https://www.exped... https://news.ycombinator.com/item?id=13442597 AWS: https://expeditedsecurity.com/aws-in-plain-english/ https://news.ycombinator.com/item?id=10202286
Similar to https://expeditedsecurity.com/aws-in-plain-english/ Why does AWS use such convoluted language? Is it because they're dominant and it adds friction to moving to another provider?
Kubernetes Engine, Compute, Storage, Memory Store, Cloud SQL, PubSub.... almost all of the main services do what they say on the tin.
The only downside is - ironically - it sometimes makes googling for help a bit tricker. Eg. Are you search for generic cloud storage or the Google product with the same name?
"Large & scalable non-relational database (but not really a NoSQL system)" triggered
Ha, that caught my eye too. I'd say DynamoDb is kind of the poster child of the whole NoSQL thing.
Is there something similar for Apache projects?
Earlier quoted context omitted.
Have you ever used AWS? There's a whole suite of tools they provide around pricing and budgeting. > It's quite a tour de force how Amazon have taken "separation of concerns", applied it to web services and used it to create complex and difficult to understand or predict pricing to print money. Is applying separation of concerns to web services really that bad? Look, if you're a small company with a simple product, yo…
> There's a whole suite of tools they provide around pricing and budgeting. It could be there are such tools. But they are impossible to find, setup or understand for someone who is not already an AWS expert. I recently got a $500 bill from AWS. It was impossible for me to find out which S3 buckets (or even specific files) caused these costs. I looked at this for half an hour and have used AWS before. They just don't…
EDIT: sorry, I forgot to include the screenshot link - https://imgur.com/a/tVFoocr
Earlier quoted context omitted.
> There's a whole suite of tools they provide around pricing and budgeting. It could be there are such tools. But they are impossible to find, setup or understand for someone who is not already an AWS expert. I recently got a $500 bill from AWS. It was impossible for me to find out which S3 buckets (or even specific files) caused these costs. I looked at this for half an hour and have used AWS before. They just don't…
It's literally called "Billing" and the "Cost Explorer" is the first item in the navigation when you go to the page. I've attached a screenshot and highlighted it for you. FYI, this month is the first time I've opened the AWS GUI in 4-5 months, and it took me about a minute to find the billing page and drill into our AWS costs. I've provided an image that shows how to get to the cost explorer from "Billing" (you can…
Consider that your typical enterprise software project will use quite a lot of these, and that you pay for them all separately, and sometimes pay twice for them (e.g. S3 you pay for storage and for outbound bandwidth). It's quite a tour de force how Amazon have taken "separation of concerns", applied it to web services and used it to create complex and difficult to understand or predict pricing to print money. Bravo.
Have you ever used AWS? There's a whole suite of tools they provide around pricing and budgeting. > It's quite a tour de force how Amazon have taken "separation of concerns", applied it to web services and used it to create complex and difficult to understand or predict pricing to print money. Is applying separation of concerns to web services really that bad? Look, if you're a small company with a simple product, yo…
Yes, I use it extensively.
> Is applying separation of concerns to web services really that bad? Look, if you're a small company with a simple product, you can just put your stuff on a few EC2 boxes and pay the monthly bill for that. At that size, your infra costs are going to be dwarfed by your other costs of doing business anyway. If you're a big business, you can literally pay people to keep track of this stuff. You've got the extra money, because now you don't employ data center architects, server engineers, etc. AWS is able to "print money" because it brings a lot of value to many businesses.
It's not bad per se. The real problem I often see is that many people within the typical org aren't aware of how these costs can accumulate, especially when you have multiple DTAP environments, microservices, and so on.
Another problem is the days of "put your stuff on a few EC2 boxes" seem to have been overtaken by the cloud native, microservices, k8s trends of the last few years. Personally I 100% agree this is the way to go for many (if not most) people -- and for this purpose Digital Ocean is just as good -- but what I see more often is people diving straight into the deep end, because "Is applying separation of concerns to web services really that bad?"
I also think even big businesses underestimate the total costs of these all-in cloud infrastructures. You indeed need to pay people to keep track of this stuff -- multiple people. Your cloud costs + your devops/platform personnel costs can get to be a significant % of your total IT costs. Is it really necessary?
Just because your business has a big market cap or significant revenue from digital doesn't necessarily mean it needs any of that stuff. Chances are you can run it all on the same couple of EC2 boxes you ran it on when you were still a small company.
Earlier quoted context omitted.
Have you ever used AWS? There's a whole suite of tools they provide around pricing and budgeting. > It's quite a tour de force how Amazon have taken "separation of concerns", applied it to web services and used it to create complex and difficult to understand or predict pricing to print money. Is applying separation of concerns to web services really that bad? Look, if you're a small company with a simple product, yo…
> Have you ever used AWS? There's a whole suite of tools they provide around pricing and budgeting. They don't work. To elaborate, they fail to provide the user with information with enough clarity to allow him to form accurate mental models of what is being used,what it costs, and what is the implication in cost of applying some change. Heck, at any given moment it's unexplainably hard to tell exactly which AWS serv…
Did you actually look at the billing page? Here's a screenshot of my billing page:
It meticulously breaks out per-service costs across whatever dimension you want. "EC2-Other" is rolled up in the chart, but it's broken out by each individual item further down in the list.
I see that AWS IoT Greengrass is missing. https://aws.amazon.com/greengrass/ I may be wrong but from what I understood, it's more or less a way to manage AWS Lambda functions (cgi-bin scripts), Docker, and a MQTT client connected to AWS on your GNU/Linux devices (raspbian on a raspberry pi for example, or a x86 pc). However you still need Ansible or similar to manage the device so the actual value is kinda low becaus…
The whole lot of IOT services are pretty confusing. Mostly because I have no experience with IOT/MQTT in general and it took a few days to actually figure out how to create and connect things (emulated). I actually bought some IOT devices (lamps, sensors) to try it out, but this turned out to be vendor-locked without any possibilities for MQTT. I reckon somebody with more experience in the IOT field could provide mor…
IoT Core: Managed MQTT broker, and state management for devices with intermittent connectivity
FreeRTOS: RTOS operating system for microcontrollers to automatically connect to IOT-Core or greengrass.
IoT 1-Click: Manage 1-click buttons that can be connected to other systems like Lambda
IoT Analytics: Clean up and save messages from topics into a data-store for analytics
IoT Device Defender: Automated detection of misbehaving devices
IoT Device Management: Firmware release management
IoT Events: Visually build automation rules based on device data
IoT Greengrass: Run Lambda functions on remote devices, and manage release of new versions.
IoT SiteWise: Turnkey industrial automation platform
IoT Things Graph: Represent IoT devices in terms of connectivity - for example a door sensors connects to a hub, which has an internet connection.
And one bonus definition:
AWS Sumerian - A 3D game engine integrated with AWS services.
Not particularly helpful if you have no idea what a VPC is! Of course it takes 2 seconds to search this for yourself, but still.