Alessandro Macrí

𝗛𝗲𝘆, .𝗡𝗘𝗧 𝗗𝗲𝘃𝘀- 𝗦𝘁𝗿𝘂𝗴𝗴𝗹𝗶𝗻𝗴 𝘄𝗶𝘁𝗵 𝗧𝗮𝗻𝗴𝗹𝗲𝗱 𝗖𝗼𝗱𝗲𝗯𝗮𝘀𝗲𝘀? 𝗥𝗲𝗳𝗮𝗰𝘁𝗼𝗿 𝘀𝗺𝗮𝗿𝘁𝗲𝗿 𝘄𝗶𝘁𝗵 𝗗𝗗𝗗 𝗶𝗻𝘀𝗶𝗴𝗵𝘁𝘀 I am honored to receive a launch copy of 𝗗𝗼𝗺𝗮𝗶𝗻-𝗗𝗿𝗶𝘃𝗲𝗻 𝗥𝗲𝗳𝗮𝗰𝘁𝗼𝗿𝗶𝗻𝗴 𝘄𝗿𝗶𝘁𝘁𝗲𝗻 𝗯𝘆 Alessandro Colla and Alberto Acerbis. As I read through the book, I keep agreeing with its ideas, seeing how valuable it is for developers dealing with old, complicated systems. Whether you're migrating a legacy system to a modern architecture or starting a new project from scratch, you’ll find value in this book. 𝗞𝗲𝘆 𝗛𝗶𝗴𝗵𝗹𝗶𝗴𝗵𝘁𝘀 𝗼𝗳 𝘁𝗵𝗲 𝗕𝗼𝗼𝗸: ↳ 𝗖𝗹𝗲𝗮𝗿 𝗖# 𝗲𝘅𝗮𝗺𝗽𝗹𝗲𝘀 that simplify key concepts. ↳ Simple breakdown of 𝘁𝗮𝗰𝘁𝗶𝗰𝗮𝗹 𝗮𝗻𝗱 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝗰 𝗗𝗗𝗗 𝗽𝗮𝘁𝘁𝗲𝗿𝗻𝘀. ↳ Uses 𝘁𝗼𝗼𝗹𝘀 𝗹𝗶𝗸𝗲 𝗖𝘆𝗻𝗲𝗳𝗶𝗻 𝗳𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸, residuality, and EventStorming. ↳ 𝗕𝗿𝗲𝘄𝗲𝗿𝘆 𝗘𝗥𝗣 case study that’s relatable yet insightful. ↳ Practical tips to connect 𝗗𝗗𝗗 𝘄𝗶𝘁𝗵 𝗺𝗼𝗱𝗲𝗿𝗻 𝗖𝗜/𝗖𝗗 𝗳𝗹𝗼𝘄𝘀 ↳ .NET code with 𝗗𝗼𝗰𝗸𝗲𝗿 𝗮𝗻𝗱 𝗥𝗮𝗯𝗯𝗶𝘁𝗠𝗤 𝗲𝘅𝗮𝗺𝗽𝗹𝗲𝘀 for CQRS, Sagas, and modular monoliths. 𝗣𝗮𝗿𝘁 𝟯: 𝗠𝘆 𝗳𝗮𝘃𝗼𝗿𝗶𝘁𝗲 𝘀𝗲𝗰𝘁𝗶𝗼𝗻 𝗼𝗳 𝘁𝗵𝗲 𝗯𝗼𝗼𝗸 Why? Because it tackles one of the biggest challenges in modern software architecture. That is, when and how to transition to microservices. 𝗪𝗵𝘆 𝗬𝗼𝘂 𝗦𝗵𝗼𝘂𝗹𝗱 𝗥𝗲𝗮𝗱 𝗜𝘁? Are you a software architect or .NET developer? Do you want to improve your application's scalability and maintainability? Perfect. I highly encourage you to read this book. 📖 𝗚𝗲𝘁 𝗬𝗼𝘂𝗿 𝗖𝗼𝗽𝘆 𝗧𝗼𝗱𝗮𝘆 🔗 𝗣𝗮𝗰𝗸𝘁: https://lnkd.in/d_MnGYAR 🙏 A big thank you to Packt and Mansi S. for sharing this insightful launch copy. ♻️ If you find this content useful, please repost it to spread the knowledge. 🔔 Follow me and click the notification bell icon to get all my latest posts. (Ajay Patel) #DDD #dotnet #csharp

