Diego Sánchez Mendoza

Are you ready to boost your Code Efficiency! 🚀 In our latest blog post, Azure Data expert, Ines Olmos Alonso, shares practical tips to improve code structure, readability, and efficiency. From moving from notebooks to well-organized scripts to advice on naming variables and functions, this article offers essential tips to help you write cleaner, more collaborative code. 📈 Enhance your productivity and that of your team with best coding practices. 👉 Read the article here: https://lnkd.in/e53gQfEz

21

Kubernetes 1.30 a.k.a. #Uwubernetes has some new features and improvements we’re particularly excited about. In this article, nOps Engineer Alonso Parasxidis Moreno breaks down the most important updates and what they mean for your team. Learn about the significant CLI and API upgrades, robust networking, and autoscaling enhancements that can help you manage large clusters and complex workloads more efficiently. Upgrade now to save — Amazon EKS clusters running on older versions of Kubernetes will be charged $0.60 per cluster per hour for extended support. https://lnkd.in/guH9fi5P

24

1 comentario

How to create secure SSO authentication for Azure Function Apps?   In this article, Natalia Trojanowska-Korepta will guide you through Azure Function App authentication setup for different client types.   Find the link to the article in comments 👇

22

3 comentarios

The slides of my session in #Drupal #DrupalIberia about Legacy code are already availables here https://lnkd.in/dYM7d2Rf Now, you can copy the memes and share without problems :P

10

1 comentario

Integrations and microservices in Agiblocks ⚙️ Developed from the ground up using .NET, C# and standard Microsoft systems, Agiblocks takes full advantage of web- and cloud-enabled technologies. Where others talk about the cloud, they imply that their systems are in the cloud and not on on-location servers. With Agiblocks, you can actually work from the cloud – 24/7, anywhere, on any device that has a browser. We’d like to talk about the myriad of integrations and microservices Agiboo offers so that you have everything you need in one place – from procurement, accounting, logistics and everything else ‘ERP’ to risk management, physical contract management, mark to market valuation and flexible reporting. ⬇️ #Agiblocks #CloudBased #Integrations #Microservices #ERP #RiskManagement #ContractManagement #Reporting

6

In betav1, Karpenter has adopted a more fine-grained approach to IAM permissions, aligning operations with security best practices and the principle of least privilege access. Learn more about these enhancements and what they mean for Karpenter users in this article by nOps engineer Alonso Parasxidis Moreno. https://lnkd.in/g6bdFq5g . #karpenter #aws #nops #eks

9

Microservices architecture involves breaking down a monolithic application into smaller services. This approach offers benefits, including: 👉 Minimizing the impact of failures. 👉 Using the best tools for each service. 👉 Deploying services independently for quicker iterations.

2

❗ TODAY ❗ 🎙 "Navigating and Optimizing Karpenter - Avoiding Common Pitfalls" by Ivan Yurochko #KCDBarcelona by DevBcn Join us for an interactive session including real-world examples, and resources you can start leveraging to optimize your #Karpenter implementations today! Kubernetes Community Days Spain Cloud Native Barcelona

22

1 comentario

🚀 Revolutionize your cloud infrastructure automation with the powerful combination of #Terraform and #GitLab! Learn how Infrastructure as Code (#IaC) can optimize resource management, reduce errors, and enhance scalability in our latest blog. Discover how these tools can transform your organization's operational efficiency in the #cloud ➡️ https://hubs.li/Q02yw2QP0 #DevOps #CloudComputing #AWS

3

Microsoft Azure 's Ricardo Villarreal discusses why network API standardization is important, including use of CAMARA open APIs: ✅ "We only consume, in our platform, CAMARA-compliant APIs. We believe that an API is going to be more powerful if its the same API...if an API is only available through one operator, its loses power." ✅ The industry needs more developer buy-in so we can introduce even more network capabilities (beyond anti-fraud), and CAMARA and Open Gateway make this easier Hear the rest of the discussion on "Scaling Open Gateway for Developer Success" from this year's GSMA Open Gateway's Open OpenDevCon, including insight from Infobip's Mijo Soldin: https://lnkd.in/eydx4heK

32

In this MinIO architecture overview, Will Dinyes takes us through how an object is sent to and retrieved from a MinIO #objectstore using a deterministic function and a PUT and GET request.

29

2 comentarios

💡💊 A Software Engineering Pill from Marcelo 💻✨ 🚀 DDD (Domain-Driven Design), Hexagonal, and Clean architectures are approaches to structuring software systems in a way that promotes maintainability, scalability, and code comprehension. Although they have some similarities, each has its specific objectives and nuances. Here are the differences, objectives, and application scenarios for each: 🏛️ Domain-Driven Design (DDD) 🎯 Objective: 🏗️ Focus on the complexity of the business domain, using a common language to describe the system that is shared by developers and domain experts. 🛠️ Characteristics: 🧱 Entities and Aggregates: Structures that have a distinct identity and logical consistency. 📦 Repositories: Abstractions for accessing persistent data. 🛠️ Domain Services: Functionalities that don't naturally belong to any entity or aggregate. 🏭 Factories: Complex object creation. 📜 Value Objects: Objects that are described solely by their attributes. ⏰ When to Use: 🔍 Projects with significant business complexity. 🤝 Systems where collaboration between domain experts and developers is crucial. 📚 Domains where the language and business rules are complex and mutable. 🔄 Hexagonal Architecture (Ports and Adapters) 🎯 Objective: 🔄 Isolate the core of the application from its external dependencies to facilitate changes and testing. 🛠️ Characteristics: 🔑 Core: Contains business logic independent of external technologies. 🚪 Ports: Interfaces that define how the core interacts with the external world. ⚙️ Adapters: Implementations of ports that connect to specific technologies (database, user interfaces, APIs). ⏰ When to Use: 🧩 Projects that need high flexibility to swap external dependencies. 🧪 Applications where testability is a significant concern. 🏢 Systems requiring a clear separation between business logic and infrastructure details. ✨ Clean Architecture 🎯 Objective: ✨ Provide a code structure that is independent of frameworks, databases, and user interfaces. 🛠️ Characteristics: 🎯 Concentric Layers: Business core at the center, with each outer layer depending on the more inner layers. 🧬 Entities: Business models that are independent of any other layer. 🔄 Use Cases: Specific applications that orchestrate the entities. 🌉 Interfaces: Abstractions that define how the outer layers interact with the core. ⏰ When to Use: 🏛️ Projects that require high independence from frameworks and specific technologies. 🛠️ Systems needing a highly modular and decoupled architecture. ♻️ Projects where the reusability of business components is a priority. 🎯 Each of these architectures has its advantages and is best suited for different types of projects and needs. The choice between them should be based on the specific requirements of the project, the complexity of the business domain, and the needs for maintenance and scalability. #DomainDrivenDesign #HexagonalArchitecture #CleanArchitecture #SoftwareArchitecture #SoftwareEngineering

2

🌟Online Speaker Series Announcement! 🌟 Introducing Alberto Acerbis presenting a session on "Tackling Chaos, Resilience and Metrics in the heart of your .NET Applications". With the spread of microservices and distributed cloud architectures, the web has become increasingly complex. We all depend on these systems more than ever, yet bugs have become much more difficult to predict. Chaos Engineering is a disciplined approach to identifying bugs before they become real service disruptions. But how do you test the response of a system under stress to identify, and prevent, weaknesses? Recently .NET has made available, directly in the framework, everything necessary to implement Chaos experiments in code. Let us see how. Find out more more - https://lnkd.in/eC_ZRMnD #CommunitySpeaker #NetApplications #ScottishSummit #Resilience #Metrics

20