Liron Ratzabi

For those who missed it, Java.IL event for May 29 is set and will include three great lectures: 1. Natan Silnitsky from Wix will explain how Wix started with classic CRUD over a Relational Database, during its massive growth phase transitioned to a method called CQRS, and recently moved to CRUD with Event Sourcing. Those who want to understand why should definitely attend this event. I highly recommend it. 2. Ben from Intuit will explain how they implemented a Distributed Rate Limiter over Redis using a library called Bucket4j. 3. Yaron also from Intuit will explain about an open-source library he wrote so they could extract data items from GraphQL Result Node similar to XPath. Many thanks to Intuit for providing us with excellent food (sandwiches, salads, etc.) and beers.

6

12 𝐡𝐨𝐮𝐫𝐬 𝐨𝐟 .𝐍𝐄𝐓 9 𝐨𝐧 𝐩𝐫𝐨𝐝𝐮𝐜𝐭𝐢𝐨𝐧 - 𝐰𝐢𝐭𝐡 1.1 𝐦𝐢𝐥𝐥𝐢𝐨𝐧 𝐫𝐞𝐪𝐮𝐞𝐬𝐭𝐬. 𝐖𝐡𝐚𝐭 𝐢𝐬 𝐭𝐡𝐞 𝐝𝐢𝐟𝐟𝐞𝐫𝐞𝐧𝐜𝐞 𝐭𝐨 .𝐍𝐄𝐓 8? 🚀 As an early adopter, I have already updated all my projects to .NET 9; this was not difficult so far, as I have always tested the release candidates for my libraries, websites and projects anyway. After the release of .NET 9 yesterday, I have now also updated https://myCSharp.de on production - but what difference does it make, do you notice it? 👀 𝓨𝓮𝓼! 𝐂𝐏𝐔 𝐔𝐬𝐚𝐠𝐞 🧮 Since we know .NET and C# very well, we code very well :-), sustainable and very optimized. The CPU has therefore never been a problem for us. Even with bot attacks. However, you can see that CPU usage is much smoother! 𝐓𝐡𝐫𝐞𝐚𝐝 𝐏𝐨𝐨𝐥 🛀 Each request is processed by one thread - and here, too, you can see a very optimized, improved behavior of the thread pool. Fewer are required and they are available more quickly. This makes the application more performant and efficient. 𝐌𝐞𝐦𝐨𝐫𝐲 📝 The biggest improvement is the Memory behavior. We keep a lot stuff in-memory in order to be able to process requests in an optimized way. Without having changed the code, the allocation rate is much lower, the Gen 0 behavior is gigantically better and over all we need 20% less memory to run the platform. ✅ 𝐂𝐨𝐧𝐜𝐥𝐮𝐬𝐢𝐨𝐧 .NET 9 is another huge update - the best .NET we've ever had (it would be silly if it wasn't 😊) I 💚 .NET #dotnet #aspnetcore #dotnet9 #mvpbuzz #mycsharp

137

6 תגובות

