Software Architecture on jason grey

Enterprise Rust 2025: Overview

Fri, 04 Apr 2025 00:00:00 +0000

Introduction to Enterprise Applications with Rust Link to heading

In the world of software development, the term “enterprise” often evokes images of bloated, legacy systems that are difficult to maintain and extend. However, this perception doesn’t capture the essence of what modern enterprise applications can and should be. In this blog series, we’ll explore how Rust—a language known for its performance, reliability, and increasingly rich ecosystem—is becoming a compelling choice for building enterprise-grade applications.

Enterprise Rust 2025: Framework Analysis

Fri, 04 Apr 2025 00:00:00 +0000

Framework Analysis and Selection for Rust Enterprise Applications Link to heading

When building enterprise applications with Rust, selecting the right frameworks and libraries is crucial for long-term success. In this post, we’ll analyze the Rust ecosystem for enterprise development, providing data-driven comparisons and practical guidance for making informed decisions.

The Rust Framework Landscape Link to heading

Unlike ecosystems such as Java with Spring or .NET with ASP.NET, Rust doesn’t have a single dominant “enterprise framework” that provides an all-in-one solution. Instead, Rust follows a more modular approach, with specialized libraries that excel at specific tasks and can be composed together.

Enterprise Rust 2025: Core Components

Fri, 04 Apr 2025 00:00:00 +0000

Core Components for Rust Enterprise Applications Link to heading

Building robust enterprise applications requires careful consideration of core components that handle data persistence, communication between services, and message processing. In this post, we’ll explore how to implement these essential components in Rust, focusing on database management, modularization approaches, internal RPC mechanisms, and message queuing systems.

Database Management in Rust Link to heading

Data persistence is fundamental to most enterprise applications. Rust offers several approaches to database management, each with different trade-offs between type safety, performance, and developer experience.

Enterprise Rust 2025: Application Development

Fri, 04 Apr 2025 00:00:00 +0000

Application Development with Rust for Enterprise Systems Link to heading

Building enterprise applications requires a diverse set of tools and approaches depending on the target platform and user interface requirements. In this post, we’ll explore how Rust can be used to develop web, CLI, desktop, and mobile applications for enterprise environments.

Web Application Development Link to heading

Web applications are a common requirement for enterprise systems. Rust offers several approaches to building web frontends, from server-side rendering to WebAssembly.

Core Components - Enterprise Rust

Wed, 01 Nov 2023 00:00:00 +0000

Series Outline Link to heading

Overview
Framework analysis and selection: Delving into the specifics of framework selection and application.
1. Core Components: Database management, modularization, internal RPC, AMQP.
2. Web and API: Web Server, GraphQL API.
3. Application Development: Web, CLI, desktop, and mobile app development.
4. Miscellaneous Tools: Observability, logging, machine learning.
Boilerplate project: A comprehensive guide including setup instructions for selected frameworks, architectural diagrams, and development environment configurations.

Modularization Link to heading

Modularization is important in big software projects. It’s like building with Lego blocks – each piece of code is its own little block. This makes it easier for different teams to work on their own parts without messing up the whole thing. It’s also great for fixing bugs and adding new features, since you only have to change one block at a time. Plus, you can reuse these blocks in other projects, saving time and hassle. In short, modularization keeps everything organized, flexible, and easy to handle, especially when things need to change fast.

Overview - Enterprise Rust

Fri, 20 Oct 2023 00:00:00 +0000

Introduction to Enterprise Applications Link to heading

The term “enterprise” in the context of software development often elicits mixed reactions. However, for the purpose of this discussion, let’s define an enterprise application as a comprehensive, collaboratively developed solution that adheres to high standards of long-term maintenance. Such an application is characterized by its modular design, both internally and externally, ease of integration, and its ability to address complex business challenges efficiently and reliably.

Migrations are hard...

Tue, 09 May 2023 00:00:00 +0000

Watched this video today. It talks about how migrations are some of the harder problems in tech, but, nobody likes to work on them :)

I actually LIKE such migrations:

Challenging: Matt is very right - it is usually VERY hard to do this well.
Meta: You get to learn how someone else did something - and have to understand it enough to refactor it away gradually.
Rewarding: the migration usually needs to happen for some really interesting business/user experience reason.

Much of the focus of my professional life has been what I’d call “cleaning up other people’s messes” - migrating them from a messy/slow/non-expandable system to some new thing. Always during such projects one must think about how to elegantly migrate users from one system to another - ideally, without them even noticing. That’s the part I like the best - if I can pull it off without users noticing, I feel extra clever.

What makes a good component/service?

Wed, 01 Oct 2008 00:00:00 +0000

A few collected thoughts & notes from around the web regarding what makes a good component/service.

Interface - all implementations share this. Should have few methods, use data objects as return values, take primitives as inputs, throw only custom exceptions, and be very, very well documented.
Implementations - implement the logic behind the service. May provide extra features such as caching, or such things as optional collaborations.
Data - data objects this service deals with. Should be immutable, comparable, cloneable as much as is possible. Should be serializable/XML/Persistance annotated in most languages.
Storage - Data (or data.io) package should define storage API, and an in-memory data store. Allow other services/projects/subprojects to define database backed or other kinds of data stores.
Cache - Data.Cache packages should define cache API? (or can this be standard per runtime?) Who should be in charge of caching? The service itself, or the user of the service?
Use dependency injection for all services/data stores it requires. Use constructor-injection as much as possible.
Throw errors early - in constructor if possible.
Exceptions - custom exceptions for high level categories of erroneous behavior (try not to do one for every possible condition - classify, and wrap). * Don’t re-throw exceptions from other frameworks - wrap in custom exception.
Make behavior configurable via dep injection as much as possible. Use filters or strategies.
Inject 1 configuration object instead of many options. Standardize on configuration API/Framework for each runtime/language.
Standardize on logging framework/API for each runtime/language, and make sure it’s used (instead of System.out or similar)
Provide events/messages and/or hooks for important happenings so others can do things pre/post.

Mach-II first blush

Thu, 27 Nov 2003 00:00:00 +0000

I recently have evaluated the Mach-II framework for ColdFusion MX. I started by developing our company holiday party RSVP website. It used a pretty simple form bean, and some standard “manager”, “dao”, and “gateway” objects, as shown in the Mach-II developer guide. My initial thoughts are very favorable:

Cleanly supports writing your code in a re-useable way.
Much more object oriented than fusebox.
Very good framework for MVC development.
Fast - I like how many objects are stored in application scope, so they don’t have to be instantiated every request.

I’ve also started developing some base objects, filters, plug-ins and other useful tools which others may find useful, I’ll post them up here soon.