Spinnaker vs. Vercel

Spinnaker suits well for applications which are stateless and can adapt to an immutable architecture of deployment. But for applications which are stateful and cannot afford to spin up new servers for every deployment doesn't go well with Spinnaker. It can handle only deployments which are VM based and cannot support deployments to serverless architecture like AWS Lambda etc.

Incentivized

For me personally, Vercel was the best choice for website deployment. As I said, it automatically detects every push to my GitHub repository and redeploys it. No overhead of manually reconfiguring every setting. The cloud features are limited but good. The scenario where I would say it lacks is the option to deploy one's backend. Engineers like me mostly prefer to deploy their frontend on Vercel.

• Fast deployments.
• Can be integrated with a good variety of other products.
• Also provides some insights from your environment.

Incentivized

• Static Hosting
• Serverless Functions
• Deployment
• Integration
• Developer Experience

Incentivized

• It does NOT support CFN based deployments
• Windows based systems finds it difficult to onboard to Spinnaker.
• Pipeline level access authorisation is not there.
• Support for EBS volume encryption is probably missing.
• Attach/detach EBS volumes during deployments is difficult.
• No support to deploy the artifacts without re-creating the servers. Only pure immutable deployment are allowed.
• Open-source - so good and bad!
• Spinnaker on its own has 10 underlying micro services. Managing Spinnaker needs a focussed platform approach.
• User authentication is easy but authorisation management is not straight forward.

Incentivized

• Interface Revamp
• Cost reduction

Incentivized

Most of the website deployment work is handled by Vercel, especially for the frontend. It currently lacks backend code hosting, which makes me look for additional infrastructure or cloud providers that may not be as generous as Vercel and can be costly. This is the reason for an 8-out-of-10 rating.

• Pipeline Expressiveness • Self-Service/Override • Visibility of Client Teams • Operability of Client Teams - • High-Quality Integrations (AWS, IHP, Google) • Extensibility – (Ability to add code) • The maturity of Deployment Process • Speed/Ease of Onboarding

Incentivized

Vercel beats Heroku and DigitalOcean by a mile with pricing. Since Vercel uses serverless infrastructure, we don't pay for servers that don't get used, which is great for smaller platforms. Vercel Support is also very quick to respond, unlike DigitalOcean who took a while to get back to me after they didn't honor platform credits they sent me.

Incentivized

• By using Spinnaker we are able to deploy new versions of our product quickly.
• A deployment takes in average 2 minutes.
• Our investment on Spinnaker was just time learning it.

Incentivized

• Good clients.
• Faster delivery.
• Less overhead of DevOps.