𝐄𝐱𝐩𝐥𝐨𝐫𝐢𝐧𝐠 𝐈𝐇𝐨𝐬𝐭𝐞𝐝𝐒𝐞𝐫𝐯𝐢𝐜𝐞 𝐢𝐧 .𝐍𝐄𝐓 𝐂𝐨𝐫𝐞 💡 𝐖𝐡𝐚𝐭 𝐢𝐬 𝐈𝐇𝐨𝐬𝐭𝐞𝐝𝐒𝐞𝐫𝐯𝐢𝐜𝐞? In .NET Core, IHostedService is an interface designed for running background tasks. Think of it as a way to run services that live alongside your main application without blocking its primary operations. IHostedService implementations can start tasks when your application starts and gracefully stop them when the application is shutting down. 🔧 𝐂𝐨𝐦𝐦𝐨𝐧 𝐔𝐬𝐞 𝐂𝐚𝐬𝐞𝐬 𝐟𝐨𝐫 𝐈𝐇𝐨𝐬𝐭𝐞𝐝𝐒𝐞𝐫𝐯𝐢𝐜𝐞 1. 𝐁𝐚𝐜𝐤𝐠𝐫𝐨𝐮𝐧𝐝 𝐉𝐨𝐛𝐬: Perfect for periodic data processing, cleanup tasks, or sending scheduled notifications. 2. 𝐋𝐨𝐧𝐠-𝐫𝐮𝐧𝐧𝐢𝐧𝐠 𝐏𝐫𝐨𝐜𝐞𝐬𝐬𝐞𝐬: Useful for processes that need to persist across the app's lifecycle, like monitoring a queue. 3. 𝐄𝐯𝐞𝐧𝐭 𝐋𝐢𝐬𝐭𝐞𝐧𝐞𝐫𝐬: Ideal for apps that listen for changes in real-time, such as handling messages from message queues like RabbitMQ. 4. 𝐃𝐚𝐭𝐚 𝐅𝐞𝐭𝐜𝐡𝐢𝐧𝐠 𝐒𝐞𝐫𝐯𝐢𝐜𝐞𝐬: Great for services that require regular updates from an external API. 💼 𝐖𝐡𝐞𝐧 𝐭𝐨 𝐔𝐬𝐞 𝐈𝐇𝐨𝐬𝐭𝐞𝐝𝐒𝐞𝐫𝐯𝐢𝐜𝐞? 1. 𝐑𝐞𝐜𝐮𝐫𝐫𝐢𝐧𝐠 𝐁𝐚𝐜𝐤𝐠𝐫𝐨𝐮𝐧𝐝 𝐓𝐚𝐬𝐤𝐬: Tasks like sending emails, syncing data, or cleaning up files work well with IHostedService. 2. 𝐀𝐩𝐩𝐥𝐢𝐜𝐚𝐭𝐢𝐨𝐧-𝐖𝐢𝐝𝐞 𝐋𝐢𝐬𝐭𝐞𝐧𝐞𝐫𝐬: Monitoring queues, websockets, or real-time events. 3. 𝐀𝐬𝐲𝐧𝐜𝐡𝐫𝐨𝐧𝐨𝐮𝐬 𝐎𝐩𝐞𝐫𝐚𝐭𝐢𝐨𝐧𝐬: When you need something to run independently of the main application thread, IHostedService is a perfect fit. #dotnetcore #IHostedService #BackgroundTasks #CSharp #AsyncProgramming #Microservices

15

In my last post, I briefly compared using slots and compound components for creating customizable components. Today, I want to focus more on compound components and explain when it’s a good idea to use them and when it’s better to avoid them. 𝘜𝘴𝘪𝘯𝘨 𝘊𝘰𝘮𝘱𝘰𝘶𝘯𝘥 𝘊𝘰𝘮𝘱𝘰𝘯𝘦𝘯𝘵𝘴 𝘪𝘯 𝘜𝘐 𝘋𝘦𝘷𝘦𝘭𝘰𝘱𝘮𝘦𝘯𝘵 Compound components are a useful pattern in frontend development, especially when you need flexible and scalable UI components. They work well in situations where you have several related components, like when building a form with nested fields or creating a card with customizable parts like the header, title, and body. ✅ 𝘞𝘩𝘦𝘯 𝘵𝘰 𝘜𝘴𝘦 𝘊𝘰𝘮𝘱𝘰𝘶𝘯𝘥 𝘊𝘰𝘮𝘱𝘰𝘯𝘦𝘯𝘵𝘴: - For complex UIs that need different levels of customization. - When components have separate parts that need to work together (e.g., Tabs, Dropdowns, Accordions). ❌ 𝘞𝘩𝘦𝘯 𝘵𝘰 𝘈𝘷𝘰𝘪𝘥 𝘊𝘰𝘮𝘱𝘰𝘶𝘯𝘥 𝘊𝘰𝘮𝘱𝘰𝘯𝘦𝘯𝘵𝘴: - For simple components that don’t need much customization. - For components that are specific to your application, like UserCard or ProductsList. - When using slots or render props would be easier and more straightforward. Compound components can make your code more organized and easier to manage, but they can also add complexity if used too much. It’s important to choose the right approach for each situation! #vuejs #vuejs3 #reactjs #typescript #javascript #frontend

