<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Flask on Gaurav.dev</title><link>/tags/flask/</link><description>Recent content in Flask on Gaurav.dev</description><generator>Hugo</generator><language>en-US</language><copyright>© 2026 Gaurav. Built with care and clean code.</copyright><lastBuildDate>Fri, 24 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/flask/index.xml" rel="self" type="application/rss+xml"/><item><title>Flask, FastAPI, or Bottle: Choosing a Python Microframework</title><link>/posts/flask-fastapi-bottle-python-api/</link><pubDate>Fri, 24 Jul 2026 00:00:00 +0000</pubDate><guid>/posts/flask-fastapi-bottle-python-api/</guid><description>&lt;p&gt;Python gives API teams an unusual amount of choice. Flask, FastAPI, and Bottle can all expose an HTTP endpoint in a few lines, but they optimise for different kinds of simplicity. Choosing well means looking beyond the first route and asking how the service will be validated, tested, deployed, and changed.&lt;/p&gt;&#10;&lt;h2 id="flask-flexible-and-proven"&gt;Flask: flexible and proven&lt;/h2&gt;&#10;&lt;p&gt;Flask is the dependable general-purpose option. Its request model is easy to understand, its extension ecosystem is mature, and experienced Python developers can recognise a Flask application quickly. It works especially well for internal tools, integration services, conventional REST APIs, and products that need freedom without inventing the entire HTTP layer.&lt;/p&gt;</description></item></channel></rss>