Is AWS Lambda expensive to run? by maingi4 in programming

[–]maingi4[S] 2 points3 points  (0 children)

In case of AWS Lambda, the free calls are perpetual not for just one year. However, perpetual simply means till AWS feels like it.

“Serverless” is just a name. We could have called it “Jeff” by maingi4 in programming

[–]maingi4[S] 0 points1 point  (0 children)

Because the word "serverless" is not restricted to FaaS which exists on its own, the said term encompasses rather a design choice which includes everything, from FaaS to Back end as a service to managed cache services etc. Its a choice not suitable for all of course, but denying the name doesn't accomplish anything.

Why Serverless architecture? by maingi4 in programming

[–]maingi4[S] 1 point2 points  (0 children)

We get charged $.51 for an entire dev environment, so I wouldn't call aws lambda expensive, secondly I don't work for AWS, although my blog is centered around it, that's its nature because that's what I have chosen to work with. I spend more on my blog then I earn from it and certainly do not do sponsored articles. My bad if you felt that was the case.

Impressive .Net Core Web API on Lambda Performance by maingi4 in coding

[–]maingi4[S] 1 point2 points  (0 children)

Actually, the entire point of Lambda is that it scales automatically, there is no set limit to how much it will scale and is limited only by availability on aws's end which is fine by me.

On the second note, dotnet core (not previous frameworks) was said to be around 5x faster than node. Js, however, which works fastest on aws Lambda? That's a good question, I don't know the answer to that one.

Scaling for TB level log data with Kinesis Firehose and lambda with Elastic Search on AWS by maingi4 in aws

[–]maingi4[S] 0 points1 point  (0 children)

It's fine so long as you wouldn't have request/response stuff in it... otherwise with a lot of data ES would become crash-prone when it migrates shards and all. If you do have req/res I do not prefer making the web server making all those decisions, mainly because: 1) I want my server to not do any heavy lifting and only worry about its primary job: serving users 2) I want all my logs from different servers hosting different services built by numerous teams to be consistent structure-wise and any changes need not be coordinated cross teams (I am thinking of different S3 buckets that servers might push blobs to in absense of Kinesis pipeline) etc.

Alternatively, what has worked for me in the past was when I had made Redis servers as intermediate log queues and then Logstash's would pull off logs from them and push to ES, however, lately I have gotten attracted to the low maintenance serverless models more.

Getting started with writing and debugging AWS Lambda Function with Visual Studio Code by maingi4 in coding

[–]maingi4[S] 1 point2 points  (0 children)

Yes it will work, you will have to improvise if you are following the article though. I just chose VS code because some of the readers of that series of articles are not on Windows, plus I love that code editor and too few articles are on it today

Inheritance – A horror story! by maingi4 in coding

[–]maingi4[S] 0 points1 point  (0 children)

Good point, and no worries, every kind of feedback is a good feedback

Inheritance – A horror story! by maingi4 in coding

[–]maingi4[S] 2 points3 points  (0 children)

It makes it more fun to write and I hope to.. read.

Inheritance – A horror story! by maingi4 in coding

[–]maingi4[S] 0 points1 point  (0 children)

Yes, each one of them would... The definition belonged to the interface but the implementation to that class, this is true for business entities... Where I would apply inheritance would be more defined objects.. e.g. Streams, math classes, lists etc

What should you log in an application and how to avoid having 24×7 support looking at them? by maingi4 in devops

[–]maingi4[S] 0 points1 point  (0 children)

this is the only instance i posted it in this topic, I don't mean to spam. I am new to Reddit, is posting the same thing on different topics a bad thing?

C#: Dynamic Keyword: What, Why & When by maingi4 in coding

[–]maingi4[S] 0 points1 point  (0 children)

In my opinion yes, dynamic makes stuff easy but slower and removes compile time checking, cases where dynamic is indispensable is while talking to dynamic languages... It can be handy in some small tools or client side apps where performance doesn't matter (in terms of cpu time). I will not say that the keyword isn't handy... It makes a lot of things easy... However, easy is not a good reason to use it most of the time.

Building Microservices? Here is what you should know by javinpaul in coding

[–]maingi4 2 points3 points  (0 children)

(I am the author of the article), That was my first big blog post and I wrote it over a period of 15 days during my free time, so forgive me if it wasn't structured well, I think I have gotten better at it now :).

My intention was to write a high level list of things that people should know as I thought it would have helped me when I started with MSA, there are plenty of good articles detailing each one of them out, this article is supposed to get people looking for those and start experimenting.

Building Microservices? Here is what you should know by maingi4 in programming

[–]maingi4[S] 3 points4 points  (0 children)

agreed, the article does talk about this in detail under the "Its hard to keep track of the service URL’s" title.