21

🚀 Evolving with .NET Core 🚀 At Trace, our backend journey began with .NET Core 5. Since then, we’ve consistently upgraded through .NET Core 6, 7, 8, and now .NET Core 9. Each new version has brought significant performance improvements, enabling us to better serve our customers. Here’s a comparison of the cold start latency in our API, built with AWS Lambda functions and API Gateway. With the latest upgrade to .NET Core 9 using a custom runtime (Amazon Linux 2023) vs .NET 8 Runtime, we can show some improvement in performance. 🎯 Takeaway: Modern frameworks like .NET Core continue to drive efficiency and scalability, essential for cloud-native solutions. #DotNetCore #AWSLambda #PerformanceOptimization #CloudComputing #NETCore9 #AWS Trace | Certified B Corp™

15

If anyone interested to this book please comment and I will send it to you #Csharp #dotnet #technicalBooks

46

83 תגובות

🚀 .𝑵𝑬𝑻 9 𝒊𝒔 𝒄𝒐𝒎𝒊𝒏𝒈! Only 14 𝐝𝐚𝐲𝐬 𝐥𝐞𝐟𝐭, then .𝐍𝐄𝐓 9 will be released on November 12, 2024! Unfortunately, we won't get extension types after all, which will only come with .NET 10, but we will get : - finally C# 13  - many new features in ASP.NET 9 around Auth, Performance, #Blazor, SignalR and #Security as well as Built-In #OpenAPI Doc Generation - many many many bug fixes in #MAUI - #EFCore 9 gets a quality boost with providers such as #CosmosDB, generally better query generation (we will still need LinqKit), native paging - with ML.NET 4.0 the latest version for #MachineLearning features #dotnet #aspnetcore #mvpbuzz #maui #dotnet9 #csharp

20

Hello C# 13! 😍😍 Check out the latest .NET announcements and updates from Microsoft Build 2024. Discover the new features and tools designed to make .NET development faster and easier. #microsoft #developer #dotnetdeveloper #coding

8

🚀 𝗘𝗺𝗯𝗿𝗮𝗰𝗲 𝘁𝗵𝗲 𝗣𝗼𝘄𝗲𝗿 𝗼𝗳 .𝗡𝗘𝗧 𝟵 𝗳𝗼𝗿 𝗠𝗶𝗰𝗿𝗼𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀 🚀 With .NET 9, we're not just evolving — we're 𝘁𝗿𝗮𝗻𝘀𝗳𝗼𝗿𝗺𝗶𝗻𝗴 the way microservices work to be faster, safer, and more efficient! This isn’t just an upgrade; it’s a 𝗴𝗮𝗺𝗲-𝗰𝗵𝗮𝗻𝗴𝗲𝗿 for modern development. ✨ Here’s why .NET 9 is a must-have for microservices: - ⚡ 𝗕𝗹𝗮𝘇𝗶𝗻𝗴 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 𝘄𝗶𝘁𝗵 𝗡𝗮𝘁𝗶𝘃𝗲 𝗔𝗢𝗧: Reduce startup times and boost responsiveness. - 🔗𝗦𝗲𝗮𝗺𝗹𝗲𝘀𝘀 𝗴𝗥𝗣𝗖 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗼𝗻: Smooth and secure service interactions. - 🛠 𝗘𝗻𝗵𝗮𝗻𝗰𝗲𝗱 𝗠𝗼𝗻𝗶𝘁𝗼𝗿𝗶𝗻𝗴 𝘃𝗶𝗮 𝗢𝗽𝗲𝗻𝗧𝗲𝗹𝗲𝗺𝗲𝘁𝗿𝘆: Proactive monitoring for early issue detection. - 🌐 𝗟𝗶𝗴𝗵𝘁𝘄𝗲𝗶𝗴𝗵𝘁 𝗖𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿𝘀:Optimized deployments with lower cloud costs. - 🛡 𝗦𝘁𝗿𝗼𝗻𝗴𝗲𝗿 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆: Built-in TLS and API security for peace of mind. - 🔄 𝗦𝗶𝗺𝗽𝗹𝗶𝗳𝗶𝗲𝗱 𝗠𝗮𝗶𝗻𝘁𝗲𝗻𝗮𝗻𝗰𝗲:Faster upgrades and cleaner code. 💡 Ready to unlock new possibilities? 👉 Check out our upcoming FREE Master Class by Shailendra Chauhan: Building .NET Microservices with Kafka at ScholarHat Register Now: https://bit.ly/48HUH09 Don't miss this opportunity to learn from an expert! #Microservices #DotNet9 #CloudDevelopment

