Simo Roikonen
@simoroikonen
Followers
28
Following
26
Media
21
Statuses
30
Complex Domains ↣ Evolvable Backends ↣ Low Latency at Any Scale #ScalableModeling
Joined July 2009
"It's developer (mis)understanding that gets released, not the experts' knowledge.".Alberto Brandolini. Understanding the domain is crucial for an accurate model. Event-centrism aids discovery, and event immutability is key to #ScalableModeling. #EventStorming @avanscoperta
0
0
0
Scalability Challenge 3/3: Time Travel ⏱️.In #DistributedSystems, data often appears at different times due to inevitable consistency delays. To manage this ‘time travel’ effect and keep system integrity, versioning and clear cause-effect flows are essential. #ScalableModeling
0
0
0
Scalability challenge 2/3: Tailoring Consistency ✂️ Strong consistency is the wrong default. Tailoring consistency helps optimize performance without compromising integrity. #DistributedSystems #Scalability #EventSourcing #ScalableModeling
0
0
0
Scalability challenge 1/3: Deduplication 👯♂️ Exactly-once delivery is unachievable in distributed systems, so we rely on effectively-once or idempotent processing to ensure duplicate messages don’t affect outcomes. #DistributedSystems #Scalability #ScalableModeling
0
0
0
Querying the command model in #CQRS is often debated. While it’s not designed for querying, limited reads can be useful — e.g. in clustered, in-memory models (Akka-style) for quick state access post-update. Still, querying should be rare and justified. #ScalableModeling
0
0
0
The three dimensions to scalability - AKF Scale Cube:. 1️⃣ Decomposition: Scale by splitting different things .2️⃣ Duplication: Scale by cloning data or instances. 3️⃣ Partitioning: Scale by splitting similar things into many partitions. #ScalableModeling helps you to reach them.
0
0
0
#ScalableModeling.𝗖𝗼𝗺𝗺𝗮𝗻𝗱 Initiate action.𝗖𝗼𝗺𝗺𝗮𝗻𝗱 𝗠𝗼𝗱𝗲𝗹 Validate commands.𝗣𝗿𝗶𝘃𝗮𝘁𝗲 𝗘𝘃𝗲𝗻𝘁 Capture changes.𝗤𝘂𝗲𝗿𝘆 𝗠𝗼𝗱𝗲𝗹 Optimize data retrieval.𝗤𝘂𝗲𝗿𝘆 Request data.𝗣𝗼𝗹𝗶𝗰𝘆 Define business rules.𝗣𝘂𝗯𝗹𝗶𝗰 𝗘𝘃𝗲𝗻𝘁 Announce changes
1
0
1
𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗶𝘀 𝘂𝗹𝘁𝗶𝗺𝗮𝘁𝗲𝗹𝘆 𝗮 𝗺𝗼𝗱𝗲𝗹 — an invisible yet powerful solution to real challenges. In software engineering, the key steps are:.𝗪𝗛𝗬 ↔ 𝗪𝗛𝗔𝗧: Conceptual model design↔𝗛𝗢𝗪.#ScalableModeling bridges WHY to HOW, with 𝗳𝗼𝗰𝘂𝘀 𝗼𝗻 𝗪𝗛𝗔𝗧.
0
0
0
“Doing the 𝘄𝗿𝗼𝗻𝗴 𝘁𝗵𝗶𝗻𝗴 𝗿𝗶𝗴𝗵𝘁 is not nearly as good as doing the 𝗿𝗶𝗴𝗵𝘁 𝘁𝗵𝗶𝗻𝗴 𝘄𝗿𝗼𝗻𝗴.” 𝘙𝘶𝘴𝘴𝘦𝘭𝘭 𝘓. 𝘈𝘤𝘬𝘰𝘧𝘧.In SW engineering, we often focus 𝗛𝗢𝗪 rather than 𝗪𝗛𝗬+𝗪𝗛𝗔𝗧. #ScalableModeling ➡ WHY to HOW but 𝘀𝘁𝗿𝗲𝘀𝘀 𝗼𝗻 𝗪𝗛𝗔𝗧.
0
0
0
After 10 years in software #Scalability & #DistributedSystems, I'm celebrating by gathering what I’ve learned into a webpage on a modeling technique for scalable systems — called #ScalableModeling. Hope it helps! #CQRS #EventSourcing #DDD #EventStorming
0
0
0
RT @jboner: Check this one out:. "Inspired by #DomainDrivenDesign (#DDD) and #EventStorming in the modeling phase, I built a horizontally #….
0
2
0
Lucky me! *<:o)
. and our winners was @simoroikonen and @pbvie at the final @scaladays raffle! Berlin was the perfect place for this 2018 Europe edition. The Lunateam thanks all the attendees/speakers/organisers for this wonderful 2018 edition. #scaladays2018 #lightbend #heisegruppe #berlin 🏢
0
0
4
RT @jboner: Snippet from my @reactivesummit keynote today. Why back-pressure/flow control matters:.A fast system should not overload a slow….
0
97
0
0
0
1