Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -185,10 +185,12 @@ Why Crawlee is the preferred choice for web scraping and crawling?

### Why to use Crawlee rather than Scrapy?

- Crawlee has out-of-the-box support for **headless browser** crawling (Playwright).
- Crawlee has a **minimalistic & elegant interface** - Set up your scraper with fewer than 10 lines of code.
- Complete **type hint** coverage.
- Based on standard **Asyncio**.
- **Asyncio-based** – Leveraging the standard [Asyncio](https://docs.python.org/3/library/asyncio.html) library, Crawlee delivers better performance and seamless compatibility with other modern asynchronous libraries.
- **Type hints** – Crawlee is a new project built with modern Python, and complete type hint coverage for a better developer experience.
- **Minimalistic and elegant interface** – Set up a functional scraper in fewer than 10 lines of code, keeping things clean and simple.
- **Headless browser support** – Crawlee natively supports the headless browser crawling via [Playwright](https://playwright.dev/python/).
- **State persistence** – Unlike Scrapy, Crawlee supports state persistence during interruptions, saving time and costs by avoiding the need to restart scraping pipelines from scratch after an issue.
- **Separated result storage** – Crawlee provides an easy option for separated result storages ([datasets](https://crawlee.dev/python/api/class/Dataset) & [key-value stores](https://crawlee.dev/python/api/class/KeyValueStore)) for a single scraping run.

## Running on the Apify platform

Expand Down
Loading