Inventory App Part 0. Foundations

Inventory App Part 0. Foundations

Inventory App Part 0. Foundations

Scala end to end

In Scalac we believe that Scala is a great general-purpose language, that helps you to build high-quality software quickly. And although Scala shines in the backend, its use is not limited to server-side programming. With these blog posts, we would also like to convince all of you that it’s possible to build a full stack application using only Scala.

This, and the following blog posts from the series, are an experiment proving that the Scala ecosystem is mature enough to be the main driving force for building production-ready apps. Although I would not recommend using Scala only for its hype, I want to show that it’s a viable alternative for freelancers, startups, and enterprises looking for a full-stack technology.

Application

The application that we are going to build is a simple inventory manager. It will keep some information about items and where they are located. It’s not much, but we will improve and grow the application while we introduce new libraries and approaches to the mix.

Application layers:

  • database layer – Software Transactional Memory approach with Activate Framework
  • API layer – brand new Akka HTTP in action
  • web client – done with Scala.js
  • mobile app – Android application created with Scaloid

You can track the progress on Inventory App

Summary

I hope this short post will get you interested in the series I’m preparing for you. The first “real” part is coming soon and next will be published every 1-2 weeks.

Links

Do you like this post? Want to stay updated? Follow us on Twitter or subscribe to our Feed.

See also

Get the State of

Scala 2025 report

Download now

Authors

Patryk Jażdżewski
Patryk Jażdżewski

I'm a software consultant always looking for a problem to solve. Although I focus on Scala and related technologies at the moment, during the last few years I also got my hands dirty working on Android and JavaScript apps. My goal is to solve a problem and learn something from it. While working with teams I follow "The Boy Scout" Rule - "Always check a module in a cleaner state than when you checked it out". I think this rule is so good, that I extend it also to other aspects of software development - I try to improve communication patterns, processes and practices ... and all the things that might seem non-technical but are vital to success.

Latest Blogposts

02.07.2026 / By 

THE SIGNAL: What matters in distributed systems | #4

AI agents pushed GitHub to 275 million commits a week, and Microsoft's own cloud couldn't keep up. Microsoft and JetBrains just placed opposite bets on who should own the harness your coding agents run in.

01.07.2026 / By  , Piotr Bandurski

Rust as the A2A Orchestrator: What We Learned Building a Multi-Agent System

Minimalist Scalac hero graphic with a black Rust crab at the center, connected to chat, routing, context, code, UI, and database components in an A2A multi-agent system.

What we learned building a Rust orchestration layer for a real multi-agent AI system — from A2A protocol churn and manual agent loops to Agent Skills and context design.

18.06.2026 / By 

AI Agents Are Distributed Systems. Why Scala’s Type Safety Matters More Than Prompts

Scalac blog hero image showing AI agents as a distributed system with connected service nodes.

AI agents fail at system boundaries, not in prompts. Here's where Scala's type safety helps when LLM pipelines move from prototype to production.

software product development

Need a successful project?

Estimate project