News for hackers. Stuff that matters.
Re:So many bad takes. Learn from the Prime Video microservic... by emodendroket on Sunday May 07, 2023 @04:37PM (#35855404)
> I make money from porting people off of poor technical choices onto solid ones

So it was successful enough for long enough to get them to the point where someone cared about optimizing and paid you to come in, right? I don't see how you are disproving the article's argument that this is a great way to prototype ideas or get a first version of the product out there.

Re:So many bad takes. Learn from the Prime Video microservic... by rat9988 on Sunday May 07, 2023 @04:52PM (#35855508)
"So it was successful enough for long enough " Which doesn't necessarily make it a good choice at any point. It just says it wasn't enough of a bad technical choice to make the product sink.
Re:So many bad takes. Learn from the Prime Video microservic... by emodendroket on Sunday May 07, 2023 @05:01PM (#35855557)
OK, sure, it's not ironclad proof that it was the right decision. But it's certainly not proof it was the wrong decision when it was made.
Re:So many bad takes. Learn from the Prime Video microservic... by namaria on Sunday May 07, 2023 @05:18PM (#35855695)
"It works and makes money" is at the root of so much shoddy workmanship in software I think you're making a different point than what you're trying to.
Re:So many bad takes. Learn from the Prime Video microservic... by emodendroket on Sunday May 07, 2023 @11:53PM (#35857894)
The argument of TFA is that starting with serverless and evolving away from it bit by bit as it is revealed to be necessary is a sound strategy most of the time. Whatever you may think of that argument, “I have been hired to optimize projects built using serverless and get them off of it” is not a rebuttal.
Re:So many bad takes. Learn from the Prime Video microservic... by namaria on Monday May 08, 2023 @02:23AM (#35858700)
Thanks for rehashing how this thread got started for me?
Re:So many bad takes. Learn from the Prime Video microservic... by emodendroket on Monday May 08, 2023 @03:10AM (#35858926)
What is this different point you think I’m making then?
Re:So many bad takes. Learn from the Prime Video microservic... by namaria on Monday May 08, 2023 @05:36AM (#35859746)
>this is a great way to prototype ideas or get a first version of the product out there

As long as it works and makes money it excuses shoddiness. Publishing a draft to fish for revenue is the reason we have so much poor software running out there. After it's in production, you will not be able to make a business case to re-make it right.

Re:So many bad takes. Learn from the Prime Video microservic... by emodendroket on Monday May 08, 2023 @10:55AM (#35862217)
Apparently you will since the other guy in this thread has made this a specialization.
Re:So many bad takes. Learn from the Prime Video microservic... by re-thc on Monday May 08, 2023 @12:13AM (#35858004)
This has nothing to do with software. Same applies for things like buildings where the developers get away with so many defects even after people pay huge $$$ for it.
Re:So many bad takes. Learn from the Prime Video microservic... by jpgvm on Sunday May 07, 2023 @04:52PM (#35855512)
My opinion from doing both these ports and greenfield is this:

None of the tools that say they help you move faster matter after the first 3 months.

It's true they take less code and pieces to get started with. No k8s manifests, no Dockerfiles (usually) but if you don't hate your future self you will still use IaC to create the API Gateways/function contexts/DynamoDB/whatever, so you will still be dicking around with at least one of Terraform/Pulumi/similar.

The thing is the setup cost of a traditional lang + pg + k8s setup amortised over 3 months is essentially nothing and yet you have a setup that will last you effectively forever.

If your company wasn't going to die because of being a few days slower in that initial 3 month period you have came out ahead. You have a forever architecture and you avoided a whole bunch of costs and technical debt in the process.

Maybe the calculus is different if you don't have the same depth of infrastructure experience I do but for me it's obvious this is a faster and better way of delivering a prototype that gives it proper room to grow into production software.

Re:So many bad takes. Learn from the Prime Video microservic... by emodendroket on Sunday May 07, 2023 @05:05PM (#35855584)
I am more of a generalist than you are but I have worked with a Kubernetes setup and I've also worked with going all-in on Lambda and other AWS services managed by CDK and I don't share your intuition. Besides the initial setup, the former also has other ongoing maintenance things that are harder to deal with. It does give you more flexibility if whatever you're doing isn't a good fit for those tools, though (though obviously nothing stops you from provisioning EC2 instances or whatever through other tools).
Re:So many bad takes. Learn from the Prime Video microservic... by Aeolun on Sunday May 07, 2023 @10:38PM (#35857505)
I have a hard time imagining anyone doing anything non trivial with CDK and walking away happy.
Re:So many bad takes. Learn from the Prime Video microservic... by emodendroket on Sunday May 07, 2023 @11:51PM (#35857882)
Why? Do you have something specific to say about why you dislike it? I think it’s pretty good.
Re:So many bad takes. Learn from the Prime Video microservic... by scubbo on Monday May 08, 2023 @12:21AM (#35858055)
Oddly I'm not able to reply directly to re-thc, so I hope you don't mind me commenting here that - I suspect that they're not deploying with a CDK-defined Code Pipeline (starter article[0], in-depth example[1]), which makes cross account/region deployments so ludicrously smooth and simple that it often has newbies refuse to believe that it can have worked _that_ easily.

It is true that _some_ resources don't have L2 constructs, but there's pretty damn good coverage of the most popular services - and, even when you have to drop back to L1, that's still better than hand-written CFN templates or abandoning IaC entirely!

[0] https://docs.aws.amazon.com/cdk/v2/guide/cdk_pipeline.html

[1] https://pipelines.devops.aws.dev/

Re:So many bad takes. Learn from the Prime Video microservic... by emodendroket on Monday May 08, 2023 @12:23AM (#35858067)
If the reply link doesn't appear you can still reply by clicking on the timestamp. I don't know why it works that way.
Re:So many bad takes. Learn from the Prime Video microservic... by scubbo on Thursday May 11, 2023 @01:23AM (#35897920)
Odd - it's showing up now. I'll remember for next time. Thanks!
Re:So many bad takes. Learn from the Prime Video microservic... by re-thc on Monday May 08, 2023 @12:11AM (#35857990)
Cross region/account usage is terrible. It's also 1/2 baked. Some things have higher level constructs but some don't. Lots of things have to be "escaped" to get it to work.

If you're just on a single region/account then yes it's better than alternatives.

Re:So many bad takes. Learn from the Prime Video microservic... by scubbo on Thursday May 11, 2023 @01:23AM (#35897917)
I suspect that you're not deploying with a CDK-defined Code Pipeline (starter article[0], in-depth example[1]), which makes cross account/region deployments so ludicrously smooth and simple that it often has newbies refuse to believe that it can have worked _that_ easily.

It is true that _some_ resources don't have L2 constructs, but there's pretty damn good coverage of the most popular services - and, even when you have to drop back to L1, that's still better than hand-written CFN templates or abandoning IaC entirely!

[0] https://docs.aws.amazon.com/cdk/v2/guide/cdk_pipeline.html

[1] https://pipelines.devops.aws.dev/

Re:So many bad takes. Learn from the Prime Video microservic... by Aeolun on Monday May 08, 2023 @12:26PM (#35863514)
It’s just… half baked. It feels like the CDK team constantly has to work circles around the lacking functionality in CFN. Want to upload a docker image to ECR, use this hacky lambda function. Want to create an object in an S3 bucket? Use this other hacky lambda function.

Then a lot of the resources depend on each other in funky ways, but they’re not always implicitly defined, so whether everything will be created in the right order is anyone’s guess and you often have to define the dependencies manually anyway.

Then when it fails to bring up/modify a stack you get the helpful message that resource x failed to create, but nearly never why.

Like, CDK is marginally better than plain CF, but something like Terraform or Pulumi is so much better that it’s hard to imagine anyone would want to use anything else.

Also, like someone else said, the stacks are directly bound to specific accounts/regions. When I bring domething up that is my QA environment, I’d enjoy it if I didn’t have to split every stack in twain (cloudfront certificates that can only be in us-east-1 or something).

Oh, and when you finally work through all these issues and work on your app for a few months, the dreaded message will come up… “Maximum of 500 resources in stack reached”.

Now enjoy splitting it all up.

Re:So many bad takes. Learn from the Prime Video microservic... by scubbo on Thursday May 11, 2023 @01:34AM (#35898004)
> It feels like the CDK team constantly has to work circles around the lacking functionality in CFN. Want to upload a docker image to ECR, use this hacky lambda function. Want to create an object in an S3 bucket? Use this other hacky lambda function.

It feels like you have a different boundary of what constitutes "infrastructure" than the CDK team do. I'd call both of those examples content _within_ an infrastructure component. Would you expect CDK to initialize an SQS Queue with a message on it? Or a DynamoDB table with data in it? I guess you could make that argument, but to me _populating_ your infrastructure is a very different task from _making_ it - it's an application-level task, not a infrastructure-level one.

Most of the rest of your comments are pretty subjective - I can't say I agree with most of them or have experienced them, but I also don't disbelieve you that they've happened to you.

Not sure what you mean by having an issue with "stacks [being] directly bound to specific accounts/regions", though. Why is that an issue? Why would you _want_ a stack that spans multiple account/regions? I just successfully created and validated a Certificate in us-west-2, so I'm not sure what your parenthetical means.

Re:So many bad takes. Learn from the Prime Video microservic... by nostrebored on Sunday May 07, 2023 @05:30PM (#35855785)
The IAC piece is the same across both. Except with k8s you’re managing infrastructure across cloud, k8s, potentially frameworks like helm, etc.

And on a large team there’s very little likelihood that everyone understands the different configuration layers. There’s very little likelihood that people understand the scope that changes to configuration might touch either. But when you work with CDK, it’s one tool to understand.

Faster and better way to grow into production ignores team level problems and team level constraints. At 10, 20, 100 engineers this is fine. But when you have dozens of teams you’re almost certainly losing efficiency by being prescriptive.

I find that this type of pedantry really surrounds the k8s ecosystem. I think k8s is an enterprise scale tool that has uses in enterprise applications. But the idea of suggesting it to everyone is lunacy

Re:So many bad takes. Learn from the Prime Video microservic... by Aeolun on Sunday May 07, 2023 @10:26PM (#35857436)
If you consider building your service that should take 3000 man hours to build in 300k instead, overspending by a factor if a 100, and then still succeeding, then yeah, you could consider that a success.

I’d consider it a massive, massive waste.

Re:So many bad takes. Learn from the Prime Video microservic... by emodendroket on Sunday May 07, 2023 @11:50PM (#35857870)
I have no idea what you’re arguing with this one.
Re:So many bad takes. Learn from the Prime Video microservic... by Aeolun on Monday May 08, 2023 @12:37PM (#35863699)
You can build exactly the same application even if you throw different amounts of money at it.

Large corpo spends 2M on a CRUD app and is happy with the result (e.g. consider it a success).

Another organisation (with more skilled people) builds exactly the same thing for just 50K, and also consider it a success.

The fact that it’s a success doesn’t mean that it wasn’t silly.

Sorry kind of lost track of the original thread here too.