bunny-storm
fastapi-crudrouter
| bunny-storm | fastapi-crudrouter | |
|---|---|---|
| 4 | 4 | |
| 23 | 1,317 | |
| - | - | |
| 0.0 | 0.0 | |
| over 2 years ago | 7 months 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.
bunny-storm
- Framework/Library/Template for Event-driven Microservices with RabbitMQ
- I would really love to get feedbacks! I have developed a RabbitMQ asynchronous connector library for Python (named Bunny-Storm). It contains an easy one-liner implementation for asynchronous RPC pattern over Rabbit (https://github.com/PythonCloudFrameworks/bunny-storm)
- I would really love to get your feedbacks! (especially if you are a backend developers who building microservices). I have developed a RabbitMQ asynchronous connector library for Python (named Bunny-Storm). It contains an easy one-liner implementation for asynchronous RPC among other features.
fastapi-crudrouter
-
why when I search for Python jobs I find alot! but when I search for Django (the most used Python framework ) I get few compared to spring or nodejs ?
FastAPI does have an equivalent. Something like this? https://github.com/awtkns/fastapi-crudrouter
- FastAPI CRUD Router
-
FUNCTOOLS CHANGED MY LIFE
I can't show any pics cuz of uk NDA and all that. I can tell you the gist of it though. FastAPI is already pretty good at the abstraction part. Our middleware had a lot of rerouting and it was basically just a bunch of redundant functions. I just used this cool ass package https://fastapi-crudrouter.awtkns.com/ and used the partial function from functools to generate endpoints for every scenario/db tables.
-
FastAPI framework, high perf, easy to learn, fast to code, ready for production
Thanks, that's a really helpful example.
Where I think this could be taken to the next level of reusability is in modularising the front-end into API-specific components. For example, the login behaviour could depend on FastAPI-Users, with a sibling frontend library containing components that implement the same login flow. Adding user behaviour is then a matter of using the same third-party library on the front and back end.
This approach could be extended to other components such as an admin panel (perhaps using https://github.com/awtkns/fastapi-crudrouter), or a blogging component.
What are some alternatives?
aiorabbit - An AsyncIO RabbitMQ client for Python 3
starlite - Light, Flexible and Extensible ASGI API framework | Effortlessly Build Performant APIs [Moved to: https://github.com/litestar-org/litestar]
aiomultiprocess - Take a modern Python codebase to the next level of performance.
Flask-AppBuilder - Simple and rapid application development framework, built on top of Flask. includes detailed security, auto CRUD generation for your models, google charts and much more. Demo (login with guest/welcome) - http://flaskappbuilder.pythonanywhere.com/
Propan - Propan is a powerful and easy-to-use Python framework for building event-driven applications that interact with any MQ Broker
fastapi-users - Ready-to-use and customizable users management for FastAPI
b-rabbit - A thread safe library that aims to provide a simple API for interfacing with RabbitMQ. Built on top of rabbitpy, the library make it very easy to use the RabbitMQ message broker with just few lines of code. It implements all messaging pattern used by message brokers
mangum - AWS Lambda support for ASGI applications
zero - Zero: A simple and fast Python RPC framework
Dask - Parallel computing with task scheduling
taskiq-aio-pika - AMQP broker for taskiq
openapi-generator - OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3)