Research Mode Activated – Hosting, Tools & How “One Click” Automation Really Works

Today was not coding day.

Today was research day.

And trust me…

Research sometimes is more intense than coding 😅

First Question: What Stack Am I Using?

I had to clearly decide:

• Backend?
• Frontend?
• Database?
• Hosting? No more “just testing.”

Now it’s architecture thinking.

Backend Decision

I chose:

FastAPI

Why?

Async support

Clean structure

Perfect for API-heavy systems

Lightweight

Since my project is social media automation, it’s API-first.
So FastAPI makes sense.

Database Decision

After research, relational database fits better.

Users → Platforms → Tokens → Posts.

So PostgreSQL is logical.

Structured. Reliable. Production-ready.

Hosting Research

I checked:

• VPS (my current setup)
• Railway
• Firebase
• Render

For simple website? Many options work.

But for:

• OAuth
• Background workers
• Persistent Telegram connections
• Token refresh
• You need proper server. Conclusion?

My VPS is strong enough if configured correctly.

How Buffer Makes It “One Click”?

I also researched tools like:

• Buffer
• Sprout Social At first I thought:

“How are they making it so easy?”

Click → Allow → Done.

Looks simple.

But internally?

• OAuth redirects
• Token exchange
• Encryption
• Refresh tokens
• Database storage

It’s not magic.

It’s architecture.

Understanding OAuth Flow

When user clicks:

“Connect LinkedIn”

It redirects to:

LinkedIn

User clicks “Allow.”

Platform sends back authorization code.

Backend exchanges code for access token.

Token gets encrypted and stored.

That’s it.

The complexity is hidden behind good UX.

Architecture Thinking

Now I’m planning:

• Separate service layer per platform
• Unified post method
• Token refresh handler
• Background worker system
• Clean folder structure Before, I wrote platform code separately.

Now I’m thinking unified architecture.

That’s growth.

Today’s Realization

Automation is not just:

“Write script and post.”

It is:

• OAuth
• Security
• Token lifecycle
• Hosting decisions
• Scalability planning Today was less coding.

More thinking.

And honestly?

That thinking stage is where real engineers are built.

Final Thought

Yesterday was review.

Today was research.

Tomorrow?

Implementation with clarity.

Slowly but surely, this “single click automation” is becoming something serious.

Built with coffee ☕
Debugged with patience 🧠
And powered by curiosity 🚀