7

4 תגובות

Behind this small page of documentation are months and months of work of several teams: https://lnkd.in/dQhMiUWd #oneteamonescore You can now Bring Your Own Key #byok to your tenants in Auth0; if that's a bit too much for your use-case, we have you covered anyway with Control Your Own Key #cyok capabilities. Pick & choose!

37

Two years ago KDAB organized a cool event - Qt Developers Conference. I talked there about CI/CD. To my mind, it is one of the first steps that you should take in order to check on the quality of your software solutions continuously 🥇 This knowledge is still relevant :) The title of the talk was "Cross-platform Qt CI/CD setup - make it easy!" and you can find it here: https://lnkd.in/di_UX77v   I finally made a blog post out of it: https://lnkd.in/gQfAaMvi   You can find there: ✔️ Reasons to introduce CI/CD in your project and profits that are effects of doing that ✔️ Story from my personal career as a software engineer about the results of not introducing CI/CD in your organization ✔️ Basics of CI/CD - what does it mean, what steps are usually included, how typical CI/CD setup at Scythe Studio looks like, what would you need to introduce CI/CD in your project ✔️ Example of GitLab CI/CD configuration for cross-platform #qt project I share on LinkedIn my thoughts and content often about #softwaredevelopment, Qt, QML, C++, and running the company. If you find this interesting, feel free to follow me 🔔😀 #qtdev #scythestudio #crossplatform #qml #cpp #devops #gitlab

28

