So I'm allowed to talk a bit about what our client @scribd is up to in the wake of yesterday's funding announcement: tech.scribd.com/blog/2019/buil…
As mentioned in that blog post, they're going all-in on @awscloud as a provider. We've been doing a fair bit of cost modeling work with them over the past few months to figure out what a currently DC-bound environment looks like in AWS.
It turns out, there's no straight shot path to get there, despite what a bunch of replies to this thread selling services will tell you.
Do you migrate everything as it stands today and then modernize it later? Do you transform some workloads in place? Something else?
What will it cost to run your applications? "Well, it depends; how much data talks to your database from your app servers in a month?" Virtually nobody is instrumented to answer a lot of the questions involved.
Some tips: Tag in your AWS account rep early. They've got tools to help.
Partners are a mixed bag. Some are great, some are awful. We're not an AWS partner at all, for what it's worth.
SaaS or software solutions? Hard pass. They lack nuance, and fail to deliver value commensurate with their cost.
There's nuance here. If you'd like to see what it's like on the inside, they'll be live-blogging parts of the transformation over the coming months on their tech blog.
If you want a closer look, I do suggest applying to be a part of it yourself; they're hiring up a storm over at Scribd--and doing so remotely. They're good people. scribd.com/careers
