MVPs and $100k AWS Bills: Reflections on our launch
1–10 of 101 posts
Re: MVPs and $100k AWS Bills: Reflections on our launch
#2"To bring Octopus Cloud to market quickly, we did the simplest thing possible; we took our self-hosted Octopus Server product and bundled it into an EC2 instance for each customer that signed up. We had to make changes to the product, but mostly around permissions."
I have used octopus and I could have told them that they can't lift-and-shift. The amount of requests the app makes is ridiculous, the way they wrote their database is appalling (actually crazily dumb https://octopus.com/blog/sql-as-document-store). Everything about it would mean they can't scale in the cloud without wasting a ton of money.
"Cloud stuff can be really expensive" - yes if you write dog shit, putting that in the cloud will be expensive.
Re: MVPs and $100k AWS Bills: Reflections on our launch
#3"To bring Octopus Cloud to market quickly, we did the simplest thing possible; we took our self-hosted Octopus Server product and bundled it into an EC2 instance for each customer that signed up. We had to make changes to the product, but mostly around permissions." I have used octopus and I could have told them that they can't lift-and-shift. The amount of requests the app makes is ridiculous, the way they wrote the…
From the "sql-as-document-store" post, I re-read it every now and then to realise how actually terrible it is:
"For a many-to-many, we do something a bit naughty: we store the values with | characters between each value:"
Not naughty, stupid.
Re: MVPs and $100k AWS Bills: Reflections on our launch
#4"To bring Octopus Cloud to market quickly, we did the simplest thing possible; we took our self-hosted Octopus Server product and bundled it into an EC2 instance for each customer that signed up. We had to make changes to the product, but mostly around permissions." I have used octopus and I could have told them that they can't lift-and-shift. The amount of requests the app makes is ridiculous, the way they wrote the…
From the "sql-as-document-store" post, I re-read it every now and then to realise how actually terrible it is: "For a many-to-many, we do something a bit naughty: we store the values with | characters between each value:" Not naughty, stupid.
Why would you bother with a relational database at that point? That sounds like it’s not normalized.
I haven’t read the post... maybe I’m missing something.
Re: MVPs and $100k AWS Bills: Reflections on our launch
#5Earlier quoted context omitted.
From the "sql-as-document-store" post, I re-read it every now and then to realise how actually terrible it is: "For a many-to-many, we do something a bit naughty: we store the values with | characters between each value:" Not naughty, stupid.
Why would you bother with a relational database at that point? That sounds like it’s not normalized. I haven’t read the post... maybe I’m missing something.
For ACID guarantees?
Re: MVPs and $100k AWS Bills: Reflections on our launch
#6Pardon me for asking a really dumb question: but do you have a positive item charge - CGS? Because I'm sure one can get a great demand by selling a $1.00 for $0.90 but that's not a business model.
Re: MVPs and $100k AWS Bills: Reflections on our launch
#7"To bring Octopus Cloud to market quickly, we did the simplest thing possible; we took our self-hosted Octopus Server product and bundled it into an EC2 instance for each customer that signed up. We had to make changes to the product, but mostly around permissions." I have used octopus and I could have told them that they can't lift-and-shift. The amount of requests the app makes is ridiculous, the way they wrote the…
From the "sql-as-document-store" post, I re-read it every now and then to realise how actually terrible it is: "For a many-to-many, we do something a bit naughty: we store the values with | characters between each value:" Not naughty, stupid.
Agreed.
Lifting and shifting is hard. It's harder when you do it in a careless way.
Re: MVPs and $100k AWS Bills: Reflections on our launch
#8Earlier quoted context omitted.
Why would you bother with a relational database at that point? That sounds like it’s not normalized. I haven’t read the post... maybe I’m missing something.
For ACID guarantees?
ACID guarantees have nothing to do with relational vs non-relational. FoundationDB is one example of a non-relational key value store that none the less provides ACID guarantees.
Re: MVPs and $100k AWS Bills: Reflections on our launch
#9The lesson to be learned here, and the one they admittedly already knew in advance, is if you do a lift and shift to AWS without changing your processes to be cloud native, you will always spend more.
Unfortunately, I’ve met way too many old school netops guys who got one AWS certification and all they knew was how to log into the web console and duplicate their colo infrastructure, charge their client a lot of money, and call it a day.
That being said, I’ve used a lot of CI/CD tools and OctopusDeploy is by far my favorite.
Even though my company is very much a “pay someone to do the undifferentiated heavy lifting” type of company, OctopusDeploy is so easy to use and maintain, I am not sure we would migrate.
Re: MVPs and $100k AWS Bills: Reflections on our launch
#10Earlier quoted context omitted.
From the "sql-as-document-store" post, I re-read it every now and then to realise how actually terrible it is: "For a many-to-many, we do something a bit naughty: we store the values with | characters between each value:" Not naughty, stupid.
Why would you bother with a relational database at that point? That sounds like it’s not normalized. I haven’t read the post... maybe I’m missing something.
> Why would you bother with a relational database at that point? That sounds like it’s not normalized.
It's non-1NF, though they sometimes (based on expected cardinality) normalize that aspect via a trigger, using the application-accessed table as, in effect, something of a write-through denormalized materialized view. It's not an entirely unreasonablev way to use an RDBMS in and of itself.