5 ms·
I take issue with all of the complaints here... - performance: first rule of architecture is that you don't build the entire thing on the needs of high perform
by ChicagoDave 6y ago
I take issue with all of the complaints here...
- performance: first rule of architecture is that you don't build the entire thing on the needs of high performance...you only address performance as-needed
- vendor lock in: this is the worst reason. Most companies choose cloud vendors and stick with them over many years. I'd love any survey that showed some massive migration between vendors on a regular basis, but it does not exist.
- the monolith: granted, serverless is really best when building something from scratch. Trying to "migrate" to serverless is just a bad idea. Trying to "upgrade" portions is okay, but do it well using the autonomous bubble pattern, making sure you have a solid translation layer
I believe serverless is our best modern architecture, but I also understand that not every company is ready to do the work and/or pay the price of the change in development processes. I'd agree that it's stalled, but moreso out of fear and ignorance than anything else.
- mrkeen 6y ago> vendor lock in: this is the worst reason. Most companies choose cloud vendors and stick with them over many years. I'd love any survey that showed some massive migration between vendors on a regular basis, but it does not exist. Why do you think companies stick with vendors for so long instead of switching?
- ChicagoDave 6y agoBecause it’s a part of long-term planning and the lock-in variable a lower priority than all of the other factors.
- mrloba 6y ago> I'd love any survey that showed some massive migration between vendors on a regular basis, but it does not exist. Isn't this a sign of existing lock-in? Also, I think lock-in comes in degrees. Some are worse than others. Even if we're slightly locked in right now, we can easily make it worse if we try.
- FpUser 6y ago>"I'd agree that it's stalled, but moreso out of fear and ignorance than anything else." How about simple common sense instead of "fear and ignorance". I have a C++ monolith that serves me just fine already for years. The performance is great and I am able to rent dedicated servers that can serve at least 10 times more requests that I have at a price that is a tiny fraction of AWS for the same work. Why would I switch and incure more expenses? What's the ROI?
- ChicagoDave 6y agoCan your business adapt to change well? That’s the first issue with any monolith.
- FpUser 6y agoWhat change? I am not going to worry about some abstraction. You have to be more particular. In my case I change features on on need basis with no problems. Hence I have 0 issues with the monolith. Micro- services actually do not really make life any easier. All that immense cloudy push is driven by handful of very big corps who'd build architecture for scale that most of the businesses would never even dream to approach. So I'll let them worry about their problems and I'll worry about mine. I am not in business of transferring my money to cloud paying 10x and more comparatively to my current solutions.
- robocat 6y ago> vendor lock in: this is the worst reason Vendor lock-in is magically valuable, until it is not. The problem isn’t lock-in per se: the problem is choosing lock-in that will bring surplus extra value for an extended period of time.
- ChicagoDave 6y agoReplying to my own comment because I went looking for a current article on vendor lock-in. This is anecdotal and I get that, but I agree with it: https://www.cloudtp.com/doppler/is-vendor-lock-in-keeping-you-up-at-night/ https://www.cloudtp.com/doppler/is-vendor-lock-in-keeping-yo... We’re not buying into IBM mainframes anymore and although there are still customers tied to Oracle databases, vendor lock-in just isn’t that big of a deal anymore.