How to Design a Simple Ticket-Tracking Information System from Scratch

·1 views

A tutorial published on DEV Community walks through the architecture of a basic internal ticket-tracking system, using it as a practical example to explain how information systems work. The system is designed for organizations where employees report technical issues, such as a broken printer, and support staff update ticket statuses after resolution. The author breaks the system into three core layers: a user interface, a server-side backend, and a relational database. Using PostgreSQL, the article demonstrates how to model two linked tables — users and tickets — connected by a one-to-many relationship to avoid data duplication. The goal is not to build a production-ready product but to illustrate how the key components of an information system interact with each other.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How Static Code Analysis Tools Like PHPStan and Psalm Improve PHP Development

Static code analysis tools such as PHPStan, Psalm, and Rector are widely available to PHP and Symfony developers, yet many teams use them only superficially to pass CI checks rather than as a core part of their workflow. Unlike black-box testing, static analysis is a white-box technique that reads source code directly, scanning all execution paths to detect type mismatches, null-reference errors, and unused variables without running the application. The approach offers broader coverage than unit tests and operates significantly faster, sweeping entire codebases in seconds. The Symfony framework is particularly well-suited to static analysis due to its explicit coding conventions, ecosystem-specific plugins like phpstan-symfony, and built-in CLI linters for YAML, Twig, and service containers. Integrating these tools into pre-commit hooks or CI pipelines can automate routine code-review tasks, freeing developers to focus on solving business problems.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How Schema Drift Crashed a Crypto Dashboard and What Fixed It

CryptoPulse Terminal, a lightweight real-time cryptocurrency dashboard built with React and TypeScript, suffered a complete page crash when the CoinGecko API returned a 429 rate-limit response during high-volatility trading periods. Because TypeScript only validates types at compile time, the app blindly parsed unexpected API payloads, causing a fatal runtime error when React components tried to access properties on undefined objects. The crash rendered a blank white screen for traders, potentially obscuring critical market movements. Developers resolved the issue by adding runtime guards: checking HTTP response status codes, validating the API payload structure before updating state, and using optional chaining in the UI layer. The fix also introduced dedicated loading and error states, giving users clear feedback and a retry option instead of a silent crash.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Amlaki Engineers Detail State Machine Design for Saudi Ejar Lease Contract Workflow

Saudi real estate platform Amlaki has published a technical breakdown of its lease contract registration workflow built around Saudi Arabia's government Ejar platform. The system follows a strict request lifecycle — validation, fee computation, wallet debit, and request creation — before moving through four tightly defined states: PENDING, IN_PROGRESS, COMPLETED, and REJECTED. Engineers deliberately limited the number of states, arguing that a state only justifies its existence if system behavior differs within it, not merely its description. Both terminal states are explicitly guarded in code to prevent duplicate refunds from concurrent admin actions. Amlaki notes it has not yet joined Ejar's official digital integration program and currently routes registrations through a licensed broker.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Kairi is an open-source local AI chat tool that filters LLM outputs for accuracy

Kairi is a locally run, bring-your-own-key (BYOK) chat application that applies a post-generation filter pipeline to LLM responses before they reach the user. Unlike most chat interfaces that display model output directly, Kairi runs named checks for false citations, numeric errors, misattributed quotes, and stale date references after each response. The tool includes a market-focused reference app supporting US and Japan trading sessions, which serves as a real-world testbed for the grounding pipeline. Users can flag suspicious responses, which are logged and converted into regression test cases to permanently strengthen the filter layer. The project is open-source on GitHub and can be run in demo mode without an API key using Docker.

0 comments Read more at DEV Community