+ +_Sometimes the best you can do is to help yourself._ + ++ +_Cheers, and take care!_ diff --git a/src/data/blog/articles/serverless.md b/src/data/blog/articles/serverless.md index 07ce202..fa98d47 100644 --- a/src/data/blog/articles/serverless.md +++ b/src/data/blog/articles/serverless.md @@ -1,12 +1,14 @@ --- id: serverless title: "Serverless Deployment" -date: "06-15-2022" -featured: 1 +date: "06-16-2022" +featured: 2 image: images/serverless.png tags: [technology, software_development] --- +
Image sourced from Hexaware
+ This infamous depiction of serverless has been circulating around for years now. According to this image, Serverless Functions, also called "Functions as a Service", is way to write an application with a focus on business logic and not worrying about infrastructure or runtime. ## I'm new to serverless, how does this work? @@ -25,7 +27,7 @@ app.get(`/`, async (req, res) => { res.json({ cats }) }) -app.listen(3000) +app.listen(process.env.PORT) ``` To have a similar application on a serverless platform like AWS Lambda, your code would look like this - @@ -54,18 +56,64 @@ functions: method: get ``` -This can now be deployed to Lambda using the AWS cli. Based on the configuration file, when a trigger event happens, a new container will spin up and execute this function. ++ Serverless Framework Configuration +
+ +This can now be deployed to Lambda using the AWS CLI (or something vendor-agnostic like the serverless framework). Based on the configuration file, when a trigger event happens, a new container will spin up and execute this function. You just wrote some code and deployed it without thinking about any infrastructure or runtime! ## Execution On Demand -While on the surface the code looks similar, your cannot simply throw out express, setup lambda routes and call it a day. - -Well, technically you can, but you'll end up with a very unoptimized and wasteful mess, followed by losing trust in all cloud services and going back to buying racks and switches. +When you deploy traditional apps, you (or your trusty Continuous Delivery service) will spin up a container, start your application process inside the container, establish a network connection, and send an alert to your slack channel. This application will now wait for network requests and react to them as told. All this while, it's consuming memory and processing power, even when it does not receive any requests. -With traditional apps, you (or your trusty orchestration service) will spin up a container, start your application process inside the container, establish a network connection, and send an alert to your slack channel. This application will now wait for network requests and react to them as told. All this while, it's consuming memory and processing power, even when it does not receive any requests. +
In comparison, when you deploy a serverless function, a service like Lambda will only bill you for the time your function is actually running, which only happens when it's triggered. When there is a trigger event, Lambda will find the corresponding function for that trigger, then either spin up a new container and load the function in it (cold start) or find an existing container that has the function already loaded in memory (hot start), and execute the function. The container will then either stay on and wait for more requests, or die out.
-So you can start to notice some differences here. If you receive 1 request every second, you will only have 1 running function every second. However, if you get a thousand requests at the same time, Lambda will run a thousand containers with the function. So this approach is extremely elastic. You will use and pay for only the exact resources that you use. If you have multiple functions, each function is deployed as a separate Lambda, so you also will only be using the resources required to run that one function for any trigger.
+
+
+So you can start to notice some differences here. If you receive 1 request every second, you will only have 1 running function every second. However, if you get a thousand requests at the same time, Lambda will run a thousand containers with the function. So this approach is extremely elastic. You will use and pay for only the exact resources that you use. If you have multiple functions, each function is deployed as a separate Lambda, so you also will only be using the resources required to run that one function.
+
+## So it's always cheaper?
+
+Not really.
+
+For a base unit of computation (like an hour of server usage), you will pay more to the serverless service than you would for a virtual server.
+
+
+
+
+The difference lies in how much computation you are using. With a virtual server, you are paying for every second the server is alive, regardless of whether your code is running in it. In comparison, a serverless function will only cost you the computation of the function itself.
+
+It's optimized for elasticity, so it's only feasible in scenarios where you need elasticity. If you have inconsistent or unpredictable usage, serverless is a nice fire-and-forget deployment method where you app will scale up and down automatically as needed.
+
+
+ AWS Lambda costs around $0.06 for a full hour of execution with 1 GB of memory (calculated per ms of use).
+ AWS EC2 can cost between $0.008 to $0.01 per hour for an instance with 1 GB of memory. +
++ AWS EC2 can cost between $0.008 to $0.01 per hour for an instance with 1 GB of memory. +
+ Sources: + EC2 Pricing, + Lambda Pricing +
+
+
+
+
+
-I found this particularly interesting because I have always considered myself to be a very ambitious person. I often think about where I could be 5-10 years in the future, and those scenarios are sometimes not very realistic. But on this day, we had to think about a specific personal vision that we always have wanted to see realized. So unlike the other occasions when I used to dream about my future, this one had to be a little more realistic, specific and organized, so that I can easily convey it. This was followed by an activity, which made us write a news article that would be published when our vision would be realized, and the news article would describe the achievement. [Here is the article I wrote](/leadershape-article.jpeg). +I found this particularly interesting because I have always considered myself to be a very ambitious person. I often think about where I could be 5-10 years in the future, and those scenarios are sometimes not very realistic. But on this day, we had to think about a specific personal vision that we always have wanted to see realized. So unlike the other occasions when I used to dream about my future, this one had to be a little more realistic, specific and organized, so that I can easily convey it. This was followed by an activity, which made us write a news article that would be published when our vision would be realized, and the news article would describe the achievement. [Here is the article I wrote](/images/experiences/leadershape/leadershape-article.jpeg). Aside from the main objective, one important aspect of the whole experience was getting to know more like-minded people and talking about ideas, thoughts and feelings. On the very first day, we were told that to truly develop self, we need to stretch out of our comfort zone and try out new things, until those new things become our comfort zone. For me, this is exactly what happened throughout the week. diff --git a/src/data/showcase/projects/hackathon.md b/src/data/showcase/projects/hackathon.md index 6d8ee1c..d6fbc72 100644 --- a/src/data/showcase/projects/hackathon.md +++ b/src/data/showcase/projects/hackathon.md @@ -18,13 +18,13 @@ This project is composed of: - An emails server to process templates designed in HTML and SCSS and produce email templates. Built using Express and HEML. - A modular monolith API server, built with NestJS and Postgres. -
- Instagram + + Twitter + {" "} +
+ + Facebook + {" "} +
+ + Instagram + diff --git a/src/pages/index.d.ts b/src/pages/index.d.ts new file mode 100644 index 0000000..1ea2b53 --- /dev/null +++ b/src/pages/index.d.ts @@ -0,0 +1 @@ +declare module "*.jpg" diff --git a/src/pages/index.js b/src/pages/index.js deleted file mode 100644 index 1be3f40..0000000 --- a/src/pages/index.js +++ /dev/null @@ -1,14 +0,0 @@ -import React from "react" -import Layout from "../components/layout" - -const IndexPage = ({ location }) => ( -
-
- Welcome to my site!
-
+
+
+
+
+ 
+
+
+
+ Welcome!
++ I am a software developer and an aspiring software architect and + content creator. +
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
diff --git a/src/templates/project-page.tsx b/src/templates/project-page.tsx
index fa23ebc..ece98c7 100644
--- a/src/templates/project-page.tsx
+++ b/src/templates/project-page.tsx
@@ -23,7 +23,9 @@ const ProjectPageTemplate = ({ pageContext }) => {
title={project.name}
description={project.description}
path={path}
- image={project.image ? `/images/projects/${project.id}.png` : undefined}
+ image={
+ project.image ? `/seo-images/projects/${project.id}.png` : undefined
+ }
>
diff --git a/static/images/blog/serverless/consistent-execution.png b/static/images/blog/serverless/consistent-execution.png
new file mode 100644
index 0000000..c7d8fca
Binary files /dev/null and b/static/images/blog/serverless/consistent-execution.png differ
diff --git a/static/images/blog/serverless/execution-time.png b/static/images/blog/serverless/execution-time.png
new file mode 100644
index 0000000..9156a9a
Binary files /dev/null and b/static/images/blog/serverless/execution-time.png differ
diff --git a/static/images/blog/serverless/serverless-deploy.png b/static/images/blog/serverless/serverless-deploy.png
new file mode 100644
index 0000000..3c37d99
Binary files /dev/null and b/static/images/blog/serverless/serverless-deploy.png differ
diff --git a/static/images/blog/serverless/traditional-deploy.png b/static/images/blog/serverless/traditional-deploy.png
new file mode 100644
index 0000000..bf75c13
Binary files /dev/null and b/static/images/blog/serverless/traditional-deploy.png differ
diff --git a/static/leadershape-article.jpeg b/static/images/experiences/leadershape/leadershape-article.jpeg
similarity index 100%
rename from static/leadershape-article.jpeg
rename to static/images/experiences/leadershape/leadershape-article.jpeg
diff --git a/static/images/experiences/revolutionuc/architecture.png b/static/images/experiences/revolutionuc/architecture.png
new file mode 100644
index 0000000..af52180
Binary files /dev/null and b/static/images/experiences/revolutionuc/architecture.png differ
diff --git a/static/images/experiences/revolutionuc/teams.png b/static/images/experiences/revolutionuc/teams.png
new file mode 100644
index 0000000..41e25f9
Binary files /dev/null and b/static/images/experiences/revolutionuc/teams.png differ
diff --git a/static/images/experiences/revolutionuc/trello.png b/static/images/experiences/revolutionuc/trello.png
new file mode 100644
index 0000000..5d7a7e3
Binary files /dev/null and b/static/images/experiences/revolutionuc/trello.png differ
diff --git a/static/hackathon-deployment.png b/static/images/projects/hackathon/deployment.png
similarity index 100%
rename from static/hackathon-deployment.png
rename to static/images/projects/hackathon/deployment.png
diff --git a/static/hackathon-web.jpg b/static/images/projects/hackathon/web.jpg
similarity index 100%
rename from static/hackathon-web.jpg
rename to static/images/projects/hackathon/web.jpg
diff --git a/static/images/blog/index.html b/static/seo-images/blog/index.html
similarity index 100%
rename from static/images/blog/index.html
rename to static/seo-images/blog/index.html
diff --git a/static/images/experiences/index.html b/static/seo-images/experiences/index.html
similarity index 100%
rename from static/images/experiences/index.html
rename to static/seo-images/experiences/index.html
diff --git a/static/images/projects/index.html b/static/seo-images/projects/index.html
similarity index 100%
rename from static/images/projects/index.html
rename to static/seo-images/projects/index.html