Iniciar sesión para ver el perfil completo de John 👨🏻💻
o
¿Ya eres miembro de LinkedIn? Inicia sesión
Al hacer clic en «Continuar» para unirte o iniciar sesión, aceptas las Condiciones de uso, la Política de privacidad y la Política de cookies de LinkedIn.
Iniciar sesión para ver el perfil completo de John 👨🏻💻
o
¿Ya eres miembro de LinkedIn? Inicia sesión
Al hacer clic en «Continuar» para unirte o iniciar sesión, aceptas las Condiciones de uso, la Política de privacidad y la Política de cookies de LinkedIn.
Medellín, Antioquia, Colombia
Iniciar sesión para ver el perfil completo de John 👨🏻💻
John 👨🏻💻 puede presentarte a más de 10 personas en NodeSource
Unirse con el email
o
¿Ya eres miembro de LinkedIn? Inicia sesión
Al hacer clic en «Continuar» para unirte o iniciar sesión, aceptas las Condiciones de uso, la Política de privacidad y la Política de cookies de LinkedIn.
1 mil seguidores
Más de 500 contactos
Iniciar sesión para ver el perfil completo de John 👨🏻💻
o
¿Ya eres miembro de LinkedIn? Inicia sesión
Al hacer clic en «Continuar» para unirte o iniciar sesión, aceptas las Condiciones de uso, la Política de privacidad y la Política de cookies de LinkedIn.
Ver tus contactos en común con John 👨🏻💻
John 👨🏻💻 puede presentarte a más de 10 personas en NodeSource
Unirse con el email
o
¿Ya eres miembro de LinkedIn? Inicia sesión
Al hacer clic en «Continuar» para unirte o iniciar sesión, aceptas las Condiciones de uso, la Política de privacidad y la Política de cookies de LinkedIn.
Ver tus contactos en común con John 👨🏻💻
o
¿Ya eres miembro de LinkedIn? Inicia sesión
Al hacer clic en «Continuar» para unirte o iniciar sesión, aceptas las Condiciones de uso, la Política de privacidad y la Política de cookies de LinkedIn.
Iniciar sesión para ver el perfil completo de John 👨🏻💻
o
¿Ya eres miembro de LinkedIn? Inicia sesión
Al hacer clic en «Continuar» para unirte o iniciar sesión, aceptas las Condiciones de uso, la Política de privacidad y la Política de cookies de LinkedIn.
Acerca de
¡Hola de nuevo!
Al hacer clic en «Continuar» para unirte o iniciar sesión, aceptas las Condiciones de uso, la Política de privacidad y la Política de cookies de LinkedIn.
¿Estás empezando a usar LinkedIn? Únete ahora
Actividad
1 mil seguidores
-
John 👨🏻💻 Agudelo ha compartido estoJohn 👨🏻💻 Agudelo ha compartido estoGetting a backend job in 2026 won’t be about who writes the most code. It will be about who understands how systems behave in production. Today, we’re seeing a shift: • From building features → to operating reliable systems • From debugging code → to analyzing runtime behavior • From intuition → to data-driven decisions If you're preparing for backend roles, focus on this: Observability is no longer optional. If you can’t see what your system is doing, you can’t fix it. But going further — dashboards are not enough. The real difference comes from understanding what’s happening inside the runtime: • Event loop behavior • CPU and memory usage • Garbage collection • Performance under real load This is where modern backend engineering is heading. And now, AI is accelerating that shift — helping teams move from raw telemetry to actual insights and optimization. The engineers who stand out won’t just build systems. They’ll understand, measure, and improve them in production. If you're aiming for backend roles, start there. #Nodejs #Backend #SoftwareEngineering #Observability #AI #Performance
-
John 👨🏻💻 Agudelo ha compartido estoJohn 👨🏻💻 Agudelo ha compartido estoNode.js scales beautifully 🚀 Until one day… latency starts stretching 🫠 No crashes. No errors. Just… slower. 20ms ➝ 120ms. p99 drifts 📈 Throughput softens. Infra looks healthy ✅ Database is fine ✅ So what changed? 🤔 The answer is usually inside the runtime. The Event Loop is precise. Deterministic. Efficient. ⚙️ But it runs on a single main thread. And if that thread is: • Busy with CPU-heavy logic 🔥 • Handling too many callbacks at once 📦 • Waiting behind thread pool work 🧵 • Spinning in microtasks 🔁 Forward progress slows down — quietly. Understanding how V8 + libuv + the thread pool + the kernel coordinate work is the difference between: “It feels slow” 😕 and “We know exactly why.” 🎯 We broke it down layer by layer: 👉🏼 https://lnkd.in/eZV3whFP If you run Node.js in production, knowing the framework isn’t enough. Knowing the runtime is the real edge. 🧠✨ #NodeJS #Backend #PerformanceInside the Node.js Event Loop: What Actually Blocks Your Production SystemInside the Node.js Event Loop: What Actually Blocks Your Production SystemNodeSource
-
John 👨🏻💻 Agudelo ha compartido estoAwesome!!John 👨🏻💻 Agudelo ha compartido estoToday, we’re proud to announce that NodeSource has joined the OpenJS Foundation’s LTS Upgrade & Modernization program 🚀 The reality: A significant portion of enterprises are still running legacy or End-of-Life Node.js versions — exposing their systems to security vulnerabilities, compliance risk, and performance limitations. This collaboration introduces a structured, AI-powered modernization path designed specifically for enterprise environments: • Secure local static analysis • AI-assisted risk scoring • Native addon & dependency conflict detection • Automated refactoring guidance • Phased migration roadmap Scan. Analyze. Execute. As the inaugural partner of the program, NodeSource will also share 15% of program revenue with the Foundation to support continued Node.js ecosystem development. Modernizing Node.js shouldn’t be a high-risk migration. It should be predictable, measurable, and secure. Read the full announcement: 🔗 https://lnkd.in/e3xxRrWt Explore the Upgrade Program: 🔗 https://lnkd.in/efJTkEuK #NodeJS #OpenJSFoundation #UpgradeProgram #EnterpriseSoftware #DevOps #RuntimeSecurity #JavaScript
-
John 👨🏻💻 Agudelo ha compartido estoJohn 👨🏻💻 Agudelo ha compartido esto¡De Las Vegas a Medellín! ✈️🏙️ Fue un verdadero gusto conectar nuevamente con la comunidad AWS User Group - Medellín y revivir lo mejor del AWS re:Invent 2025. Traer la esencia del evento de nube más importante del mundo directamente desde Las Vegas hasta nuestra ciudad es una experiencia increíble. ☁️✨ ¡Gracias por compartir las últimas innovaciones y fortalecer el ecosistema tech local! 💻 #AWSreInvent #AWSreInventRecap #AWSUserGroupMedellín #AWSCommunity #CloudComputing #AWS
-
John 👨🏻💻 Agudelo ha compartido estoJohn 👨🏻💻 Agudelo ha compartido esto🔐 Node.js January 2026 Security Release — What Changed and Why It Matters The latest Node.js security release is now available, bringing important fixes across memory safety, permissions, HTTP/2, and TLS. No new features — just critical updates that improve stability, resilience, and security in production environments. If you run Node.js in production, this release is worth your attention. 👉 Read the full breakdown and upgrade guidance here: https://nsrc.io/4b0cnY8 #NodeJS #Security #Production #CVE #Backend #PlatformEngineering
-
John 👨🏻💻 Agudelo ha compartido estoJohn 👨🏻💻 Agudelo ha compartido estoWe'd love your input, Node.js community 💚 - Where do you learn Node.js today? - What kind of content do you actually find useful? - What do you feel is missing right now? We put together a very short form to better understand how the community learns and stays up to date 👇🏼 Thanks for helping shape the future of the Node.js community 🫶🏻 https://lnkd.in/ewBSHBPA
-
John 👨🏻💻 Agudelo ha compartido estoJohn 👨🏻💻 Agudelo ha compartido estoHay un repositorio que se está haciendo famoso porque supuestamente te permite tener Cursor Pro sin pagar. ¡No lo uses! Este tipo de “trucos” no solo violan los términos de servicio, también ponen en riesgo tu cuenta, tu entorno de desarrollo y tu ordenador. Si quieres usar Cursor Pro, págalo. Si no quieres pagarlo, no lo uses. Lo que nunca debes hacer es ejecutar binarios de origen dudoso que prometen “activar” productos. No merece la pena poner en juego tu equipo por ahorrarte 20$.
-
John 👨🏻💻 Agudelo ha compartido estoJohn 👨🏻💻 Agudelo ha compartido esto🚀 Big news! NodeSource has joined the @openjsf Ecosystem Sustainability Program (ESP) to help keep users of older, unsupported Node.js versions secure as they plan their upgrades. Through the ESP, we’re contributing our Node.js expertise to sustain the health and reliability of the JavaScript ecosystem. Learn more about how we’re helping secure legacy Node.js environments while supporting the community’s long-term growth.
-
John 👨🏻💻 Agudelo ha compartido estoIncredible!John 👨🏻💻 Agudelo ha compartido estoCheck out Velociy - a zero-dependency Node.js framework: 🚀 Performance Benchmarks (Node.js v20.x LTS, rewrk, 128 connections): - 91,330 req/s (Velocy) vs 16,438 req/s (Express) - 1.40ms avg latency vs 7.78ms - 16.11 MB/s transfer vs 3.76 MB/s ✨ Highlights - Multiple router implementations (FastRouter, SimpleRouter, Router) - Express-style middleware + built-in essentials (JSON, CORS, cookies, sessions, static files, compression, rate limiting) - WebSockets built-in (rooms, broadcasting, RFC 6455 support) - Familiar request/response APIs with performance optimizations - Zero dependencies: built entirely on Node core modules Velocy also doubles as the foundation of Learn Node.js the Hard Way, a project that walks through Node.js internals by building production-ready components. The project is MIT licensed and open to contributions. 👉 https://nsrc.io/3HuweT3
-
John 👨🏻💻 Agudelo ha recomendado estoJohn 👨🏻💻 Agudelo ha recomendado esto💡 Tip: “Zero overhead” is not a feature. It’s the baseline. If your observability tool adds overhead… you’re not measuring your system — you’re influencing it. Before adopting any tooling, ask: • Does it impact CPU or latency? • Does it rely on sampling instead of full visibility? • Does it force context switching to understand issues? If yes — your data might not reflect reality. Good observability doesn’t interfere. It reveals. #ZeroOverhead #NoContextSwitch #NodeJS #Observability #WebSummitVancouver #TheMissingLink
-
John 👨🏻💻 Agudelo ha reaccionado a estoJohn 👨🏻💻 Agudelo ha reaccionado a estoNode.js Collaboration Summit just wrapped up in London (April 14–15) 🇬🇧 Our team was there — Rafael Gonzaga, Ulises Gascón, Santiago Gimeno, Adrian Estrada — contributing to the conversations shaping what’s next for Node.js, from production challenges to ecosystem-level decisions. One topic that sparked debate 🔥: → Moving security reports to a more public workflow The idea is simple (and controversial): If AI can rediscover many issues instantly… are they really “private”? This raises real questions: • Are we creating a false sense of security? • What actually deserves an embargo today? • How do we fix faster without adding noise? This is the kind of discussion that defines the future of open source. Curious — what do you think should be debated more openly in Node.js? If you want to explore more: https://lnkd.in/eKtP_54H https://lnkd.in/ePig3hGZ #Nodejs #OpenSource #JavaScript #Backend
-
John 👨🏻💻 Agudelo ha reaccionado a estoJohn 👨🏻💻 Agudelo ha reaccionado a estoGetting a backend job in 2026 won’t be about who writes the most code. It will be about who understands how systems behave in production. Today, we’re seeing a shift: • From building features → to operating reliable systems • From debugging code → to analyzing runtime behavior • From intuition → to data-driven decisions If you're preparing for backend roles, focus on this: Observability is no longer optional. If you can’t see what your system is doing, you can’t fix it. But going further — dashboards are not enough. The real difference comes from understanding what’s happening inside the runtime: • Event loop behavior • CPU and memory usage • Garbage collection • Performance under real load This is where modern backend engineering is heading. And now, AI is accelerating that shift — helping teams move from raw telemetry to actual insights and optimization. The engineers who stand out won’t just build systems. They’ll understand, measure, and improve them in production. If you're aiming for backend roles, start there. #Nodejs #Backend #SoftwareEngineering #Observability #AI #Performance
-
John 👨🏻💻 Agudelo ha recomendado estoJohn 👨🏻💻 Agudelo ha recomendado estoAre you also learning through every code review? 💻 Just checked my GitHub activity over the past year, it’s honestly such a nice feeling to see that effort in the data. Those little squares actually mean something ☺️ And to be honest, the biggest growth didn’t come just from committing code. It came from working with an amazing team at Runa. Reviewing my teammates’ code has taught me so much - different approaches, better patterns, small details I wouldn’t notice on my own. And at the same time, sharing my own thoughts and suggestions made me grow even more. Always happy to learn more 👩🏻💻 Check my GitHub profile if you’re curious and let's follow there each other: 🔗 https://lnkd.in/dnqCs3yc #github #commits #team
-
John 👨🏻💻 Agudelo ha recomendado estoJohn 👨🏻💻 Agudelo ha recomendado estoExcited to share a new episode of Beyond Node.js ✨🎉 This time, we sit down with Santiago Gimeno — contributor to Node.js & libuv and Senior Software Architect at NodeSource — to talk about what actually matters in production. We cover: • The worst things seen in real Node.js applications • Common misconceptions about Node.js in production • Performance, debugging & real-world failures • What teams should really focus on If you're working with Node.js in production, this conversation is for you. Watch the full episode in the comments 👇🏼 #Nodejs #JavaScript #Backend #SoftwareEngineering #OpenSource
-
John 👨🏻💻 Agudelo ha reaccionado a estoJohn 👨🏻💻 Agudelo ha reaccionado a estoToday is one of the happiest and most important days of my career. Today, I'm officially starting my dream job as Marketing Manager at The Linux Foundation, and I still can't believe it! If you don't know the LF yet, let me blow your mind a little: over 1,300 open source projects, 855,000 developers, and 89 million lines of code added every single week. Kubernetes - one of its flagship projects - is now the de facto "operating system" for AI, with 82% production adoption. And its Cloud Native Computing Foundation hosts more than 230 projects with over 300,000 contributors worldwide, making it one of the largest open source organizations on the planet. Across AI, cloud, security, networking, energy, and digital public goods, the Linux Foundation is expanding the shared infrastructure the world now depends on 🌎, and it's literally everywhere. I'm incredibly proud to be part of the team helping tell these stories and support the communities building the future of open technology 🐧🚀 I'm grateful, I'm ready, and I'm just getting started. #LinuxFoundation #OpenSource #NewJob #Marketing #NewBeginnings
-
John 👨🏻💻 Agudelo ha recomendado estoJohn 👨🏻💻 Agudelo ha recomendado estoNode.js scales beautifully 🚀 Until one day… latency starts stretching 🫠 No crashes. No errors. Just… slower. 20ms ➝ 120ms. p99 drifts 📈 Throughput softens. Infra looks healthy ✅ Database is fine ✅ So what changed? 🤔 The answer is usually inside the runtime. The Event Loop is precise. Deterministic. Efficient. ⚙️ But it runs on a single main thread. And if that thread is: • Busy with CPU-heavy logic 🔥 • Handling too many callbacks at once 📦 • Waiting behind thread pool work 🧵 • Spinning in microtasks 🔁 Forward progress slows down — quietly. Understanding how V8 + libuv + the thread pool + the kernel coordinate work is the difference between: “It feels slow” 😕 and “We know exactly why.” 🎯 We broke it down layer by layer: 👉🏼 https://lnkd.in/eZV3whFP If you run Node.js in production, knowing the framework isn’t enough. Knowing the runtime is the real edge. 🧠✨ #NodeJS #Backend #PerformanceInside the Node.js Event Loop: What Actually Blocks Your Production SystemInside the Node.js Event Loop: What Actually Blocks Your Production SystemNodeSource
Experiencia y educación
-
NodeSource
****** ******** ********
-
****
****** ******** ********
-
***** ***** ***
******** ********
-
*********** *****
********* ********* ** ************** ** ********* * ******** ** *********** undefined
-
-
*********** ********** ****** ***** ********
********* *************** * *******
-
Mira la experiencia completa de John 👨🏻💻
Mira su cargo, antigüedad y más
¿Ya eres miembro de LinkedIn? Inicia sesión
Al hacer clic en «Continuar» para unirte o iniciar sesión, aceptas las Condiciones de uso, la Política de privacidad y la Política de cookies de LinkedIn.
Licencias y certificaciones
Proyectos
-
Warehouse Managment System
Ver proyectoEnterprise app to control and manage inventory and documents.
- Full Stack PEAN (Postgres, ExpressJS, Angulajs, NodeJS) developer lead -
Implementación ERP Viacargo S.A.S
-
Adaptación ADempiere ERP a sector de transporte de carga masiva en Colombia, parametrización módulos de terceros, activos, compras, manifiestos de carga, facturación, pagos y recaudos, nómina, mantenimiento, contabilidad
Otros creadores -
Idiomas
-
Inglés
Competencia básica profesional
-
Spanish
Competencia bilingüe o nativa
Recomendaciones recibidas
-
Usuario de LinkedIn
«John is a talented engineer and while working with him as his technical lead he demonstrated resilience and an extraordinary talent for solving complex problems. I hope to have the opportunity to work with him again and believe that any team that has John is destined for success.»
1 persona ha recomendado a John 👨🏻💻
Unirse para verloVer el perfil completo de John 👨🏻💻
-
Descubrir a quién conocéis en común
-
Conseguir una presentación
-
Contactar con John 👨🏻💻 directamente
Ver más publicaciones
-
BuilderPlatform
18 seguidores
🚀 Introducing BuilderPlatform BuilderPlatform is a marketplace focused on production-ready developer templates designed to help developers launch modern applications faster. Our templates are built with real-world architecture and modern technologies such as Angular, Spring Boot, and cloud-ready infrastructure. What you can build with BuilderPlatform templates: • SaaS platforms • E-commerce systems • Business web applications • Scalable backend architectures Each template includes clean architecture, full source code, and technical documentation to help developers move from idea to production faster. Explore the marketplace: https://lnkd.in/ekxXPC34 #softwaredevelopment #angular #springboot #saas #webdevelopment
-
Krononsoft
392 seguidores
Legacy Ruby on Rails apps don’t fail because of bad technology. They fail because business decisions around them get delayed for too long. We’ve seen this pattern repeatedly: • The product still makes money • Customers are active • The app technically “works” • But every change takes longer than it should • Releases feel risky • And growth starts exposing cracks no one planned for At that point, the real question isn’t “Is Rails outdated?” It’s: “Is our application still helping the business or quietly slowing it down?” That’s what this article is about. Not rewrites for the sake of rewrites. Not chasing trends. Not fear-driven modernization. Instead, we break down: – How to tell whether a Rails app is truly legacy (from a business perspective) – When modernization creates real ROI and when it doesn’t – Why incremental modernization beats full rewrites in most cases – What a low-risk modernization process actually looks like – Lessons from real companies that scaled Rails responsibly Modernization is not a technical project. It’s a capital allocation decision. If you’re a founder, CTO, or product lead sitting on a Rails product that still matters to your business, this framework will help you think more clearly before pressure forces a rushed decision. We’ve published the full guide here 👇 (link in comments)
9
5 comentarios -
Alset
1 mil seguidores
Building cross-platform applications often comes with a tradeoff: higher development costs, duplicated code, or poor performance. In this video, we break down how .NET MAUI enables teams to build applications for Android, iOS, Windows, and macOS from a single C# codebase—without sacrificing native performance. We cover: - Unified development with .NET and C# - Hot Reload for faster iteration and higher productivity - Direct access to native APIs (camera, GPS, storage, etc.) - Integration with Blazor to reuse web components - Modern architecture patterns like MVVM and MVU At Alset, we help companies design and build modern cross-platform applications using .NET MAUI, .NET, and Azure, reducing time-to-market and long-term maintenance costs while keeping a native user experience. If your organization is considering a cross-platform strategy or wants to modernize existing apps, we can help you evaluate and implement the right approach. 🌐 visit: https://byalset.com/ 🚀 Book a free consultation with our team: 👉 https://lnkd.in/ea8WYeDQ https://lnkd.in/edNQtfDS
5
-
Angularidades
519 seguidores
Check out the short summary of Angularidades episode #69 with our guest Mauricio Arce Torrez, exploring when and how to apply microfrontends in Angular projects. ✔️ Why Angular doesn't include native microfrontend support ✔️ When organizational complexity justifies this architecture ✔️ Tools for runtime composition in Angular ✔️ How to maintain design consistency and shared UX across distributed teams 📖 Read the summary in English: https://lnkd.in/e2YV4UDS
15
-
Qubika
88 mil seguidores
Microservices are increasingly popular, and communication between them is crucial for system performance. While REST with JSON is the traditional choice, our latest article by Senior Software Developer, Felipe Almeida Isern, explores gRPC (an open source Remote Procedure Call (RPC) framework created by Google) as an alternative. gRPC has been adopted with great success by companies like Uber and Spotify, particularly in scenarios where performance is the top priority, such as Uber’s real-time data transfer between client and server. Felipe compares the performance characteristics of gRPC and REST, outlining when gRPC can offer advantages and when sticking with more traditional REST remains the better choice. 👉 Read more at: https://lnkd.in/evPzaPUa
7
-
Luis M. Suarez
Salesforce • 502 seguidores
🚀 Setting up an Express API takes 10 lines of code… but making it production‑ready is a whole different story Most developers have had that moment: Spin up a new Node.js project, install Express, add a single route… and suddenly you have an API server running in under 10 lines. But here’s the reality: “Hello World” is easy. Production‑grade is not. Once you move beyond a toy project, you quickly realize how many capabilities a real‑world API needs before it’s ready for enterprise environments: observability, testing, linting, dependency injection, module strategy, logging, formatting, containerization, and more. That’s exactly why I created: express-esm-template https://lnkd.in/gv_t7dcg A canonical starter repo that bundles modern, scalable, enterprise‑ready patterns for Express. 📦 Capabilities Included Below is the full list of production‑grade features baked into the template. 1. TypeScript (with tsx for Dev mode) Strong typing, fast iteration, and modern DX. 2. ES Modules Future‑proof module strategy aligned with modern Node.js. 3. Dependency Injection (Inversify) Clean architecture, testability, and separation of concerns. 4. Jest Unit Testing Configured with ts-jest and a ready‑to‑use jest.config.cjs. 5. ESLint Static analysis and code quality enforcement. 6. Prettier Consistent formatting across the entire codebase. 7. Morgan (HTTP Access Logging) Nginx‑style access logs for every request. Morgan is a request logger designed for: HTTP method, URL, status code, response time Access log formats (combined, common, tiny) Streaming logs to stdout or a file Middleware integration 8. Pino (Application Event Logging) High‑performance structured JSON logs for application events. 9. Zod Robust validation of request parameters against predefined schemas. 10. VS Code Debugging (launch.json) Breakpoints, stepping, and smooth debugging experience. 11. tsconfig.json tuned for NodeNext Correct ESM behavior, strict typing, and clean build output. 12. Dockerfile (Containerization) A production‑grade Dockerfile that: Uses multi‑stage builds Produces a minimal runtime image Ensures reproducible deployments Aligns with enterprise container standards 12. Github CI workflow (YAML) Automated testing, linting, type‑checking, and Node version matrix builds, ensuring every commit is validated before reaching main. This is essential for: Cloud deployments CI/CD pipelines Kubernetes Local reproducibility 🧱 Why this template exists I wanted a clean, modern, batteries‑included Express starter that reflects how real teams build APIs today: Strong typing Clear separation of concerns Enterprise‑grade logging Testability from day one Modern ESM module strategy Container‑ready Developer experience that feels fast and frictionless Instead of rebuilding this scaffolding for every new project, I packaged it into a reusable template. 🔗 Repo express-esm-template https://lnkd.in/gv_t7dcg If you’re starting a new Express API in 2026, this gives you a solid foundation.
7
-
Sana Nayyab
Smile's Tech • 6 mil seguidores
6 Popular API architecture styles 1. gRPC 💡Description: gRPC (gRPC Remote Procedure Calls) is a high-performance, open-source framework developed by Google that uses HTTP/2 for transport, Protocol Buffers as the interface description language, and provides features such as authentication, load balancing, and more. 🔎Use Cases: Ideal for microservices, inter-service communication, and scenarios requiring high throughput and low latency. 2. SOAP (Simple Object Access Protocol) 💡Description: SOAP is a protocol for exchanging structured information in the implementation of web services. It relies on XML and typically uses HTTP or SMTP for message transmission. 🔎Use Cases: Often used in enterprise-level applications requiring high security, ACID-compliant transactions, and formal contracts (WSDL). 3. GraphQL 💡Description: GraphQL is a query language for APIs and a runtime for executing those queries by using a type system. It allows clients to request exactly the data they need and nothing more. 🔎Use Cases: Best for applications with complex data requirements and for scenarios where clients need flexibility in data retrieval. 4. Webhooks 💡Description: Webhooks are user-defined HTTP callbacks that are triggered by specific events. When an event occurs, the source application makes an HTTP request to the URL configured for the webhook. 🔎Use Cases: Commonly used for real-time notifications and integrations between different services, such as payment processing, version control systems, and CI/CD pipelines. 5. REST (Representational State Transfer) 💡Description: REST is an architectural style that uses standard HTTP methods (GET, POST, PUT, DELETE) to interact with resources represented as URLs. It is stateless and has a uniform interface. 🔎Use Cases: Widely used for web services and APIs due to its simplicity, scalability, and ease of integration with web technologies. 6. WebSocket 💡Description: WebSocket is a communication protocol that provides full-duplex communication channels over a single TCP connection. It allows for real-time data transfer between a client and server. 🔎Use Cases: Ideal for applications requiring real-time updates, such as chat applications, live notifications, online gaming, and collaborative tools. 🕯These API architecture styles cater to different needs and use cases, allowing developers to choose the most suitable approach for their applications. Want to know more? Follow me or connect
1
-
GeneXus
25 mil seguidores
GeneXus vs Vibe Coding, Knowledge vs Prompting ➡️ https://hubs.la/Q03GfjBG0 In this article, we explore how the industry is rediscovering the importance of executable specifications in the era of prompts, and examine why abstract knowledge modeling – as a strategic asset – offers substantial advantages. We’ll look at the key differences and benefits of modeling and deterministic generation versus executable specifications – or worse, prompts – and purely generative programming. Globant | ✍️ Gabriel Simonet #VibeCoding #Prompting #genexus #prompts #software
6
-
Ignacio C.
64 mil seguidores
🚀 How CI/CD Works – From Code to Production with Confidence ✨ Continuous Integration and Continuous Deployment (CI/CD) pipelines are the backbone of modern software delivery. They help teams ship faster, safer, and more predictably. Aquí tienes una guía visual paso a paso 👇 ✅ 🟢 1️⃣ Development 🔹 Developers pull code from GitHub Version Control 🔹 Create a local feature branch 🔹 Develop features and bug fixes 🔹 Open a Pull Request for review ✅ 🟣 2️⃣ Peer Review 🔹 Peer code review ensures code quality 🔹 Bug checks validate functionality 🔹 Security analysis scans for vulnerabilities 🔹 Once approved, code is merged into Master/Main ✅ 🟡 3️⃣ QA (Quality Assurance) 🔹 QA engineers test the new build 🔹 Conduct User Bug Analysis 🔹 Re-run security checks 💡 Goal: Catch issues before production ✅ 🔵 4️⃣ Pre-Production Deployment 🔹 Build is auto-deployed to Pre-Prod environments 🔹 Cloud jobs handle orchestration 🔹 Load balancer distributes traffic across Availability Zones ✅ 🟠 5️⃣ Production Deployment 🔹 After Pre-Prod validation, code is auto-deployed to Production 🔹 Load Balancers ensure high availability 🔹 Snapshot Backups keep data safe 💡 Why This Process Matters? ✅ Reduces manual errors ✅ Speeds up release cycles ✅ Increases confidence in deployments ✅ Enables continuous improvement and feedback 🔥 Quick Best Practices: 🔸 Keep builds reproducible and deterministic 🔸 Automate security and compliance checks 🔸 Version everything (code, infrastructure, pipelines) 🔸 Monitor deployments with clear rollback strategies 💪 Ready to level up your delivery pipelines? ✅ Save this post to reference later ✅ Comment below: What’s your biggest challenge with CI/CD? ✅ Follow me for weekly guides on DevOps, GitOps, and modern engineering 👍 Like if this clarified your understanding 🔖 Save for later 🔁 Share to help your network 💬 Tag a teammate working on CI/CD pipelines #CICD #DevOps #ContinuousIntegration #ContinuousDelivery #SoftwareEngineering #CloudComputing #Automation #GitHub #PipelineAutomation #InfrastructureAsCode #PlatformEngineering #CloudNative #AWS #AzureDevOps #GitOps #Security #QualityAssurance #SoftwareDelivery #EngineeringExcellence #Microservices #Kubernetes #Agile #DeveloperExperience #CloudArchitecture #ModernEngineering #TechLeadership #CodeReview #SRE #CloudSecurity #ReleaseManagement
56
1 comentario -
Bitegarden
286 seguidores
🔧 Are you managing SonarQube instances? Then this post is for you. The role of a SonarQube administrator is essential to ensure development teams can focus on what really matters: building quality, secure software. A properly configured SonarQube instance not only enhances collaboration but also ensures the tool delivers its full potential. But what skills should a great administrator have? ✅ Monitor and maintain multiple projects ✅ Automate tasks to save time ✅ Improve visibility of key project insights ✅ Efficiently manage and maintain plugins At bitegarden, we've developed a set of plugins designed to make a SonarQube admin’s life easier and more productive: 🔹 Universal Plugin Manager – Easily install, update, and remove plugins 🔹 Control Center – Organize your instance and perform bulk project actions 🔹 Project Tag – Automate and manage project tagging with ease More info in our blog: https://lnkd.in/dEr4YKdV
6
-
LlamaIndex
283 mil seguidores
New LlamaParse v2 API + New SDKs for LlamaCloud are here 🦙 LlamaParse API v2 is here with cleaner configuration, structured outputs, as well as brand new llama-cloud SDKs for Python and Typescript 🚀 We've completely rebuilt the API based on feedback from thousands of developers building document agents. Here's what's new: · LlamaParse: 📋 Content-focused configuration - organize parameters into intuitive categories (input_options, output_options, processing_options) instead of dozens of flat parameters 🎯 Structured outputs with precise control - the expand parameter gives you exact control over returned content: text, markdown, structured JSON, or metadata ⚡ Enhanced parsing quality paired with significantly less complexity - focus on what to parse rather than how to parse 🔧 Improved UX and better Typescript support · New SDKs for LlamaCloud: The new SDKs replace our existing llama-cloud-services packages and support our entire suite of agentic document understanding modules, including LlamaParse and LlamaExtract. Current v1 users can keep using the existing API and SDK - nothing breaks, but v2 is the recommended path for new projects. Install the new SDKs: Python: pip install llama-cloud TS: npm i '@llamaindex/llama-cloud' Read the full announcement here: https://lnkd.in/eTmkGXDM
31
-
ATO Tech
The Programmer’s University • 687 seguidores
You already built a todo app tutorial. Don’t delete it. Upgrade it. Here’s how to turn it into a fullstack portfolio project: Add auth Users can sign up / log in Each user only sees their todos Move data to a real DB Start with MongoDB / Postgres No more hard-coded arrays Create a REST API GET /todos → list POST /todos → create PUT /todos/:id → update DELETE /todos/:id → delete Handle errors properly Show “Saving…” and “Failed to save” states Validate inputs on both frontend + backend Deploy everything Frontend: Vercel/Netlify Backend: Render/Railway Add the live link + GitHub link to your CV Now it’s no longer “just a todo app”. It’s: “A fullstack task manager with auth, API, and database, fully deployed.” Same codebase. Higher value.
1
-
Bonevy BEBY
Tessi • 979 seguidores
🔥 #Registration Management-ORM #ejb, #jpa, #wildfly, #hibernate,Java EE Developed the registration management module using Java EE technologies. The system handles user registration processes efficiently, ensuring data integrity and scalability. Technologies & Stack Used: Backend & ORM: Java EE, EJB, JPA, Hibernate Application Server: WildFly Database: PostgreSQL / MySQL Additional Tools: Maven (build management), Git (version control) Role & Responsibilities: Designed and implemented the registration module using EJB, JPA, and Hibernate Managed data persistence and transactions through ORM best practices Deployed and tested the application on WildFly server Ensured performance, security, and reliability of the registration system
6
-
Tarun Kumar
First American (India) • 638 seguidores
🔥 𝐖𝐡𝐲 𝐘𝐨𝐮𝐫 𝐒𝐩𝐫𝐢𝐧𝐠 𝐁𝐞𝐚𝐧𝐬 𝐀𝐫𝐞𝐧’𝐭 𝐓𝐡𝐫𝐞𝐚𝐝-𝐒𝐚𝐟𝐞 (𝐄𝐯𝐞𝐧 𝐖𝐡𝐞𝐧 𝐘𝐨𝐮 𝐓𝐡𝐢𝐧𝐤 𝐓𝐡𝐞𝐲 𝐀𝐫𝐞) 🍀 Most Spring apps fail under load for one simple reason: Singleton beans + shared mutable state = hidden race conditions. 👉🏻 Here’s the quick breakdown: 1️⃣ 𝑺𝒊𝒏𝒈𝒍𝒆𝒕𝒐𝒏 𝑩𝒆𝒂𝒏𝒔 𝑨𝒓𝒆 𝑺𝒉𝒂𝒓𝒆𝒅 𝑨𝒄𝒓𝒐𝒔𝒔 𝑨𝒍𝒍 𝑻𝒉𝒓𝒆𝒂𝒅𝒔 By default, almost every bean in Spring is a singleton. This means: 🔸one instance 🔸reused for every request 🔸accessed by many threads at the same time ⁉️ If your bean stores mutable fields, you’ve created shared state without realizing it. 2️⃣ 𝑾𝒉𝒂𝒕 𝑨𝒄𝒕𝒖𝒂𝒍𝒍𝒚 𝑪𝒂𝒖𝒔𝒆𝒔 𝑻𝒉𝒓𝒆𝒂𝒅 𝑰𝒔𝒔𝒖𝒆𝒔 You run into trouble when a bean holds: 🔹counters 🔹lists or maps 🔹cached objects 🔹request-specific data 🔹temporary values 🏗️ Multiple threads write to these fields → unpredictable behavior. 3️⃣ 𝑾𝒉𝒚 𝑰𝒕’𝒔 𝑯𝒂𝒓𝒅 𝒕𝒐 𝑵𝒐𝒕𝒊𝒄𝒆 🧵 Thread issues don’t show up locally. With 1–2 requests, everything looks fine. Under 500+ concurrent hits, your app: 🔸returns wrong data 🔸mixes user sessions 🔸fails randomly 🪄 This is not Spring’s fault. It’s how singletons work. 4️⃣ 𝑯𝒐𝒘 𝒕𝒐 𝑺𝒕𝒂𝒚 𝑺𝒂𝒇𝒆 Simple rules that prevent 90% of issues: 🔹Keep singleton beans stateless 🔹Move request data into method params 🔹Use @𝑹𝒆𝒒𝒖𝒆𝒔𝒕𝑺𝒄𝒐𝒑𝒆 only when needed 🔹Use thread-safe structures if storing shared data 🔹Never store temp values inside services ⚡ Stateless beans scale. Stateful ones bite back. 5️⃣ 𝑻𝒉𝒆 𝑶𝒏𝒆-𝑳𝒊𝒏𝒆 𝑻𝒓𝒖𝒕𝒉 ✨ Spring won’t protect your beans from races. 💡 𝑻𝒉𝒓𝒆𝒂𝒅 𝒔𝒂𝒇𝒆𝒕𝒚 𝒊𝒔 𝒅𝒆𝒗'𝒔 𝒋𝒐𝒃, 𝒏𝒐𝒕 𝒕𝒉𝒆 𝒇𝒓𝒂𝒎𝒆𝒘𝒐𝒓𝒌’𝒔. #J16 #DevReWire #SpringBoot #Java #ThreadSafety #Concurrency #Backend #Beans #CleanCode #ATKWrites
6
-
UniDocLib
1 mil seguidores
📑 Want to learn how to merge and split PDF files in Golang? 💻 With UniPDF, it’s super easy and fast! Whether you're handling documents for work or personal projects, this guide will show you exactly how to do it with just a few lines of code. 👉 Read more: https://lnkd.in/drXPa-Gi 👉 Free trial: https://lnkd.in/dcwSBNUf #unidoc #Golang #PDFmanagement #DevTools
1
-
FFactory
66 seguidores
🏗️ Screaming Architecture + DDD: File Structures That Tell Your Story Tired of project structures that feel like a disorganized closet? 😩 It's time to embrace Screaming Architecture! This principle—popularized by Robert C. Martin (Uncle Bob)—suggests your directory structure should scream the domain of your application, not the framework you're using. When you pair this with Domain-Driven Design (DDD), you unlock a powerful synergy: 🔹 Stop Organizing by Tech: Ditch top-level folders like /controllers, /services, or /models. 🔹 Start Organizing by Domain: Structure your code around Bounded Contexts (e.g., /Shipping, /Payments, /Inventory). The Result? Anyone new to the project knows immediately what the system does just by looking at the file tree. It tells the story of your business. This is more than just clean code; it’s architectural clarity. It makes scaling easier, enforces separation, and drastically lowers the cognitive load for engineers. What's the one DDD concept you've found most transformative in structuring your projects? Share in the comments! 👇 #DDD #DomainDrivenDesign #SoftwareArchitecture #CleanCode #ScreamingArchitecture #SoftwareDevelopment #TechLeadership
2
1 comentario -
Zartis
74 mil seguidores
🧼 Writing clean code in Angular isn't just about prettier files. It's about performance, scalability, and future-proofing your app. In our latest tech blog, our frontend expert and Sr. Software Engineer, Mauricio Mage shares practical ways to apply SOLID principles, embrace reactive patterns, and leverage Angular’s latest features like Signals for cleaner, more maintainable code. Whether you're building a new Angular project or refactoring legacy code, this is a must-read. 📖 Dive in: Writing Clean Code in Angular: https://lnkd.in/dcEYBSyg #Angular #CleanCode #SoftwareEngineering #Frontend #WebDevelopment #ZartisTechInsights #TeamZartis
33