graph_wrap
fastapi
graph_wrap | fastapi | |
---|---|---|
5 | 469 | |
84 | 71,023 | |
- | - | |
0.0 | 9.8 | |
about 1 year ago | 8 days ago | |
Python | Python | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
graph_wrap
-
Just curious if anyone else here auto-generates DRF APIs through meta programming?
This doesn't directly answer the question, but I wrote a library which uses meta programming to build a GraphQL Graphene API from a DRF API https://github.com/PaulGilmartin/graph_wrap. Maybe it's the type of thing which would interest you.
-
Django REST Framework: Stop Nesting Serializers and use GraphQL Instead
Enter GraphQL: GraphQL is designed so that the client decides what info it receives from the server, not the other way around. Whilst many great packages exist to create a GraphQL API from scratch, migrating an mature production REST API to use one of these frameworks is not so simple. It may also be that our REST API has functionality which is not available on a GraphQL specific API. This is where GrapWrap comes in: by adding two lines of code to your project, GraphWrap exposes a GraphQL schema which has the same "shape" as your existing REST API. With this new endpoint, we can now stop overexposing the author fields and instead simply expose author as a URL:
-
Building GraphQL APIs in Django with Graphene
I attempt to give a use case for user defined queries here: https://github.com/PaulGilmartin/graph_wrap#which-problems-does-graphwrap-address
-
GraphWrap: extend your Django REST Framework API with a GraphQL interface with just two of lines of code.
See Which problems does GraphWrap address for more.
fastapi
-
Github Sponsor Sebastián Ramírez Python programmer
He is probably most well know for creating FastAPI that I taught to some of my clients and Typer that I've never used.
-
Python: A SQLAlchemy Wrapper Component That Works With Both Flask and FastAPI Frameworks
It has been an interesting exercise developing this wrapper component. The fact that it seamlessly integrates with the FastAPI framework is just a bonus for me; I didn't plan for it since I hadn't learned FastAPI at the time. I hope you find this post useful. Thank you for reading, and stay safe as always.
-
FastAPI Best Practices: A Condensed Guide with Examples
FastAPI is a modern, high-performance web framework for building APIs with Python, based on standard Python type hints.
-
Building an Email Assistant Application with Burr
In this tutorial, I will demonstrate how to use Burr, an open source framework (disclosure: I helped create it), using simple OpenAI client calls to GPT4, and FastAPI to create a custom email assistant agent. We’ll describe the challenge one faces and then how you can solve for them. For the application frontend we provide a reference implementation but won’t dive into details for it.
-
FastAPI Got Me an OpenAPI Spec Really... Fast
That’s when I found FastAPI.
-
How to Deploy a Fast API Application to a Kubernetes Cluster using Podman and Minikube
FastAPI & Uvicorn
-
Analysing FastAPI Middleware Performance
Discussion at FastAPI GitHub: https://github.com/tiangolo/fastapi/issues/2696
-
LangChain, Python, and Heroku
An API application framework (such as FastAPI)
-
Litestar – powerful, flexible, and highly performant Python ASGI framework
It’s been my experience that async Python frameworks tend to turn IO bound problems into CPU bound problems with a high enough request rate, because due to their nature they act as unbounded queues.
This ends up made worse if you’re using sync routes.
If you’re constrained on a resource such as a database connection pool, your framework will continue to pull http requests off the wire that a sane client will cancel and retry due to timeouts because it takes too long to get a connection out of the pool. Since there isn’t a straightforward way to cancel the execution of a route handler in every Python http framework I’ve seen exhibit this problem, the problem quickly snowballs.
This is an issue with fastapi, too- https://github.com/tiangolo/fastapi/issues/5759
-
AI-Powered Image Search with CLIP, pgvector, and Fast API
Fast API.
What are some alternatives?
strawberry - A GraphQL library for Python that leverages type annotations 🍓
AIOHTTP - Asynchronous HTTP client/server framework for asyncio and Python
zimagi - Zimagi - Modular Data Integration, Distributed Processing, and API Publishing Platform
HS-Sanic - Async Python 3.6+ web server/framework | Build fast. Run fast. [Moved to: https://github.com/sanic-org/sanic]
Tornado - Tornado is a Python web framework and asynchronous networking library, originally developed at FriendFeed.
django-ninja - 💨 Fast, Async-ready, Openapi, type hints based framework for building APIs
Flask - The Python micro framework for building web applications.
swagger-ui - Swagger UI is a collection of HTML, JavaScript, and CSS assets that dynamically generate beautiful documentation from a Swagger-compliant API.
Django - The Web framework for perfectionists with deadlines.
starlite - Light, Flexible and Extensible ASGI API framework | Effortlessly Build Performant APIs [Moved to: https://github.com/litestar-org/litestar]
BentoML - The most flexible way to serve AI/ML models in production - Build Model Inference Service, LLM APIs, Inference Graph/Pipelines, Compound AI systems, Multi-Modal, RAG as a Service, and more!
django-rest-framework - Web APIs for Django. 🎸