Overview

You can utilize Entropy as a backend solution for any kind of web service project. Whether it's a single-page web app for personal use or a complex enterprise-grade application suite, Entropy is a great choice for building and maintaining your backend systems.

Entropy offers a wide palette of tools that help you express your backend logic whilst maintaining clean architecture.

This chapter is a semi-comprehensive primer on Entropy project architecture and composition. Following sections gradually introduce information - including internal and external concepts - essential to understanding the Entropy workflow and managing applications written thereon.

You are encouraged to read through, have fun!

Architecture

Entropy follows the MVC pattern. It means that your application consists of three main parts:

• Models: represent your data structures (in case of Entropy they are represented by database schema)
• Controllers: handle requests and define application logic
• Views: render the final output to the user

Directory Structure

The default Entropy application structure consists of several directories and files. In this section you can learn about their purposes.

• database: contains Prisma database schema and migrations
• public: stores static assets like CSS styles and images that are publicly accessible for the client
• src: contains your application source code
• views: contains view templates and layouts