Whats Typescript?

However, the key distinction in the original comparison was about the location and nature of the logic, not the language itself.

• When I said “TypeScript class connected to PocketBase”, I was assuming a common and simple use case: a class within a client-side application (like a React or Angular app) that directly uses the PocketBase SDK to interact with the database. In this scenario, the TypeScript code is the “UI client” because it’s running in the user’s browser, handling the user interface and making direct calls to the PocketBase server.

• The “Flask + PocketBase” setup, on the other hand, describes a separate backend server. This server is not running in the user’s browser; it’s a completely different application. The UI client (which could be written in TypeScript, or any other language) makes requests to the Flask server, and the Flask server then handles the complex logic before communicating with PocketBase.

Where TypeScript can be a backend

You can absolutely use TypeScript to build a backend server, just like you would with Flask or any other backend framework.

For example, you could use a framework like NestJS or Express.js with TypeScript to create a powerful backend API.

In that case, the architecture would look like this:

TypeScript UI Client —(API calls)—> TypeScript Backend Server —(database calls)—> PocketBase

In this architecture, the “TypeScript Backend Server” would be the equivalent of the “Flask” part in the original comparison. It would have the same ability to handle complex logic, middleware, and custom API endpoints.

So, to clarify:

• A TypeScript class in a simple client-side application is the “client.”
• A TypeScript class (or an entire application) can also be a backend server, which would allow it to handle complex logic in the same way Flask does.

The original comparison was designed to highlight the difference between a direct client-to-database connection and a more robust client-to-backend-to-database architecture, regardless of the language used for the client or backend.