How Vercel Frees Frontend Developers from Backend Burden – InApps is an article under the topic Software Development Many of you are most interested in today !! Today, let’s InApps.net learn How Vercel Frees Frontend Developers from Backend Burden – InApps in today’s post !
Read more about How Vercel Frees Frontend Developers from Backend Burden – InApps at Wikipedia
You can find content about How Vercel Frees Frontend Developers from Backend Burden – InApps from the Wikipedia website
Frontend development is where the excitement is in internet technology in 2020. Why? Because the backend is pretty much sewn up at this point. As Vercel co-founder and CEO Guillermo Rauch put it recently, “the backend has been commoditized by cloud infrastructure, Kubernetes and off-the-shelf APIs.”
Richard is senior editor at InApps and writes a weekly column about what’s next on the cloud native internet. Previously he founded ReadWriteWeb in 2003 and built it into one of the world’s most influential technology news and analysis sites.
Rauch thinks the frontend offers the “most interesting new opportunities for modernization.” In an interview, I discussed with Rauch what those opportunities are and how Vercel fits into the emerging frontend ecosystem.
Vercel (previously known as ZEIT) is one of multiple well-funded startups pursuing the JAMstack approach to web development, which decouples the backend from the frontend and removes the need to manage a web server.
This doesn’t mean, however, that the backend disappears from the developer’s life altogether — their app or website still has to be built and deployed. And while infrastructure may be largely commoditized now, it’s more complicated than ever to configure and manage. So I asked Rauch how Vercel helps developers deal with that complexity?
“When it comes down to making that choice of the infrastructure,” he replied, Vercel gives the frontend developer “a completely managed serverless edge infrastructure, so that [with] their application or website, they don’t need to make any of that [infrastructure] investment themselves — they can just focus on their core application.”
Similar to Netlify, which I profiled in last week’s column, Vercel is focused on the build and deployment aspects of the JAMstack approach.
“We built a workflow by which frontend developers just push their code, build it, optimize it for distribution and put it right next to where your customer is,“ Rauch explained.
The Favored Framework: Next.js
While Vercel and Netlify have similar build workflows and edge networks, there is one key difference between the two companies: the frameworks.
The reason is simple: Rauch is the creator of Next.js.
According to Rauch, Next.js is “the easiest way for people to build a production-grade website or application today on the web.” He cited Hulu.com, Staples.com and Nike.com as just a few of the large websites powered by Next.js.
Next.js also showcases another trend in the cloud native internet: low code. Rauch told me that a big part of the appeal of the Next.js framework is “how little code is involved in actually making a frontend website or application work.”
In other words, Next.js isn’t just for web developers; web designers can use it too.
“It’s such a slim layer on top of React,” Rauch explained, “that really you’re just manipulating concepts. The primary concept that you manipulate is components. So it’s made it really, really appealing for both designers and developers. My take is that we’re seeing the rise of a hybrid product engineer here, [who] has this design sensitivity.”
This low code, “design meets development” approach to the frontend is possible in large part because Vercel takes care of the backend work.
“Once you never again think about infrastructure,” said Rauch, “[and] you don’t think about caches, you don’t think about load balance, you don’t think about CDNs [content delivery networks], you don’t think about CI/CD…then all your time goes to optimizing design and product experience.”
Why Vercel Built a Proprietary Edge Network
Like Netlify, Vercel has built its own edge network — basically a type of CDN. Rauch described it as a “proprietary edge network that we built that plugs right into the frameworks and tools that frontend developers are using today, like Next.js, Gatsby and so on.”
A CDN is a geographically distributed network of servers, typically used to host images, video and audio. The idea is that files are delivered to the end user by the server that is geographically closest to them. But as Rauch noted, CDNs have traditionally been “very specialized tools that you had to configure to speed up one slice of your application or website.”
What both Vercel and Netlify realized was that CDNs could be the primary distribution model, and not just focused on specific files. Not only that, but by using CDNs developers could be shielded from the often tricky configuration work required with web servers.
By Vercel focusing on this kind of CDN component, said Rauch, “we get all the reliability and performance benefits of this broad network, and we give that to the developers out of the box. There’s almost no way of building on top of these tools in such a way that it’s slow, or they could go offline. So it’s basically building on top of a distributed system, out of the box.”
“The modern developer is looking for vertically integrated solutions,” said Rauch. He described Vercel as “a toolchain and workflow company that gives [developers] this end-to-end experience.”
In a blog post announcing the Vercel re-brand in April, Rauch quoted one of the company’s investors as saying that Vercel is like “AWS [Amazon Web Services] for frontend developers.” It’s a great line, but what does it mean exactly?
Vercel is “addressing a critical problem with AWS,” Rauch said, “which is [that it] never really had a developer experience.”
The AWS experience, he continued, is “a choose your own adventure type ordeal, and I really don’t think that’s what the modern product developer wants today.”
In summary, what we’re seeing now with JAMstack and companies like Vercel and Netlify, is similar to what’s happening with the serverless and managed services trends. It’s all about abstracting away the backend and helping developers build things on top of (by now well established) cloud platforms.
Feature image via Pixabay.
At this time, InApps does not allow comments directly on this website. We invite all readers who wish to discuss a story to visit us on Twitter or Facebook. We also welcome your news tips and feedback via email: [email protected].
Let’s create the next big thing together!
Coming together is a beginning. Keeping together is progress. Working together is success.