While is is still quite easy to deploy a single CD/CM instance for local development (a single website acting as ContentManagement and ContentDelivery) with no xConnect, no Processing and no Reporting, to install anything more complicated than this requires Powershell scripts, Web Deploy Packages.
To this end, Sitecore has produced a number of pre-built topologies which offer combinations of the (now) split out functionality:
XP Single (XP0)
Four Sitecore roles: Content Delivery, Content Management, Processing, and Reporting as a single WebApp instance.
Five xConnect roles: Search, Collection, Reference Data, Marketing Automation, and Marketing Automation Reporting as a single WebApp instance.
XP Scaled (XP1)
Four Sitecore roles: Content Delivery, Content Management, Processing, and Reporting, with each Role as a separate WebApp instance.
Five xConnect roles: Search, Collection, Reference Data, Marketing Automation, Marketing Automation Reporting, with each Role as a separate WebApp instance.
XM Single (XM0)
This is a Sitecore Experience Management configuration that runs the Content Delivery and Content Management roles as a single WebApp instance. (In other words no xConnect applications.)
XM Scaled (XM1)
This is a Sitecore Experience Management configuration that runs both the Content Delivery and Content Management roles, with each Role as a separate WebApp instance. (In other words no xConnect applications.)
xDB Single (XDB0)
Two Sitecore roles: Processing and Reporting as a single WebApp instance.
Five xConnect roles: Search, Collection, Reference data, Marketing automation, and Marketing Automation Reporting as a single WebApp instance. (In other words just xConnect, without any Content Management or Content Delivery applications.)
xDB Scaled (XDB1)
Two Sitecore roles: Processing, and Reporting, with each Role as a separate WebApp instance.
Five xConnect roles: Search, Collection, Reference Data, Marketing Automation, and Marketing Automation Reporting, with each Role as a separate WebApp instance.
The most obvious topology for a local developer instance is XM Single (a.k.a XM0), and for this all that is required, consisting of a single Sitecore instance, connected to the three standard web databases : core, master, web and the forms database. While this would be expected to use Azure search if deployed on the cloud, if installed on-Premises the default Lucene search would continue to operate, as was the norm for Sitecore before the more widespread adoption of SOLR or Azure for Sitecore.
If a developer wanted to have an instance with both a Content Management and Content Delivery server locally, the XM Scaled (XM1) topology would offer this, and if xConnect functionality was required, the XDB0 topology could be added.
Mintydog 