Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

*I dont understand the reason for* <https://orion-docs.prefect.io/collections/catalog/|Collections>.

For example, there is a SQLAlchemy Collection which can use `prefect_sqlalchemy.database.sqlalchemy_execute` to send a SQL statement to a DB.  But I can do that with with the sqlalchemy python library directly and write flows around that.

I must be missing the point?

I also do not understand the use case yet to be completely honest with you :sweat_smile:

Collections are entirely optional. Their main purpose is easy integration with a wide variety of systems without you having to write that code e.g. code to talk to SQL alchemy

Think of it the same way as any Python package: sure, you could use CSV reader, but you could also import a CSV file in a single line of Pandas 

Additionally collections have blocks which allow to combine business logic with secure configuration and credentials data

I guess sqlalchemy isnt the best example. I see the slack alert one incudes decorators, its convenient to use the collection vs write similar code for each application.

_edit_: <https://khuyentran1401.github.io/prefect-alert/|prefect-alert> labelled as "Alert" on Collections page.  This makes the usage more clear to me. Thanks again!