X-Git-Url: http://njoseph.me/gitweb/blog.git/blobdiff_plain/19a95bf14c01a4fc4e2084727cb8f3d48b7a5dbc..a37c7a265ea1e753c979576095d57b9933dd1470:/content/posts/demystifying-the-term-serverless.md diff --git a/content/posts/demystifying-the-term-serverless.md b/content/posts/demystifying-the-term-serverless.md index 3017147..71f2228 100644 --- a/content/posts/demystifying-the-term-serverless.md +++ b/content/posts/demystifying-the-term-serverless.md @@ -9,15 +9,14 @@ type: "post" highlight: false --- - - +![A server rack](/blog/server-hardware.jpeg) *Server, the physical hardware* When people think of servers, they imagine a big machine or a large stack of them making humming noises and furiously serving millions of requests. A server can also mean a computer program that is continuously running, listening for client requests and serving them. Think Apache, Nginx or Tomcat. -![Apache HTTP server, the software](https://cdn-images-1.medium.com/max/2000/1*ANRQ-WLCLs5yM13GKGBtPg.png) +![Apache HTTP Server logo](/blog/apache-logo.png) *Apache HTTP server, the software* When someone says that they have gone *serverless*, what they actually mean is that they are no longer running a software program listening to requests. There should still be a physical computer of some sort serving the requests of the clients.