Bring structure to #AI coding - "spec-driven" development.
fmodel.fraktalio.com/distill
26.09.2025 12:40
👍 1
🔁 0
💬 0
📌 0
Bring structure to #AI coding - "spec-driven" development.
fmodel.fraktalio.com/distill
Data, in its raw form, is simply a collection of facts and figures. The real value emerges when we analyze this data, uncovering patterns and insights. Effective data analysis leads to informed decision-making, and ultimately, innovation.
#EventSourcing
fmodel.fraktalio.com/event-sourcing
The meaning of an object isn't in its internal structure, but in how it responds to interaction.
You can collapse the object into a point, and focus on the arrows going into and out of it.
Only by poking it - observing both what goes in and what comes out - do you come to understand what it is.
🕐 Destructuring the past into the present 🕒
♥️ A different perspective on #EventSourcing ♥️
You "selectively" match on past events to validate commands.
It's just like destructuring in programming.
This #Kotlin Gist is a runnable engine that models "any" system. gist.github.com/idugalic/bc7...
But... that's just one side of the coin.
🧠 The Engine – Generalization
- Clean, abstract, domain-agnostic
❤️ The Steering Wheel – Specification by Example
- Directs the engine to serve real human needs
Do not model the current state of the world, model how you get there!
#EventSourcing #DomainModeling
fmodel.fraktalio.com
#Kotlin #TypeScript #Rust
The Events We Store, The Stories They Tell.
Money matters, but so does how you earn it. Where are the bottlenecks in your business flow? Are inefficiencies hiding in plain sight?
#SoftwareDesign #EventSourcing #DomainModeling
www.linkedin.com/pulse/design...
Accelerate the development of compositional, safe, and ergonomic applications with #KotlinServerSide. 🚀
Clarify requirements seamlessly using #EventModeling and #EventSourcing.
Learn more: fraktalio.com/fmodel/
Rust’s powerful type system provides an exceptional way to model your domain effectively and efficiently.
By separating functions from data, you gain flexibility in your deployment:
👉 Execute directly within the database
👉 Or deploy on the server, connected to the database.
fraktalio.com/run-in-db
👋 New here? We're AxonIQ—pioneers in making event sourcing easy.
Here’s the deal: #EventSourcing doesn’t have to feel like rocket science. We make it accessible, scalable, and—dare we say—enjoyable. Follow us if you’re into solutions, not buzzwords. #SoftwareArchitecture #EventDriven
Seems like a safe bet that object storage as a foundation of data systems architecture is here to stay blog.colinbreck.com/predicting-t...
We could go on about how we welcome publishers, we don't demote links, we encourage independent developers to build apps and extensions on top of Bluesky's network.... but instead, we'll show you.
All thanks to the incredible community here! 🦋
AWS advertises 99.999999999% (11 nines) durability for S3. I think that's per object per year. Sounds great until you realise that S3 stores 280 trillion = 2.8*10^14 objects (source: www.allthingsdistributed.com/2023/07/buil...). That suggests S3 is corrupting somebody's objects many times per year.
🚀 Exciting news! Our latest reference guide for the Fmodel #TypeScript library is now live! Dive in, to explore advanced #DomainModeling, #EventSourcing, and #InformationSystems techniques.
Check it out here: fraktalio.com/fmodel-ts/
Building #better #software #faster? 💻🚀
Remember: When developing an information system, you're modeling the business. Your abstractions, behaviors & UI all reflect the domain. Get the model right, and everything clicks! 🔑 #DomainModeling
fraktalio.com/blog/
You are welcome Jan!
Being able to run your deciders in a single transaction or in a distributed setting is a decision that we can postpone. It is very powerful.
Does adding new features or requirements to your information system force you to revisit the old design (`change` old Decider)?
Or, we combine/`add` a new EmailVerificationDecider with the old UserRegstrationDecider?
A design capable of evolving in this way is not only robust but also future-proof
It is very common scenario of having some rule/invariant between two (or more) deciders. In that case, it is valuable to combine them on the core domain layer.
Example: github.com/fraktalio/fm...
Hi Jan. If there is no rule/invariant between the Deciders (Event of first should trigger the Command of second) you can wrap them in independent handlers, sure. Nevertheless, combining them in a single Decider and exposing a single Handler (application layer) will act as a Command router/bus.
🚀 Explore our @deno.land demo app!
🌟 Harness the power of #EventSourcing with the #Deno KV database.
🔗 Demo: github.com/fraktalio/fm...
💡 Build compositional, ergonomic apps faster in #TypeScript: fraktalio.com/fmodel-ts/
I love #Kotlin! Its powerful, #composable, and ergonomic type system makes encoding complex information systems a breeze. 🚀💻 #Coding #Programming #DomainModeling
gist.github.com/idugalic/bc7...
fraktalio.com/fmodel/
When designing systems, the way we model our business domain fundamentally shapes how we operate. By formally modeling the `state` of our system and the `events` that led to that state, we open the door to two approaches:
- State Stored System
- Event Sourced System
gist.github.com/idugalic/bc7...
Hello Bluesky, as of today, I will start sharing my content here about #DomainModeling, #EventSourcing, #Kotlin, #TypeScript...
Hi, I am working on an open-source library fraktalio.com/fmodel/
"Functional, Algebraic and Reactive #DomainModeling"
I write about #InformationSystems and #Kotlin
fraktalio.com/blog/
I put together a #Kotlin / #KotlinMultiplatform starter pack based on folks I follow here. If you're Kotlin dev related, feel free to comment below, and I will add you!
Reposts appreciated 💜!
go.bsky.app/BV8HXZ1