4 ms·
Every company I know of that this happened to, and I know of at least five personally and others via 2nd hand, disappeared within six months. One of them went
by jedberg 9y ago
Every company I know of that this happened to, and I know of at least five personally and others via 2nd hand, disappeared within six months.
One of them went on to start a new company and was acquired by Facebook for a whole lot of money.
But overall the outlook isn't great, and here's why. Amazon is great at the "80% solution". If you're already in AWS, and they have something that does most of what you want, it's way easier to use that than try and integrate with someone else.
So if what you're doing is only in AWS and isn't significantly better than what they offer, the news isn't good.
I'm sorry this happened to you. :(
- scarface74 9y agoIt's the old "No one ever got fired for buying IBM". Why would I choose a slightly better product from an unknown company? If it was the wrong decision it calls my competence into question. If I choose AWS and it was the wrong solution, no one will bat an eye because they would have made the same choice.
- akinjide 9y agoYou'd have to weigh or SWOT your decision, using a better product from an unknown company that might offer more or from a trusted company (AWS) that offers less. Especially if, the unknown company is offering something the trusted company isn't
- blowski 9y agoThe thing about "nobody ever gets fired for buying IBM" is that going with an unknown alternative is a risk to you personally and most of the benefits go to the company. When you over-spend on a well-known brand, the company suffers the costs and they barely even notice. The only time they care is if something goes wrong, and then they want to know why you chose an unknown brand.
- akinjide 9y agoSay something went wrong, and the company is questioning why you went for an unknown brand. My answer to that would be they offered more value than the trusted brand, also I would have notified necessary stakeholders before making that decision of using services provided by the unknown brand.
- blowski 9y agoOr you could save yourself the risk and all the hassle, and just go with the well-known brand. It's not necessarily what you should do, but it is what often happens.
- paulcole 9y ago> My answer to that would be they offered more value than the trusted brand So much value that things went wrong and now you're explaining yourself.
- singingfish 9y agoI figure the correct way is that you build for "the cloud" aka someone else's computer. This means that don't use their proprietary offerings to do so unless absolutely necessary.
- scarface74 9y agoIf you don't use their proprietary offerings, you lose most of the benefit of going to the cloud over being on prem. If all you're doing is hosting a bunch of VMs on the cloud, what's the point? Yes, be mindful as a developer I do take a few common sense steps... 1. ElastiCache uses the Memcached protocol so you're really not tying yourself to anything. 2. Lambda - think the "ports and adapters" pattern. Treat your Lambda function as a controller and keep all of your business logic separate. 3. Logging - all of our logging that goes to CloudWatch goes through Serilog. We can switch out the sink easily enough to anything. 4. Simple Queueing System - don't have calls to SQS all over your code, have it in one central module (in our case a Nuget package). 5. Autoscaling - have a shutdown method and wrap the calls that check when your instance is being shut down as events. 6. AWS KMS - We use Hashicorp's Vault and use AWS as a "backend". 7. Cognito - authentication. It's just Middleware for .Net Core that creates a principal before every request. It would be quite easy to add another piece of middleware.
- scarface74 9y agoAnd if that unknown small company goes out of business, then what? I've been on both sides of that equation - the vendor and the client. When I was working for the vendor, the only way that we were able to secure our biggest deal was to put our entire software stack in escrow -both the proprietary development platform and the system we built for them on top of it. * As the client, part of the contract was that they had to put their code in escrow. In both cases, the client was large enough to negotiate those terms. What if you aren't large enough to force those terms? * That worked out well for me. When the company I worked for went belly up, the client that enforced those terms hired me to complete their system since they had the right to the source code and I was the only person on the planet that was available that knew how both the C based development platform and their implementation worked well enough to complete it.
- lev99 9y agoI don't think it's just that. I have complete freedom to use any cloud solution in my organization, but I almost always choose AWS. Mostly it's a seal of basic quality. I know it had documentation, I know it has uptime, and I know it has packages for any environment I want to use it in. I've had mixed experiences with less established SaaS, and mixed experiences means more dev time on average.
- akinjide 9y agoIf the unknown company is offering everything you just listed, will the unknown company be considered?
- PeterisP 9y agoAn unknown company by definition is unable to offer what they just listed, namely, that they know and trust that all of that really is there at the quality they expect. It may claim these things and might actually have them, but any company or sysadmin must spend significant time, effort and thus cost to investigate and verify if that really is true, at least until they have established a solid reputation and aren't an unknown company anymore. And there should be some reason to spend this cost in reviewing and considering them if more established options are available; if other factors are equal, then the more widely used service is better for various reasons, so if they aren't promising some nontrivial improvement over AWS, why bother?
- filleduchaos 9y agoIf the company does offer all that, how are they still unknown?
- lev99 9y agoNo. The things I listed are reasons I am hesitant to work with a company I am unfamiliar with. To be considered you have to have everything listed, and be clearly better than AWS. Better shouldn't be defined as cheaper, but by a higher quality product. It's hard to define that without knowing exactly what service you provide.
- 9y ago