🚨 The top 6 signs that your ViewModel implementation is wrong, and 5 ways to correct these mistakes. 🚨 𝗠𝗩𝗩𝗠 is a common Android architecture and it is supposed to be fairly straightforward. Yet many developers seem to get the 𝗩𝗶𝗲𝘄𝗠𝗼𝗱𝗲𝗹 part wrong. This includes Google developers. Here are clues that your implementation is wrong: 1. You have to update your ViewModel when switching from XML to Jetpack Compose. 2. Your ViewModels have Android dependencies. 3. Your View is telling the ViewModel what to do. 4. Your ViewModel is incredibly complex. 5. Your ViewModel holds state. 6. Your ViewModel handles UI concerns, such as configuration changes (I'm looking at you, Google). 7. You're using MVI (just kidding, but I had to go there) So, how do we make things right? 💡 Follow these guidelines: 1. Implement your ViewModel 𝗯𝗲𝗳𝗼𝗿𝗲 implementing the UI. Don't consider HOW data is represented. Focus on WHAT is shown and what events you care about. 2. Don't use Google's Architecture Components for ViewModels. This addresses point 6 above, too. 3. Prefix all of the ViewModel's public function names with "on" to get into the right mindset of reporting events to the ViewModel. 4. Handle UI logic in the UI. This includes configuration changes, multiple item selection and sorting. 5. Keep state in one place: it's source of truth. UI holds its state, as do data sources (API/cache). 6. Don't use MVI (had to go there again...) To read more about this, check out my book, Clean Architecture for Android 👉 https://amzn.to/4bjEPkn You can also see an example here: 👉 https://lnkd.in/eTnfMCJv and here 👉 https://lnkd.in/ekmP5Gc3 #androiddev #cleanarchitecture #android #kotlin #mvvm

113

17 תגובות

Would you like to hear about #platform_engineering in .NET? There is my recent talk to watch: https://lnkd.in/dpfBKGnz I am trying to close a gap in understanding what #IDP is, what is its ultimate goal, how big is landscape of „technical platform” and show few examples of usage in .NET. Enjoy watching! :) PS. I am talking also a bit about #DevOps methodology and philosophy :)

7

#RabbitMQ Streams is a feature introduced to provide high throughput, low latency, and high availability for messaging and event streaming. It was officially introduced in RabbitMQ version 3.9, released in July 2021. RabbitMQ Streams is designed to handle large volumes of data efficiently, providing stream semantics similar to those found in other stream processing platforms like Apache Kafka. Key Features: - High Throughput and Low Latency. - Stream Semantics: Unlike traditional RabbitMQ queues, which store messages and are consumed and removed, RabbitMQ Streams retain messages for a specified period or until they reach a specified size. Consumers can read messages at any point within the stream, allowing for replayability and time-based processing. - Efficient Storage: Streams use efficient disk storage techniques to handle large volumes of data. They store messages in segments and use write-ahead logging to ensure data durability and consistency. - Consumer Offsets: Streams track consumer offsets, enabling consumers to resume processing from where they left off. This is similar to how Kafka handles consumer offsets, allowing for robust and fault-tolerant consumption. - Advanced Routing and Filtering: Streams support advanced routing and filtering capabilities, allowing for selective consumption of messages based on specific criteria. - Horizontal Scalability: Multiple brokers can be used to distribute the load, and stream segments can be replicated for high availability. - Backwards Compatibility: Designed to be compatible with existing RabbitMQ infrastructure, allowing users to integrate streams into their current RabbitMQ deployments. Use Cases: - Event Sourcing: Streams are well-suited for event sourcing architectures, where the complete history of changes to an application's state needs to be stored and replayed. - Real-time Analytics: Applications that require real-time data analytics can benefit from the high throughput and low latency characteristics of RabbitMQ Streams. - Log Aggregation: Collecting and processing logs from various sources in a centralized manner can be efficiently handled using RabbitMQ Streams. - Data Pipelines: Building data pipelines that require reliable, scalable, and fault-tolerant message delivery. 📣 WhatsApp Channel: https://lnkd.in/gxQfpuGD

3

Convert your app to any language | Satellite Assembly in .net

3

🚀 𝗧𝗵𝗲 𝗙𝘂𝘁𝘂𝗿𝗲 𝗼𝗳 .𝗡𝗘𝗧: 𝗞𝗲𝘆 𝗛𝗶𝗴𝗵𝗹𝗶𝗴𝗵𝘁𝘀 𝗳𝗿𝗼𝗺 .𝗡𝗘𝗧 𝗖𝗼𝗻𝗳 𝟮𝟬𝟮𝟰 𝗮𝗻𝗱 𝗪𝗵𝗮𝘁'𝘀 𝗡𝗲𝘄 𝗶𝗻 .𝗡𝗘𝗧 𝟵! 🚀 Last week, at the much-anticipated .𝗡𝗘𝗧 𝗖𝗼𝗻𝗳 𝟮𝟬𝟮𝟰, Microsoft unveiled some of the most exciting updates to the .NET ecosystem. From performance improvements to cutting-edge AI integrations, here’s a roundup of the top features that .NET 9 brings: 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 𝗕𝗼𝗼𝘀𝘁𝘀: .NET 9 introduces groundbreaking optimizations, including a 𝗦𝗲𝗿𝘃𝗲𝗿 𝗚𝗮𝗿𝗯𝗮𝗴𝗲 𝗖𝗼𝗹𝗹𝗲𝗰𝘁𝗼𝗿 that reduces memory usage by up to 𝟵𝟯% in specific scenarios. This enhancement makes it easier to scale applications, handle large datasets, and maximize performance across multi-core systems​. 𝗔𝗜 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻 𝗠𝗮𝗱𝗲 𝗘𝗮𝘀𝘆: With 𝗠𝗶𝗰𝗿𝗼𝘀𝗼𝗳𝘁.𝗘𝘅𝘁𝗲𝗻𝘀𝗶𝗼𝗻𝘀.𝗔𝗜 and tighter integration with OpenAI, Azure, and Pinecone, .NET 9 streamlines the process of embedding AI into applications. This is a game-changer for developers looking to build intelligent apps and leverage modern AI models directly within the .NET ecosystem​. 𝗔𝗦𝗣.𝗡𝗘𝗧 𝗖𝗼𝗿𝗲 𝗮𝗻𝗱 𝗕𝗹𝗮𝘇𝗼𝗿 𝗘𝗻𝗵𝗮𝗻𝗰𝗲𝗺𝗲𝗻𝘁𝘀: 𝗛𝘆𝗯𝗿𝗶𝗱𝗖𝗮𝗰𝗵𝗲 brings more efficient caching solutions for .NET Core, while Blazor now offers enhanced performance for building interactive web apps. The new version also supports server-side rendering optimizations, making Blazor even faster and more scalable​. 𝗦𝗺𝗮𝗿𝘁𝗲𝗿 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁 𝘄𝗶𝘁𝗵 .𝗡𝗘𝗧 𝗠𝗔𝗨𝗜: .NET 9’s MAUI (Multi-platform App UI) received significant updates for building cross-platform apps. Now, developers can seamlessly create apps for Android, iOS, Windows, and macOS with greater performance and reduced resource consumption​. 𝗔𝗜-𝗗𝗿𝗶𝘃𝗲𝗻 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝗧𝗼𝗼𝗹𝘀: The latest tools like GitHub Copilot now offer even more robust suggestions for .NET developers, making it easier to write code, debug, and automate common tasks. This upgrade is designed to make your development workflow smoother and faster​. 🔧 𝗪𝗵𝘆 𝗧𝗵𝗶𝘀 𝗠𝗮𝘁𝘁𝗲𝗿𝘀: These innovations are not just incremental improvements, they’re setting the stage for the next generation of software development. Whether you're building scalable cloud-native apps, enhancing your AI capabilities, or optimizing your web applications, .NET 9 has something that can help you do it faster, smarter, and more efficiently. 🔎 𝗥𝗲𝗮𝗱𝘆 𝘁𝗼 𝗲𝘅𝗽𝗹𝗼𝗿𝗲 𝘁𝗵𝗲 𝗳𝘂𝘁𝘂𝗿𝗲 𝗼𝗳 .𝗡𝗘𝗧? Check out the full recap from .NET Conf 2024 (dotnetconf.net) to dive deeper into these features and how they can benefit your projects! 🚀 If you have other improvements that you think are interesting and I didn’t point out, please let me know. #DotNet9 #DotNetConf #AI #CSharp #Performance #Development #SoftwareEngineering #Blazor #MAUI #Cloud #OpenAI #Microsoft

51

50 תגובות

TGIF (Tech Gyan In Five) #176 -> Fabulous conversation between Pallavi Lokesh Shetty and Bob German on the topic of integrating APIs into M365 Copilot Experience. A must watch if you are building Copilot Experiences. #WeeklyTechCapsule #Conversations #GenerativeAI #Plugins #TGIF #MicrosoftInnovationHub #HubBengaluru

35