Skip to content
Tutorials Center
My learning

Topics

Lesson 3 of 39 ยท Getting Started

The Now Platform Architecture

Understand how a ServiceNow instance is built: single-tenant instances, the application layer, the relational database, server and client scripting, and the MID Server.

Knowing what runs where makes every later topic easier. When a script behaves differently on the form than in a list, or an integration cannot reach a server inside your office, the explanation is almost always architecture. This lesson gives you the mental model without drowning you in infrastructure detail.

Single-tenant instances

ServiceNow uses a multi-instance, single-tenant design. Each customer gets their own instance, with its own application code and its own database, rather than sharing one big database with all other customers. Your data never mixes with another customer's at the database level, and each customer decides when to upgrade.

Most organizations run several instances in a chain:

Instance Purpose
Development (dev) Build and configure changes
Test / QA / staging Verify changes with test data
Production (prod) Real users and real data

Changes are moved up the chain as update sets or application packages, not copied by hand. A later lesson covers that.

The request path

Browser Forms, lists, portal.
App server Runs the platform and scripts.
Database Tables and records.
Integrations REST, MID Server, email.

Every page load crosses these layers.

1 / 2

The layers

Browser (client). The interface you see is HTML, CSS and JavaScript running in your browser. Client scripts and UI policies run here, so they can react instantly while you type.

Application server (server). A Java application server runs the platform: it receives requests, checks access control, runs business rules, builds responses and talks to the database. Server-side scripts are written in JavaScript and executed by an engine inside the Java process (historically Mozilla Rhino; newer releases offer a more modern JavaScript mode, so check the current documentation for the language level you can use).

Database. Records live in a relational database. You do not write SQL to use the platform; the GlideRecord API and the table APIs generate queries for you. Behind it every table is a set of columns and rows, and every row has a sys_id, a 32-character unique identifier.

Metadata. Tables, fields, forms, rules and scripts are themselves records in system tables (like sys_db_object for tables and sys_dictionary for fields). That is why you can customize ServiceNow by editing records and why changes can be exported as update sets.

Client side versus server side

This split decides which tool to choose:

Client side Server side
Runs in The user's browser The instance's app server
Examples Client scripts, UI policies Business rules, script includes, flows
Good for Show/hide fields, instant checks Data integrity, security, integrations
Trust level Low, can be bypassed High, always enforced

Never rely on client-side logic alone for security or required data, because an import, an API call or a script bypasses the form. Enforce the rule on the server too (a data policy, a business rule or an ACL).

The MID Server

An instance lives in the cloud, but a company's servers are often inside a private network. The MID Server (Management, Instrumentation and Discovery) is a small Java program you install inside your network. It opens an outbound connection to the instance, picks up jobs (discovery scans, integration calls) and returns results. Because the connection is outbound only, you do not have to open inbound firewall ports.

Python Which layer runs it? (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Data and request flow

When you open an incident:

  1. The browser requests the form for incident and a record sys_id.
  2. The server checks the ACLs (can you read the table, the record, each field?).
  3. The server loads the record, applies display business rules, and builds the form definition plus field data.
  4. The browser draws the form and runs client scripts and UI policies.
  5. When you save, the browser sends the changes; the server runs before business rules, writes the record, then runs after business rules, updates audit and journal data and queues notifications.
Python A tiny layered request (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Upgrades and releases

ServiceNow delivers new features as family releases about twice a year and fixes as patches and hot fixes. Because every customer instance is separate, the customer schedules the upgrade. Skipping customization and using configuration keeps upgrades smooth, and ServiceNow's upgrade tooling reports where your changes collided with the new release (skipped changes).

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does 'single-tenant' mean for ServiceNow?

    Each customer gets dedicated instances, so data is not mixed with other customers' data.
  2. 2. Where do UI policies and client scripts run?

    They run on the client, which is why they cannot be your only protection for data integrity.
  3. 3. What is the MID Server used for?

    The MID Server runs inside your network, connects outbound to the instance and performs discovery and integration jobs.
  4. 4. Where do metadata such as table definitions live?

    Platform metadata is stored as records, which is what makes it exportable in update sets.

Summary

  • Each customer has private, single-tenant instances (dev, test, prod).
  • A request passes browser, application server, database and sometimes the MID Server.
  • Client-side logic is quick but bypassable; enforce rules on the server.
  • Metadata are records, so configuration can be moved as update sets.
  • Upgrades arrive in family releases that the customer schedules.

Next: Your First Incident