Arkency

Join Łukasz Reszke on 31 March 7 PM (CET) to discuss rewrite vs modernization subject. You’ll learn the pros and cons of rewriting vs modernizing. Plus, he'll reveal alternative strategies beyond costly rewrites and slow modernizations.

Arkency is hosting From React to Hotwire - an unexpected journey. Make sure to attend it today!

Join us for an exclusive webinar where Maciek 🤖 Korsan will share his journey transitioning from React to Hotwire. Discover how to simplify frontend development in Rails, build dynamic UIs without the complexity of React, and unlock the full potential of Hotwire in 2025. Don’t miss it!

Are you DDD, Event Sourcing enthusiast working in Ruby on Rails looking to expand their knowledge? Join our online workshop and - Discover business insights that guide purposeful code design, - Redesign existing classes to be smaller and better aligned with business goals, - Get started with Event-Driven Design, - Build a reliable audit log using Event Sourcing,

- Do I need to use a framework to do #EventSourcing? - You should. - Why? - Do you play piano? - Yes, I'm quite good. - Do you know how to build a piano? - No, absolutely not. 🙈 Curtain... 🎹 A pianist doesn't need to understand the intricate mechanics of hammer actions or string tensioning to create beautiful music. They need a well-crafted instrument that lets them focus on what matters: the melody, the composition, the story they want to tell. 🛠️ Similarly, Event Sourcing frameworks and libraries (like Axon Framework from AxonIQ, Jeremy Miller Marten, Arkency RailsEventStore etc.) are your piano - they handle the complex mechanics so you can focus on your domain's melody. 🤯 Just as a pianist wouldn't craft their own piano (though theoretically, they could), a developer shouldn't need to build their own Event Sourcing solution. While it's possible, it's better to rely on solutions crafted by those who have already solved the complex challenges like scalability, projections, versioning etc. 🤔 After all, would Chopin have created such masterpieces if he had to build his own piano first? Which frameworks do you recommend? #EventSourcing #DomainDrivenDesign #SoftwareArchitecture #Programming #CQRS #SoftwareDevelopment #Piano #Analogy #NaKodach #ZycieNaKodach #DDDHeroes #NaKodachPL

Are you frustrated because you are working on application that is difficult to maintain? Introduce new features takes way more time than it should? Such situation often leads to dissatisfaction among stakeholders, who may suggest decisions like changing the technology. Migrate to NodeJS, anyone?  Why would that help? Well... Btw. this is not unique phenomenon. It exists outside of the Rails world as well. But we'll get to that. The problem is not the technology itself. Even in 2025, we think Rails will still be a good choice and an excellent way to start building a business. Rails is fantastic for building applications. It doesn't limit you in any way. The same cannot be said for RailsWay. Common challenges with Rails include callbacks and performance issues when rendering pages. It's important to realize that the key is not the technology itself (Rails), but how we use it (e.g. with callbacks). Yes, yes... but we are already here in this... mud. If you have similar thoughts, we'd like to invite you to a webinar where we'll show you how to overcome typical Rails challenges. We will also explore whether Rails will still be a viable option in 2025. Then we'll have a Q&A session. It's all free. Does that resonate with you? Sign up for the webinar: https://lnkd.in/eBn-5_3z