104

11 commenti

𝗔 𝗿𝗲𝗮𝗹-𝘄𝗼𝗿𝗹𝗱 𝗴𝘂𝗶𝗱𝗲 𝗳𝗿𝗼𝗺 𝘁𝗮𝗻𝗴𝗹𝗲𝗱 𝗰𝗼𝗱𝗲 𝘁𝗼 𝗰𝗹𝗲𝗮𝗻 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 I recently had the chance to read 𝐃𝐨𝐦𝐚𝐢𝐧-𝐃𝐫𝐢𝐯𝐞𝐧 𝐑𝐞𝐟𝐚𝐜𝐭𝐨𝐫𝐢𝐧𝐠 by Alessandro Colla and Alberto Acerbis And as someone who works daily with cloud-native systems and Go-based architectures, I wanted to explore how this book captures modern refactoring principles.. What really stood out to me in this book and something you don’t see often 𝐡𝐨𝐰 𝐭𝐨 𝐝𝐨 𝐫𝐞𝐟𝐚𝐜𝐭𝐨𝐫𝐢𝐧𝐠 𝐟𝐫𝐨𝐦 𝐚 𝐦𝐨𝐧𝐨𝐥𝐢𝐭𝐡 𝐭𝐨𝐰𝐚𝐫𝐝 𝐝𝐞𝐞𝐩 𝐝𝐨𝐦𝐚𝐢𝐧 𝐮𝐧𝐝𝐞𝐫𝐬𝐭𝐚𝐧𝐝𝐢𝐧𝐠 𝐚𝐧𝐝 𝐦𝐨𝐝𝐮𝐥𝐚𝐫 𝐚𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞, 𝐰𝐢𝐭𝐡𝐨𝐮𝐭 𝐣𝐮𝐦𝐩𝐢𝐧𝐠 𝐢𝐧𝐭𝐨 𝐦𝐢𝐜𝐫𝐨𝐬𝐞𝐫𝐯𝐢𝐜𝐞𝐬 𝗪𝗵𝗮𝘁 𝗱𝗼𝗲𝘀 𝘁𝗵𝗮𝘁 𝗺𝗲𝗮𝗻 🤔 ❌This book doesn’t say: "𝑱𝒖𝒔𝒕 𝒈𝒐 𝒔𝒕𝒓𝒂𝒊𝒈𝒉𝒕 𝒕𝒐 𝒎𝒊𝒄𝒓𝒐𝒔𝒆𝒓𝒗𝒊𝒄𝒆𝒔 𝒕𝒐 𝒃𝒆 𝒂 𝒑𝒓𝒐.” ✅Instead, it says: “𝑺𝒕𝒂𝒓𝒕 𝒘𝒊𝒕𝒉 𝒂 𝒘𝒆𝒍𝒍-𝒔𝒕𝒓𝒖𝒄𝒕𝒖𝒓𝒆𝒅 𝒎𝒐𝒅𝒖𝒍𝒂𝒓 𝒎𝒐𝒏𝒐𝒍𝒊𝒕𝒉, 𝒘𝒊𝒕𝒉 𝒄𝒍𝒆𝒂𝒓𝒍𝒚 𝒖𝒏𝒅𝒆𝒓𝒔𝒕𝒐𝒐𝒅 𝒄𝒐𝒓𝒆 𝒅𝒐𝒎𝒂𝒊𝒏𝒔, 𝒂𝒏𝒅 𝒐𝒏𝒍𝒚 𝒄𝒐𝒏𝒔𝒊𝒅𝒆𝒓 𝒎𝒊𝒄𝒓𝒐𝒔𝒆𝒓𝒗𝒊𝒄𝒆𝒔 𝒘𝒉𝒆𝒏 𝒚𝒐𝒖𝒓 𝒔𝒚𝒔𝒕𝒆𝒎 𝒓𝒆𝒂𝒄𝒉𝒆𝒔 𝒂 𝒄𝒆𝒓𝒕𝒂𝒊𝒏 𝒍𝒆𝒗𝒆𝒍 𝒐𝒇 𝒎𝒂𝒕𝒖𝒓𝒊𝒕𝒚.” 𝗪𝗵𝘆 𝗱𝗶𝗱 𝗶𝘁 𝗰𝗹𝗶𝗰𝗸 𝗳𝗼𝗿 𝗺𝗲? 🔹 Most books push theory or microservices early. This one offers a 𝐩𝐫𝐚𝐜𝐭𝐢𝐜𝐚𝐥 𝐩𝐚𝐭𝐡 𝐟𝐫𝐨𝐦 𝐦𝐞𝐬𝐬𝐲 𝐜𝐨𝐝𝐞 𝐭𝐨 𝐜𝐥𝐚𝐫𝐢𝐭𝐲 🔹 It shows how to apply 𝐓𝐚𝐜𝐭𝐢𝐜𝐚𝐥 𝐃𝐃𝐃 𝐢𝐧𝐬𝐢𝐝𝐞 𝐚 𝐦𝐨𝐧𝐨𝐥𝐢𝐭𝐡, using a 𝐦𝐢𝐜𝐫𝐨𝐬𝐞𝐫𝐯𝐢𝐜𝐞 𝐦𝐢𝐧𝐝𝐬𝐞𝐭, but without splitting yet 🔹 It gives a step-by-step guide: ✳️ Identify subdomains ✳️ Modularize around business rules ✳️ Move toward bounded contexts ✳️ Apply CQRS/eventing gradually ✳️ Split into microservices only when necessary 𝗔𝗯𝗼𝘂𝘁 𝘁𝗵𝗲 𝗰𝗼𝗱𝗲 The examples in the book use an object-oriented style, but that doesn’t mean Go developers can’t benefit from it, and here’s why: 🔸 The core concepts of Domain-Driven Design and Refactoring 𝐚𝐩𝐩𝐥𝐲 𝐭𝐨 𝐚𝐧𝐲 𝐥𝐚𝐧𝐠𝐮𝐚𝐠𝐞, 𝐰𝐡𝐞𝐭𝐡𝐞𝐫 𝐢𝐭’𝐬 𝐆𝐨, 𝐉𝐚𝐯𝐚, 𝐏𝐲𝐭𝐡𝐨𝐧 𝐨𝐫 𝐞𝐯𝐞𝐧 𝐂++ (like bounded contexts, aggregates, value objects and entities) 🔸The book teaches you how to structure your code 𝐚𝐫𝐨𝐮𝐧𝐝 𝐭𝐡𝐞 𝐝𝐨𝐦𝐚𝐢𝐧, 𝐧𝐨𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐟𝐫𝐚𝐦𝐞𝐰𝐨𝐫𝐤𝐬 𝐨𝐫 𝐭𝐞𝐜𝐡𝐧𝐢𝐜𝐚𝐥 𝐥𝐚𝐲𝐞𝐫𝐬 and that mindset works perfectly in Go. 🔸You can apply the same steps in Go, even with a different syntax Huge thanks to Packt for sharing this with me. If you're a developer, an engineer, software architect or simply someone working with evolving systems this book should be on your reading list. You can check it out here: Amazon: https://lnkd.in/dBkuCxac Packt: https://lnkd.in/db4RqTNt #DomainDrivenDesign #Microservices #SoftwareArchitecture #Refactoring #Engineering #Packt #Developers

