Guillaume Chervet

🚀 Server-Side Rendering (SSR) in ASP.NET Core Angular (2024): Boost Your Web App Performance! 🚀 In this article, Pieterjan De Clippel will guide you through the latest techniques to implement SSR in your ASP.NET Core Angular projects. 🎯 you'll explore: ⚡ The benefits of SSR for enhanced performance and user experience. 🔍 How SSR can boost your search engine visibility. 🛠️ A step-by-step guide to set up SSR in your projects. Whether you're an experienced Angular developer or just starting out, this article will provide the knowledge you need to harness the power of SSR in your ASP.NET Core applications. #Angular #ASPNETCore #SSR #WebDevelopment #Performance

1

🎉 Another 𝗦𝘁𝗮𝗯𝗹𝗲 Release for 𝗖𝗼𝗺𝗽𝗼𝘀𝗲 𝗠𝘂𝗹𝘁𝗶𝗽𝗹𝗮𝘁𝗳𝗼𝗿𝗺! Exciting news for developers: Compose Multiplatform 𝟏.𝟔.𝟏𝟏 is now released! This update includes several fixes for multiplatform as well as platform-specific improvements. 🚀 https://lnkd.in/g9FJ-gui #google #jetbrains #kotlin #compose #kmp #composeMultiplatform #multiplatform

27

In this talk Sébastien Stormacq shows us how we can easily deploy an existing server-side Swift app to AWS Lambda with no code changes! Then you'll see how to deploy a native function to Lambda and finally how to use the SwiftPM plugin

3

GoFr vs Chi: A Comparison of Golang Frameworks #golang #frameworks #gofr #chi #comparsion https://lnkd.in/eyUWbCVw

7

Inspired by the demo of Matthieu Riegler, I found a use case of Angular v18 content projection fallback. The card displays the default content for the free tier. They display custom header, content, and default footer for start-up and company tiers. For the enterprise tier, it displays a custom header, content, and footer

72

1 commentaire

don't jump into writing a unit/integration test or doing TDD or ... first, evaluate the context: * writing a test is an investment, so, will it pay off ? * can I get same benefit in other ways ? If the project is of short lifetime, you will not get "maintenance benefits" from your tests (e.g. refactoring). If you are in huge hurry, writing tests will slow you down. In above cases you better not write tests. Writing fast, throw away code is sometimes best you can do. For the 2nd point, sometimes you can get better code using compiler features that writing tests. E.g. organize your code so that non-legal states are impossible to represent. Compiler is your friend (sorry JS and Python folks). Main thing: be pragmatic, not dogmatic Context is still the King

2

1 commentaire

Performance-wise, the new protocol has reduced dataplane latency by 11% on average, and by 17.4% at the P90 mark. In addition to making SQS itself more performant, this change benefits services that build on SQS as well. For example, messages sent through Amazon Simple Notification Service (Amazon SNS) now spend 10% less time “inside” before being delivered. Finally, due to the protocol change, the existing fleet of SQS hosts (a mix of X86 and Graviton-powered instances) can now handle 17.8% more requests than before. #AWS #AmazonWebServices #AWSBlogs #Cloud #CloudComputing #Serverless #SQS

2

1 commentaire

Unit testing is safety belt for any changes in your code. You can do manual or using the codes. If you want to safe the energy later on, start by implement Unit Test codes in your Unit Test 😎

6

1 commentaire

CSRF token validation is now simpler in #Symfony 7.1 with the #[IsCsrfTokenValid] attribute. The attribute eliminates the need for explicit if checks, making your code cleaner and more concise. 👍

23

Three Laws of TDD First Law : You may not write production code until you have written a failing unit test. Second Law : You may not write more of a unit test than is sufficient to fail, and not compiling is failing. Third Law : You may not write more production code than is sufficient to pass the currently failing test. These three laws lock you into a cycle that is perhaps thirty seconds long. The tests and the production code are written together, with the tests just a few seconds ahead of the production code. #cleancode #cleanatchitecture #unclebob #tdd #kogget #unittesting #softwaredevelopment #csharp #java #dotnet

4

Kora: A cloud-native redesign of the Apache Kafka engine #kora #apachekafka #redesign #cloudnative #eventstreaming #multicloud https://lnkd.in/eu2v5FVS

9

