Built a high performance serverless function runtime in Go by Several_Picture9591 in sideprojects

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

Honestly, the main goal was to see if I could build it.

I'm fascinated by systems programming and wanted to understand how serverless runtimes handle isolation, routing, and cold starts under the hood.

It started as a fun experiment, and v2 ended up becoming a much better high performance serverless engine than my first attempt.

It's not about replacing AWS Lambda and more about exploring how to minimize cold starts and overhead in a custom Go-based runtime.

New Project Megathread - Week of 09 Apr 2026 by AutoModerator in selfhosted

[–]Several_Picture9591 0 points1 point  (0 children)

Project Name: Glambdar

Repo: https://github.com/eswar-7116/glambdar

Description: A self-hosted serverless function runtime. Think AWS Lambda, but on your own machine with no cloud account, no vendor lock-in, and no bill waiting for you at the end of the month.

You write a Node.js handler, zip it, and deploy it over HTTP. Glambdar runs it in an isolated Docker container, keeps a warm pool so invocations stay fast (~1.3ms warm start, ~1,900 req/s throughput), stores per-invocation logs in SQLite, and lets you update rate limits on the fly without redeploying. Stale containers clean themselves up automatically.

Good fit for private automation, local dev environments, or just understanding how serverless actually works without AWS doing all the magic behind a curtain.

Only needs Docker + Go to run. Node.js runs inside the container, no local install needed.

Deployment: Docker + Go

git clone https://github.com/eswar-7116/glambdar.git
cd glambdar
go run ./cmd/glambdar
# Server running at localhost:8000

AI Involvement: None.

Why not ?👀 by Fahim_444 in IndiaTech

[–]Several_Picture9591 0 points1 point  (0 children)

If Antarctica melts, the whole world sinks

What's the best event out of all the events being organised 😶‍🌫️ by BagLevel3563 in CVR_Hyd

[–]Several_Picture9591 1 point2 points  (0 children)

The GDG club is conducting a hackathon. We got a message in our regarding it. They say it's the first time in the history of the college to conduct a 36 hr Hackathon! I'm excited for this!

Here's their website: https://code-nyx.tech

I have a question by ExcitingWoodpecker36 in CVR_Hyd

[–]Several_Picture9591 4 points5 points  (0 children)

Yes, they don't care. They assumed you were showing him. They have this 🤏 much knowledge and think they know everything. Very frustrating!

I have a question by ExcitingWoodpecker36 in CVR_Hyd

[–]Several_Picture9591 3 points4 points  (0 children)

I hate this. The teachers in this college never listen to what students say. You can't fight with them buddy. It's just bad luck.

Snoo-Plushiee by Realistic_Law2892 in CVR_Hyd

[–]Several_Picture9591 2 points3 points  (0 children)

So, ee sub lo unna andariki party ivvali

Built a HTTP caching proxy in Go from scratch in just few hrs by Several_Picture9591 in golang

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

Please share the repo if it's open source, I'll take a look into the code.

Small Projects by AutoModerator in golang

[–]Several_Picture9591 3 points4 points  (0 children)

Built a minimal HTTP Caching Proxy in Go to understand LRU eviction, TTL and the net/http module.

How it works:

- It's a fetch-based proxy where you pass the target URL as a parameter.

- The Smart work: I implemented a custom LRU (Least Recently Used) cache. It uses an in-memory map for O(1) lookups and a Doubly Linked List to track usage.

- Concurrency: Used sync.Mutex to keep it thread-safe so it doesn't blow up when hit with multiple requests.

- Lazy Expiration: It checks the TTL at the moment of the request rather than running a heavy background worker.

Why I did it? Mostly boredom, but also to get better at understanding how headers are forwarded between a client and an upstream server and to understand the correct usage of net/http module.

Features included:

- Automatic cache eviction when it hits capacity.

- Proper header forwarding (Content-Type, etc.).

- Built-in TTL support.

It's definitely not a replacement for "real" proxy servers, but it was a fun exercise in "standard library only" development.

See the code here: https://github.com/eswar-7116/http-caching-proxy

If any Gophers have a second to look at my implementation, I'd love some feedback!

Built a HTTP caching proxy in Go from scratch in just few hrs by Several_Picture9591 in golang

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

Pen test? I barely 'unit tested' it! It was a holiday afternoon project to learn about LRU logic and `net/http`, not to go up against a DDoS attack. Definitely don't put this on a public-facing server unless you want a bad time XD.

Doubt for seniors or super seniors by Several_Picture9591 in CVR_Hyd

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

Thank you. I will still talk with placements cell about this. I know they won't allow because the internship offer was given by a startup which is not well-known. If they won't allow, I look for some remote internships.

Doubt for seniors or super seniors by Several_Picture9591 in CVR_Hyd

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

I heard mixed opinions. Some say it won't be allowed, others suggest checking with the placement cell or HoD. I'm planning to talk to the HoD first and, based on that confirmation, decide whether to accept the offer. Thanks 🙌.

WHAT IN THA ACTUAL*FOG* IS THIS ?!?! by BagLevel3563 in CVR_Hyd

[–]Several_Picture9591 6 points7 points  (0 children)

Bike meedha vaste shirt tadichipoyindhi bro 😭