91

9 commenti

🦀 Rust Tip, Base64 Encoding (No Padding, URL Safe) Need to encode data in Base64 for URLs or tokens? This one-liner gives you exactly that, without the annoying = padding!  • URL-safe characters  • No padding (=)  • Great for JWTs, short IDs, and query params 🦀 Fast, safe, and idiomatic, the Rust way! #RustLang #Base64 #RustTips #WebDev

51

4 commenti

🚨 𝗬𝗼𝘂𝗿 𝗡𝗲𝘅𝘁.𝗷𝘀 𝗽𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻 𝗯𝘂𝗶𝗹𝗱 𝗺𝗶𝗴𝗵𝘁 𝗯𝗲 𝟮𝟬× 𝗯𝗶𝗴𝗴𝗲𝗿 𝘁𝗵𝗮𝗻 𝗶𝘁 𝗻𝗲𝗲𝗱𝘀 𝘁𝗼 𝗯𝗲! 🚨 😱 I keep seeing this MASSIVE mistake in production deployments and it's making apps unnecessarily HUGE! 📦💥 🔴 𝗠𝗼𝘀𝘁 𝗱𝗲𝘃𝘀 𝗿𝘂𝗻 𝗻𝗲𝘅𝘁 𝗯𝘂𝗶𝗹𝗱, 𝘁𝗵𝗲𝗻 𝗱𝗲𝗽𝗹𝗼𝘆 🔴 1️⃣ Their full source code (sometimes) 📄 2️⃣ The ENTIRE node_modules folder 📚 3️⃣ The .next folder 🗂️ ⚠️ Even for a tiny app, that can mean a WHOPPING 200+ MB bloating your server! 🐘 ✅ 𝗕𝗲𝘁𝘁𝗲𝗿 𝘄𝗮𝘆 (GAME CHANGER!) ✅ In your next.config.js, enable the standalone build with just ONE simple setting! 🔥 ================= // next.config.js module.exports = { output: 'standalone' } ================= 🚀 𝗧𝗵𝗶𝘀 𝘄𝗶𝗹𝗹 𝗱𝗼 𝘁𝗵𝗲 𝗳𝗼𝗹𝗹𝗼𝘄𝗶𝗻𝗴 𝘁𝗵𝗶𝗻𝗴𝘀... 🚀 1️⃣ Tree-shakes unused code like magic! 🌳✨ 2️⃣ Bundles ONLY what's actually used! 📦✂️ 3️⃣ Produces a .next/standalone folder that's usually just 5-10 MB (depending on your libraries) 🤏🏻 💎 No full node_modules upload needed! Just 𝗱𝗲𝗽𝗹𝗼𝘆 the .𝗻𝗲𝘅𝘁/𝘀𝘁𝗮𝗻𝗱𝗮𝗹𝗼𝗻𝗲 folder to your 𝘀𝗲𝗿𝘃𝗲𝗿 and watch the magic happen! ✨ 💯 𝗧𝗵𝗲 𝗿𝗲𝘀𝘂𝗹𝘁𝘀 𝘄𝗶𝗹𝗹 𝗯𝗹𝗼𝘄 𝘆𝗼𝘂𝗿 𝗺𝗶𝗻𝗱! 💯 📉 DRAMATICALLY smaller deployments! ⚡ LIGHTNING-FAST startup times! 🧹 Super clean servers! 🤔 I'm curious... have YOU tried 𝘀𝘁𝗮𝗻𝗱𝗮𝗹𝗼𝗻𝗲 builds with 𝗡𝗲𝘅𝘁𝗝𝗦 yet? Drop a comment below! 👇🏻 hashtag #NextJS hashtag #WebPerformance hashtag #DeploymentOptimization hashtag #FrontendTips hashtag #WebDevelopment hashtag #JavaScript hashtag #ServerOptimization hashtag #DevOps hashtag #NextJSTips hashtag #WebDev hashtag #PerformanceHacks hashtag #CodeOptimization hashtag #ReactJS hashtag #ServerlessDeployment

57

10 commenti