𝐃𝐨𝐧'𝐭 𝐒𝐚𝐛𝐨𝐭𝐚𝐠𝐞 𝐘𝐨𝐮𝐫 𝐂𝐨𝐦𝐩𝐚𝐧𝐲'𝐬 𝐆𝐫𝐨𝐰𝐭𝐡: 𝐈𝐧𝐯𝐞𝐬𝐭 𝐢𝐧 𝐓𝐨𝐩 𝐓𝐚𝐥𝐞𝐧𝐭s! As a cloud technology leader, I'm astonished by the number of companies seeking full-stack developers with solutions architecture skills, but only willing to pay front-end developer salaries. This approach is not only short-sighted, but it's also a recipe for self-sabotage. 𝑻𝒉𝒆 𝑪𝒐𝒏𝒔𝒆𝒒𝒖𝒆𝒏𝒄𝒆𝒔: - Missing out on top talent - Jeopardizing company growth and profitability - Failing to innovate and stay competitive 𝑻𝒉𝒆 𝑺𝒐𝒍𝒖𝒕𝒊𝒐𝒏: 1. Conduct regular market research: Stay up-to-date on industry standards and trends to ensure you're offering competitive salaries and benefits. 2. Prioritize employee development: Invest in your employees' growth and well-being by providing training, mentorship, and opportunities for advancement. 3. Foster a culture of innovation: Encourage experimentation, creativity, and innovation within your organization to attract and retain top talent. 4. Be transparent about compensation and benefits: Clearly communicate your compensation and benefits packages to attract the right candidates and reduce turnover. 𝑹𝒆𝒄𝒐𝒎𝒎𝒆𝒏𝒅𝒂𝒕𝒊𝒐𝒏𝒔 𝒇𝒐𝒓 𝑱𝒐𝒃 𝑺𝒆𝒆𝒌𝒆𝒓𝒔: 1. Know your worth: Research the market to determine your value and don't be afraid to negotiate your salary. 2. Look for companies that invest in their employees: Prioritize companies that offer competitive salaries, benefits, and opportunities for growth and development. 3. Develop in-demand skills: Focus on acquiring skills that are in high demand, such as full-stack development, solutions architecture, and emerging technologies like AI, ML, and cloud computing. 𝑹𝒆𝒄𝒐𝒎𝒎𝒆𝒏𝒅𝒂𝒕𝒊𝒐𝒏𝒔 𝒇𝒐𝒓 𝑪𝒐𝒎𝒑𝒂𝒏𝒊𝒆𝒔 𝑳𝒐𝒐𝒌𝒊𝒏𝒈 𝒕𝒐 𝑺𝒄𝒂𝒍𝒆: 1. Diversify your hiring channels: Look beyond traditional hiring channels, such as job boards and recruiters, to attract a more diverse pool of candidates. 2. Emphasize company culture and values: Highlight your company's mission, values, and culture to attract candidates who share your vision and are more likely to stay long-term. 3. Offer flexible work arrangements: Provide flexible work arrangements, such as remote work options, to attract and retain top talent in a competitive market. 𝐓𝐚𝐤𝐞 𝐀𝐜𝐭𝐢𝐨𝐧: Don't let your company fall behind in the war for talent. Invest in your employees, prioritize innovation, and attract the best candidates to drive your business forward. Share your thoughts and experiences in the comments below! #talentacquisition #companygrowth #innovation #techindustry #leadership

2

1 commentaire

Exciting Update in ASP.NET Core Blazor WebAssembly! 🚀 📖 ASP.NET Core Blazor WebAssembly Runtime .NET and Application Bundle Caching Discover how to optimize your Blazor WebAssembly applications with enhanced caching and integrity checks! Highlights: When a Blazor WebAssembly application loads, it downloads startup resources from the server, including JavaScript code, .NET runtime and assemblies, and locale-specific data. The blazor.boot.json file, which contains a manifest of application files, ensures that only consistent, hashed files are cached using the browser’s cache API. Integrity checks are performed using SHA-256 hashes to verify the downloaded files, preventing the application from loading inconsistent or invalid files. The Blazor algorithm guarantees that users never cache inconsistent files, ensuring smooth and secure application performance. Benefits: Prevent Inconsistent File Loads: Ensures that no inconsistent file sets are loaded, avoiding application malfunctions. Avoid Caching Invalid Responses: Makes sure users’ browsers do not cache invalid or inconsistent responses, even after manual page refreshes. Efficient Caching: Allows caching of responses without frequent server-side checks unless SHA-256 hashes change, speeding up subsequent page loads. Common Issues and Solutions: Server Response Errors: 404 or 500 errors can lead to integrity check failures. Diagnose server-side issues by checking the HTTP status codes in your browser’s developer tools. File Modifications: Ensure build artifacts are not manually modified, and be cautious of deployment processes that alter files, such as line ending conversions by Git. Improper Routing: Misconfigured routing can return incorrect data types. Verify that .wasm and .dll requests return appropriate binary files. For more detailed diagnostics, refer to the provided PowerShell scripts and additional resources to help you troubleshoot integrity issues effectively. Conclusion: This update to ASP.NET Core Blazor WebAssembly enhances application reliability and performance by integrating robust caching and integrity checking mechanisms. Keep your applications running smoothly and securely with these new tools and practices! Read the full article to learn more and take your Blazor WebAssembly applications to the next level! 💻🚀 https://lnkd.in/eZ6q6tNK #Blazor #ASPNetCore #WebAssembly #WebDevelopment #Caching #IntegrityChecks #Azure #AWS #CloudComputing #DotNet

7

