When To Go Serverless? | HackerNoon

'When To Go Serverless?' by @amrh434 #serverless #serverlessarchitecture

Serverless, Serverlessarchitecture

1/22/2022 5:16:00 PM

'When To Go Serverless?' by amrh434 serverless serverlessarchitecture

It's hard to decide whether to go serverless or not. This article covers what is serverless in the first place and the pros & cons.

@ABOUT PAGEWhat is Serverless?Scaling/unpredictable workloadCostYou only care about your business logic. Everything else is not your responsibility, no server, no number of replicas, nothing you want to do 1 2 3 just write 1 2 3.The bad side?The time the cloud provider takes to lunch your function, and it depends on how frequent the function was called sometimes, it takes 1 - 2s.

Read more: HackerNoon »

Spring Storm Forces Many Colorado High Schools To Change Outdoor Graduation Plans

Weather forced high schools to switch up their graduation plans. Read more >>

Subtle Culture Problems That Often Go Unnoticed | HackerNoonWhen Peter Drucker said in 2006 that “Culture eats strategy for breakfast,” he did not mean that strategy is not important. Rather an effective strategy is crucial to organizational success. A good strategy is the key to successfully implementing the vision. But a strategy by itself cannot push any organization to achieve tremendous growth and success. What gives life to that strategy are its people.

Voting for Startups Ends Next Week! | HackerNoon'Voting for Startups Ends Next Week!' by hackernoon startups hackernoon zentist_io all the way💪

Noonies Voting Ends Next Week! | HackerNoon'Noonies Voting Ends Next Week!' by hackernoon noonies2021 hackernoon

Your Voting Power Ends Next Week | HackerNoon'Your Voting Power Ends Next Week' by escvdotca hackernoon marketing

We Built a Crypto Trading Algo Based on AI Sentiment Analysis | HackerNoon'We Built a Crypto Trading Algo Based on AI Sentiment Analysis' artificialintelligence machinelearning

Top 10 Resident Evil Games Ranked by Sales | HackerNoon'Top 10 Resident Evil Games Ranked by Sales' residentevil capcom

January 22nd 2022 new story Serverless is a cloud-based application that uses functions to run when an event happens. It means that you are not responsible for managing your infrastructure. All you have to do is write some logic to be executed when something happens. The good side: Scalability, security, speed, and cost. The bad side: Some cloud providers limit your function running time to a certain number of minutes, so if you want to process something that takes a long time, it’s a big no. @ Amr Hassan A perfectionist with an INTJ personality that worked on so many Fenkosh!. Love biking and breaking things. ABOUT PAGE I'm sure now most of you, if not all, have heard about serverless and how trendy & sexy it's. But what bothered me the most was when to use one? But before answering that, let’s answer the what & why first and by knowing that the answer will reveal itself. What is Serverless? So what is serverless? Does it mean that there is no server? Nope, that's not the case. It means that you are not responsible for managing your infrastructure. All you have to do is write some logic to be executed when a certain something happens. Certain something could be an event, for example, a file uploaded or an HTTP call. Why Serverless? Scaling/unpredictable workload . While the scaling point could be achieved by many solutions already, for example, Kubernetes with KDA could do the same effect, but again most of the cloud providers will provide this functionality out of the box and will be more efficient as you are only paying for the resources you used. Cost Theoretically speaking, cost should be very low as you are only paying for what you use, meaning the function would only work when some sort of event happens, and you are only paying for the time the function took to finish the work. Simplicity/Rapid development You only care about your business logic. Everything else is not your responsibility, no server, no number of replicas, nothing you want to do 1 2 3 just write 1 2 3. Security It's easy to apply a principle such as least privilege where you define the permissions for each function so that there is no such master function (you shouldn't have) that does it all and have permission for everything besides that the cloud provider should provide the latest updated versions of OS that runs your function so you shouldn't worry about that. The bad side? What are the limitations? Cold Start The time the cloud provider takes to lunch your function, and it depends on how frequent the function was called sometimes, it takes 1 - 2s. Can't store things in memory/files . When your function gets triggered, it runs on an ephemeral disk which is something that gets deleted after the function completes. The same thing applies to the used memory. Execution time Some cloud providers limit your function running time to a certain number of minutes, so if you want to process something that takes a long time, it’s a big no. Vendor lockin This happens when your implementation & logic rely on the infrastructure of a specific cloud provider. For example, if you are using AWS, you will end up relying on many services & permission related only to AWS, which means if you want to switch to another cloud provider, you will suffer a little. Hard to test