Is there something similar for Apache projects?
My awesome open-source data engineering list [1] covers a few Apach projects. Contributions welcome!
[1] https://github.com/gunnarmorling/awesome-opensource-data-eng...
AWS services explained in one line each
71–80 of 355 posts
Re: AWS services explained in one line each
#72Earlier quoted context omitted.
> 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…
> Heck, at any given moment it's unexplainably hard to tell exactly which AWS services are you actually using, and being billed for. Did you actually look at the billing page? Here's a screenshot of my billing page: https://imgur.com/a/DQAxgRY 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…
Isn’t that exactly what the person you replied to said? You’re showing what you’ve been charged for previously. That part works, at a certain level of detail.
That doesn’t show what you are being charged for right now, nor does it help you predict what your total costs will be at the end of the month.
Re: AWS services explained in one line each
#73Earlier quoted context omitted.
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…
This does not show the costs per bucket . Specifically, I was interested in the costs for data transfer for each of my buckets. As I said, after half an hour of looking into the "Billing" in AWS, the Cost Explorer and googling around I simply could not find a way to obtain this information.
If this is an ongoing issue and you can’t get the information from something that is in front of S3 (cloudfront/your application etc) then you can enable bucket logging in the settings (which costs!)
Re: AWS services explained in one line each
#74Earlier 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…
You can get cost breakdown on a more granular level by taking advantage of tagging. You can tag your resources logically and get a break down by tag.
The biggest mistake I see is that people jump into AWS whole hog without doing the research or if they are large enough, hiring someone who knows what they are doing.
https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2...
Re: AWS services explained in one line each
#75Earlier 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…
You can get cost breakdown on a more granular level by taking advantage of tagging. You can tag your resources logically and get a break down by tag. The biggest mistake I see is that people jump into AWS whole hog without doing the research or if they are large enough, hiring someone who knows what they are doing. https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2...
I don't understand why I even need to do manual things such as "tagging" (besides learning what that even means in AWS) to find out something as simple as why I'm being charged as much as I'm being charged. I'm sorry. It's inexcusable.
Re: AWS services explained in one line each
#76Earlier 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. 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 bu…
I think we are probably 90% in agreement on things, just talking about it in different terms. I think AWS/GCP have both gotten overwhelming in terms of how many different services they provide. Many people fall for it and end up playing AWS service golf (https://news.ycombinator.com/item?id=23274668).
Maybe a good analogy is to think of AWS as C. It's flexible and powerful, but it's easy to shoot yourself in the foot. That would explain why a lot of these "> magical-tool deploy" services have emerged, promising to abstract away AWS.
Re: AWS services explained in one line each
#77Similar 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?
I think it's because naming things is hard, that link proves it by coming up with worse names for almost everything they tried to rename, and often far, far worse. Imagine the confusion if S3 were called "Amazon Unlimited FTP Server." That gets every word wrong, except that "Amazon" is merely redundant. It's not unlimited (having to pay for a thing is a limit), it's not using FTP, and it's a service, not a server. Or…
Services like S3 are referred to as „object storage“. AWS Lambda is a service for „serverless compute“ or „function as a service“ (although it‘s debatable if these are good names for the concept).
My point is that definitely are named for these concepts but AWS uses brand names which is quite confusing for people who are new to AWS.
Re: AWS services explained in one line each
#78Similar 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?
I know the ins and outs of AWS pretty well, but when I see discussions about Azure or GCP, I’m completely lost. It’s not like I’m a stranger to the development side of the Microsoft ecosystem. I’ve been developing in C# for over decade and have used Visual Studio since 1997.
Re: AWS services explained in one line each
#79> VPC Create your own VPCs within AWS 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.
Isn't VPC a wel known term? I guess the author just included that definition to make the list complete.
Re: AWS services explained in one line each
#80Earlier quoted context omitted.
I think it's because naming things is hard, that link proves it by coming up with worse names for almost everything they tried to rename, and often far, far worse. Imagine the confusion if S3 were called "Amazon Unlimited FTP Server." That gets every word wrong, except that "Amazon" is merely redundant. It's not unlimited (having to pay for a thing is a limit), it's not using FTP, and it's a service, not a server. Or…
Services like S3 are referred to as „object storage“. AWS Lambda is a service for „serverless compute“ or „function as a service“ (although it‘s debatable if these are good names for the concept). My point is that definitely are named for these concepts but AWS uses brand names which is quite confusing for people who are new to AWS.
It makes it a lot easier to search for on Google though...