PHP architecture tool ( https://lnkd.in/eY4CbnYM ) Ensuring proper separation of concerns within a project is vital for maintaining clean and manageable code. But how can one effectively verify this architecture during development? Enter PHP Arketect, a powerful tool designed to facilitate the tracking of dependencies between layers. At its core, PHP Arketect offers a flexible solution for enforcing layer-based architecture, with the ability to define and monitor dependencies between different layers. For me, its utility is most evident in the enforcement of three fundamental rules: Domain, Application, and Infrastructure layers. Initially, I encountered a challenge with the Domain layer, particularly when it came to dependencies on core classes like DateTimeImmutable. While the rule class provided by PHP Arketect, NotHaveDependencyOutsideNamespace, was a step in the right direction, it didn't seamlessly handle these dependencies. To address this issue, I proposed a solution and submitted a merge request, which was subsequently accepted. This enhancement now allows for smoother handling of dependencies within the Domain layer, including those on core classes like DateTimeImmutable. By leveraging PHP Arketect and contributing to its improvement, developers can better enforce and validate layered architecture within their PHP projects, ultimately leading to cleaner, more maintainable codebases. https://lnkd.in/eH542gek

1

How I implement #hexagonal #architecture in #symfony ? Here is a simplistic example for a create user use-case where I show how the ports and adapters allow me to switch implementations and unit test my feature without any infrastructure dependency. Symfony with its flexible configuration makes it very easy to wire each adapter to a port according to you intention and environnement ( prod, tests, staging...)

24

6 commentaires

[𝟏/𝟓] 𝐔𝐧𝐝𝐞𝐫𝐬𝐭𝐚𝐧𝐝𝐢𝐧𝐠 𝐒𝐨𝐟𝐭𝐰𝐚𝐫𝐞 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 If you ask 100 developers, “𝑾𝒉𝒂𝒕 𝒊𝒔 𝒔𝒐𝒇𝒕𝒘𝒂𝒓𝒆 𝒂𝒓𝒄𝒉𝒊𝒕𝒆𝒄𝒕𝒖𝒓𝒆?” you’ll likely get 100 different answers. Why? Because architecture means something different for every project, depending on factors like: - Project size and domain, - Technical and non-technical requirements, and - Various constraints. In essence, architecture can be: - The big picture - A system overview - A plan to implement solutions - An abstract view of a system - The vision and strategy for software projects …and much more. But even though “architecture” is hard to define, it helps to think of it in two ways: as a 𝒏𝒐𝒖𝒏 and as a 𝒗𝒆𝒓𝒃. - 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 𝐚𝐬 𝐚 𝐧𝐨𝐮𝐧: It’s the structure of a system. This includes software elements, their externally visible properties, and the relationships between them. - 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 𝐚𝐬 𝐚 𝐯𝐞𝐫𝐛: It’s about translating functional requirements, non-functional requirements, and constraints into a technical solution. Even though I’m a .NET developer, not an architect, I’ve spent a lot of time learning about architecture. You might wonder, “𝑾𝒉𝒚 𝒔𝒉𝒐𝒖𝒍𝒅 𝑰 𝒍𝒆𝒂𝒓𝒏 𝒂𝒃𝒐𝒖𝒕 𝒔𝒐𝒇𝒕𝒘𝒂𝒓𝒆 𝒂𝒓𝒄𝒉𝒊𝒕𝒆𝒄𝒕𝒖𝒓𝒆 𝒂𝒔 𝒂 𝒅𝒆𝒗𝒆𝒍𝒐𝒑𝒆𝒓?” Well, if you’re like me, you might find yourself needing to think about the bigger picture for two reasons: 1. As a senior developer (or the person making these decisions in your project) 2. If your team doesn’t have a dedicated architect. 𝐼𝑛 𝑡ℎ𝑖𝑠 𝑝𝑜𝑠𝑡 𝑠𝑒𝑟𝑖𝑒𝑠, 𝐼’𝑙𝑙 𝑔𝑢𝑖𝑑𝑒 𝑦𝑜𝑢 𝑡ℎ𝑟𝑜𝑢𝑔ℎ 𝑘𝑒𝑦 𝑠𝑜𝑓𝑡𝑤𝑎𝑟𝑒 𝑎𝑟𝑐ℎ𝑖𝑡𝑒𝑐𝑡𝑢𝑟𝑒 𝑐𝑜𝑛𝑐𝑒𝑝𝑡𝑠. Over the next four posts, we’ll cover: 1. Deciding which non-functional requirements (like scalability and performance) are essential based on business needs 2. Understanding the most popular architectural styles (clean architecture, vertical slice, microservices) and their differences 3. How to document tech decisions for your team simply, quickly, and effectively 4. A list of 16 of my favorite architecture resources for .NET developers (books, GitHub repos, fully developed apps, and more!) Each post includes visuals and practical examples to make these concepts clear and applicable. Stay tuned to dive deeper into software architecture! #SoftwareArchitecture #DotNetDeveloper #BackendDevelopment #SystemDesign #ArchitectureNounVsVerb #TechStrategy #Scalability #CleanArchitecture #Microservices #TechDocumentation #SoftwareEngineering #LearningJourney #CareerGrowth #DeveloperCommunity #DotNetCommunity

6