News for hackers. Stuff that matters.
Re:Build versus Buy by hinkley on Monday April 13, 2020 @02:11PM (#22858329)
It's Pareto principle for me. >80% of our code should be off the shelf. The special sauce is 10% of the code. What should we spend that on? What will make us stand out?

If you can answer that, it's all the justification you need for building it. Anything you build that doesn't differentiate you can be bought by a competitor.

Re:Build versus Buy by BiteCode_dev on Monday April 13, 2020 @03:41PM (#22859241)
As usual, it depends. I know some friends that have profitable websites because they run on a private server and they handcrafted everything. If they had to use cloud services for serving stuff, host the db, provide search and cache things, it would cost too much and they couldn't make a living out of it.
Re:Build versus Buy by rconti on Monday April 13, 2020 @03:57PM (#22859387)
To me, this shows that the actual service/content they're providing has relatively low value, and so they're "making" money not just on the content but also on the services side; eg, they're a cheaper sysadmin than an outsourced one. And they're also possibly ignoring risk; eg, they don't have the data durability that a cloud provider does, but it Probably Won't Matter (TM).

There's absolutely nothing wrong with this way of making money; the lower the margins, the more watching your costs is crucially important, and the difference between making a living and not even breaking even!

Re:Build versus Buy by IanCal on Monday April 13, 2020 @04:54PM (#22859859)
Possibly, it may also be that the cloud providers are offering things they don't need. Maybe that's uptime guarantees, potential scalability or integration with other services.
Re:Build versus Buy by BiteCode_dev on Monday April 13, 2020 @04:05PM (#22859464)
Sure.

I just mention it because most people in the world have a job that make them less money than my friends web services.

And I'm assuming most startups, unless heavily founded, may have to think about this trade off as well.

The cost in infra can easily be a factor of ten.

Re:Build versus Buy by aledalgrande on Monday April 13, 2020 @04:26PM (#22859642)
If you take SaaS, they are skewed towards buy, because their margin is ridiculously high. Better to hit the market now by using stable products than optimizing on spend.

The bigger you are and the more you can think about optimizing spend.

Re:Build versus Buy by aprdm on Tuesday April 14, 2020 @11:59AM (#22867555)
I think it is quite the opposite. Having worked in startups that were VC funded it seems they consider VC money free money and just spend a lot of it in infrastructure without the need to.

I know for a fact our bill was around 15-20k USD per month for running a webapp that could be ran in digital ocean 40 dollars/month.

For a lifestyle business without VC money to burn it makes all the difference.

Re:Build versus Buy by aledalgrande on Tuesday April 14, 2020 @12:29PM (#22867943)
Oh I've definitely seen that too. My example requires responsible (and smart) leadership. My thought is that optimizing costs engineering hours, which are much more expensive than paying for the service bills.
Re:Build versus Buy by turbinerneiter on Monday April 13, 2020 @02:51PM (#22858754)
I agree with the idea, but I also think there are limits.

Let's say you build some kind of product based on some Azure/AWS product. The negative reading of it is: you spend money on innovation and have to pay Azure/AWS for infrastructure. Your product will constantly have to improve to keep up with the competitors, Azure/AWS keeps getting your money. And if your product becomes stable enough, they will make it part of their offering.

Another example would be Apps, with Apple later folding their functionality into the OS and kicking your app off the store.

But judging by my own examples, this migth be more of a platform problem.

Re:Build versus Buy by NomDePlum on Monday April 13, 2020 @03:38PM (#22859227)
Surely that very much depends on whether your product fits within the current or near future offering of Azure/AWS.

The other side of that coin is that you use a build horizontal integration strategy to replace elements of the products you buy from Azure/AWS if (and only if) it can be done in a way that increase your profit/value.

It can work both ways. Moving from buy to build also has elements of de-risking and economies of scale if you do it at the point where there is measurable success/product to market fit.

Building something you can buy too early runs the risk of premature optimisation if not done for the right reasons.

Re:Build versus Buy by DanHulton on Monday April 13, 2020 @05:00PM (#22859910)
Absolutely. This is largely what I'm betting on with my latest project, that the time you spend spinning up all the "standard stuff" for a SaaS project is duplicated - and thus wasted - effort throughout the industry. Why write another user login system?

Though it sets up an interesting situation for me, where the "special sauce" of _my product_ is the 80% "off the shelf" for my customers.