How Soma App was made - TECHNICAL

How Soma App was made - TECHNICAL

10 months ago
2 min read
2 reads
376 words

On the technical side, we’ve made some significant architectural upgrades. To begin with, we introduced Flask as a helper service. All the heavy backend workloads—recommendations, writer scoring, podcasts processing, digest email generation, and re-engagement pushes—have been migrated from Express to Flask. The reason is simple: Flask is lightweight, portable, and quick to iterate with, which is ideal for a one-man engineering team.

We now run a real-time sync worker in Express that continuously syncs operational data to the Flask service. Along with this move, we also migrated our analytics pipeline to Flask and PostgreSQL, allowing us to run daily data analysis with far more flexibility and performance than before.

The main application still runs on Express, Redis,...

Want to read more stories like this?

Join our community to unlock premium stories, track your reads, and discover amazing content!

Loading comments...

Related Stories

No related stories available.

Explore More Topics

No topics available at the moment

How Soma App was made - TECHNICAL | Soma Stories