Видео

Thank you @allalonetech 🙌!! I have more Docker videos coming up, about SQLAlchemy, Django, GraphQL, and API security 🚀🚀

@@microapis we need FastApi first

Thank you for your kind comment 🙏! I'm really glad to hear you find the content helpful 🙌!

Hi sorry for my late reply! I have a tutorial about deploying FastAPI applications to AWS serverless: ruclips.net/video/CTcBLrR32NU/видео.html. Deployment is straightforward and works fairly well for most use cases. The only thing to bear in mind about AWS serverless is that you'll have a max timeout of 30 seconds and the process will exit after that. Only question is how are you using Celery? Is it for long-running background tasks?

@@microapis Thank you for the response! Yes, my background task takes a long time, from a few minutes to an hour. I generate images for my content using OpenAI.

​@@vladyslavprykhodko2155 sorry for my late reply! Background tasks won't do well in serverless since the whole process will exist as soon as the API returns or times out. In this setup, I'd recommend using an SQS queue to manage the tasks and a separate Lambda to process those tasks asynchronously. That way, the asynchronous Lambda will have up to 15 minutes to do the job. If what you're doing is generating images, you can upload those images to s3 and you can serve them from there. All of those would be fairly cheap to operate since the Lambdas only run when needed and s3 costs are minimal for a task like this

Thank you I'm so glad you found it useful 🙌! Flask is an excellent choice and very powerful when used properly. Good luck with your project and feel free to reach out if you have any questions!

with auth0 i don't understand))

Sure! Feel free to ping me on Discord, my handle is @joseharoperalta. I've also created a Discord community for people interested in APIs, feel free to join if you'd like to: discord.gg/fCjxmfJv

Hi Pavel thank you for your kind words! That's a great idea I'll put together an example of using RBAC in an API!

Thank you for your kind words 🙏! Really glad to hear you found it useful 🙌🙌!

Thank you for your comment I'm really glad to hear you found it helpful 🚀!

Thank you 🚀🚀!!

Trying to help as many people as possible 😄!

Thank you 🙌!

Thank you for your kind words 🙏🙏! Will be in Korea 🇰🇷 in September, looking to arrange an API security workshop!

Thank you for your supportive comment Danny 🙌!! Aiming to post the next video later this week 🚀🚀!!

Thank you for your kind comment and for the suggestions 🙏!! I have those videos in the pipeline for the coming weeks 🙌!

Thank you for your kind words 🙏! This is the exact reason why I created this channel 🚀🚀!

Thanks for your support 🙌!

Thanks for your support 🙌!

Great video an Example with springboot would be helpful

@@ankitpatil5231 Thank you for your support and your suggestion 🙌! I'll look into putting together a tutorial as soon as I can!

Thank you Kelvin 🙌!

Thanks for your question! Permission sets are collections of IAM policies. With IAM policies, you can be absolutely granular on how users can access resources. So you can create a policy that gives read-only access to a specific S3 bucket, or a certain path within that bucket. Another policy with specific permissions to an EC2 instance or an RDS database, and so on. Then you can bring those policies together under a permission set. Is that the kind of access control you're looking for?

Thank you for your kind comment and your support 🙌!

It's my pleasure thank you for your comment 🙌!

Thank you for your support 🙌!

Not sure if you’re commenting on the right video but to clarify this is a video about middleware, specifically about web middleware. Middleware is a layer of software that sits between the receiving end of your server and your controllers and allows you to apply various processing steps on each request

Thank you for your kind comment @rafaelfurquim745 🙌!

Thank you was a great pleasure meeting you too and I really enjoyed our conversation! Wish you the very best with your projects too and looking forward to seeing them grow. Hope we can see each other again!

Thank you for your comment and your suggestions 🚀🚀! I'm currently working on new tutorials about auth/authz with the latest version of FastAPI and I'll show how to do this with dependency injection, integrations with auth0, okta, and more! How are you planning to customise openapi with the API routes?

Thank you for your supportive comment @venil82 🙌!

Thank you for your question! You'd follow the same approach shown in the video, only applying the filters first. Here's an example: @router.get("/jobs", response_model=ListJobs) def list_jobs(contract_type: ContractTypeEnum | None = None,): with session_maker() as session: query = select(Job) if contract_type: query = query.where(Job.contract_type == contract_type.value) count = session.execute( select(func.count()).select_from(query.subquery()) ).scalar_one() This endpoint returns a list of jobs and allows you to filter by contract type. The filter is optional and None by default, so first we check if it's set, and if so, we apply the filter to the query. Once we've filtered the result set, we count the items. Hope this helps, if you have any more questions please let me know!

Thank you for your supportive comment @kingsleyakpan3828!

Thank you @jasonhall6526 🙌🚀🚀!!

Thank you for your question! A workaround would be serving the Swagger UI assets from your own domain. For example, you can download the assets here: cdn.jsdelivr.net/npm/swagger-ui-dist/. You could serve them from Flask, from an S3 bucket if you use AWS, from Cloudflare if you use that, or any other alternative.

Thanks for your comment @RamiAwar! This is a great discussion. First of all 💯 repository isn't suitable in all situations - if it doesn't help it has no place in our codebase. Re joins and subqueries - I think this is query repository shines. You are simply encapsulating the complexity of those queries away from your business and other layers. The example in the video may give the wrong impression that repository is a 1-to-1 between classes and tables, but that's not how it works in practice. Domain models usually pull data from multiple tables and the repository should serve those needs. Ideally, repository doesn't return SQLAlchemy objects, but DTOs or something similar like you say. In the tutorial, the repo's add() method returns an instance of a plain Booking object (github.com/abunuwas/repository-pattern-tutorial/blob/master/data_access/repository.py#L24) and the list() method returns a list of dictionaries (github.com/abunuwas/repository-pattern-tutorial/blob/master/data_access/repository.py#L14). A plain and simple DTO would be a better choice. Personally, I only use the repository pattern when I want to enforce a clear separation between data access and other layers for testing and other purposes, and when queries are growing complex and I want to abstract them away from the business layer. Hope these comments help and thanks again for sharing your thoughts!

Thank you for your kind words and for visiting 🙌!