Create the Droplet

Plan cost, region, and size

Choose the smallest useful server near its users and understand which resources keep billing until you remove them.

8 minute lesson

~~~

Choose the server from the workload you have now. A small site or learning project can normally start on a Basic shared-CPU plan. Dedicated CPU or a larger machine becomes useful when measurements show sustained CPU pressure, memory pressure, or storage I/O problems.

Do not choose a size from traffic alone. A quiet application with a large in-memory process can need more RAM than a busy static site.

Make the placement decision

Choose a region close to the people and services that exchange the most data with the application. If the application uses a managed database, keep both in the same region unless you have a deliberate reason not to. This reduces latency and avoids sending private service traffic across distant networks.

Before creating anything, record:

  • the region
  • expected RAM, CPU, and disk needs
  • whether backups and improved monitoring will be enabled
  • the monthly estimate shown by the control panel
  • any extra volumes, snapshots, or reserved addresses

Treat the control-panel estimate as the evidence. Prices and available plans change, so a copied price from an old tutorial is not reliable.

A powered-off Droplet still reserves resources and continues billing. Billing ends when you destroy the Droplet. Backups, snapshots, volumes, and reserved addresses are separate resources and can continue billing after the server disappears.

Starting too large wastes money. Starting too small without monitoring creates unexplained crashes. The safe approach is to begin with a reasonable minimum, enable metrics, and resize after you can point to the constrained resource.

Resizing upward is usually easier than moving to another region. A region change normally means creating another server, copying state, testing it, and moving traffic. Choose the region carefully now.

For your learner action, write a one-paragraph capacity guess for the notes application. Include the expected users, persistent data, region, initial plan category, and the metric that would justify a resize. We will compare that guess with real measurements later.

Lesson completed

Take this course offline

Get every free book and course as PDF and EPUB files.

Get the download library →