Become independent of Medium 🎉

[blog.git] / 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 30171474cc6f0307876e642403091dd6deb79b26..71f2228dbce7bd2748b14729e95ff9d1b5f501d4 100644 (file)
--- a/content/posts/demystifying-the-term-serverless.md
+++ b/content/posts/demystifying-the-term-serverless.md
@@ -9,15 +9,14 @@ type:  "post"
 highlight: false
 ---
 
-
-<img src="https://cdn-images-1.medium.com/max/1000/1*JQwYsJYUjKLWCf8r4iEueQ.jpeg" width=800/>  
+![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.