Chrome driver restrictions for Selenium Web Scraping at Scale

Question

I plan to use the Selenium Chrome Driver for my project, which will be used for web cleaning on several public websites (something like a kayak or skyscanner). So there will be a REST GET endpoint where my backend will run mute Chrome to clear multiple websites and ultimately return managed JSON.

I want to know how scalable the Chrome Driver is, since it seems that when using the query, you do not need to start the Chrome instance without any problems.

Updated: Question Using Google Chrome Headless

Answer 1

, phantom js, . , .

:

1)It will fail to recognize the browser elements like id,xpath,csselector
when compared to chrome driver.
2)If you have login mechanism ,redirects won't work as you expect when compared to chrome driver.
3)You need to manually implement the custom logic for screen shots for the test failures if you need it.
4)If you want to switch between multiple drivers like chrome,html etc then it is very difficult

:

1)Test case execution is faster when compared to chrome driver
2)No browser is required it will run without GUI. 
3)No much configurations are needed when compared to chromedriver.

html-, , phantom, , .

Answer 2

, PhantomJS.

Chrome "" . " Chrome" , PhantomJS, . , PhantomJS , .

Selenide :

Configuration.headless = true;

Answer 3

? Chrome