Catherine Loirat

🚀 Enterprise Architect ≠ Solution Architect Too often, Enterprise Architecture is mistaken for Solution Architecture—but they serve different purposes: 🔹 Enterprise Architect (EA) Focuses on the big picture across the organization Aligns business strategy with technology roadmaps Defines enterprise-wide standards, capabilities, and governance Ensures long-term agility, scalability, and resilience 🔹 Solution Architect (SA) Focuses on specific solutions or projects Designs systems that solve targeted business needs Selects technologies, integrations, and frameworks for delivery Ensures the solution fits into the broader enterprise landscape 👉 EA builds the strategic blueprint. 👉 SA delivers the tactical solutions within that blueprint. Both are critical—but Enterprise Architecture is not Solution Architecture. #EnterpriseArchitecture #SolutionArchitecture #DigitalTransformation #Architecture #SystemsLimited #TOGAF #Zachman

641

51 commentaires

Many still think of Enterprise Architecture as something abstract — a tower of diagrams, frameworks, and documentation. But it isn't. In reality, EA is about alignment. - A common language that connects strategy to execution. - A clear plan for action that turns complexity into direction. - Yes-able insights that make decisions faster and smarter. Architecture is not a luxury. It’s how organizations stay coherent while they change. Move from “ivory tower” to impact in motion. **** 📘 Discover my new book 'Architecture in action'. Reading this book will help you transform "enterprise architecture on paper" into actionable enterprise architecture that shapes decisions, accelerates transformation, and connects strategy with execution in a tangible way. 🤘 25% discount on the PDF version until and including this Sunday 19 October - use the code FOLLOW (https://lnkd.in/en3YwZ8A) #EnterpriseArchitecture #Transformation #Leadership #StrategyExecution #ArchitectureInAction

114

22 commentaires

Here is how I do CI/CD for webMethods Integration Server. This approach has been battle-tested since 2008 and works for all scenarios I have seen so far. These are the steps: - All developers have their own environment and commit their changes into the VCS, usually multiple times per day. - The CI server (e.g. Jenkins) picks up those changes, builds the package, and runs the unit tests. - On success, a package ZIP file is created and uploaded to the binary repository (e.g. Nexus, Artifactory). You can also take GitHub here, but be aware that it is used in a fundamentally different role, compared to its usual VCS functionality. - On further test environments the package ZIP file is installed from the binary repository and tests are executed. These environments do not interact with the VCS, that is solely the job of the CI server. - Once all tests have been passed, the package ZIP file gets promoted from snapshot to official version (often called "release"). That can happen automatically for Continuous Deployment. Or you do it manually for additional control over the time of the update. - Once release status has been reached, you use the exact same package ZIP file to create a new container image, update your running VMs, or deliver a new version to your customers. All this usually with automation. The approach has the following advantages for me: - Conceptually simple with clear steps and responsibilities. - Tool-agnostic and flexible. - Compatible with standard approaches from e.g. the Java world. #webmethods #cicd #testing #integrationserver #onprem #sdlc

56

3 commentaires

The value of EA is rarely in the Architecture Review Board. And none of your stakeholders will ever use the term “alignment.” Both standards and alignment are your job. Not theirs. When you are “doing” Enterprise Architecture, don’t explain your activities. Explain the results. Explain what you *hope* they will do with the results. Work with them to figure out how to fit *their* response to your results into *their* work processes. If they cannot use your results, either you are talking to the wrong person, or you are producing something useless. Architect, be useful.

128

41 commentaires

🚀 Just published a new video: Building a custom engine agent for Microsoft 365 Copilot — powered by Mistral AI + the M365 Agents Toolkit + GitHub Copilot. 🔧 What’s inside: - Using Mistral AI LLM deployed in Azure AI Foundry inside an agent created by M365 Agents Toolkit - Tailoring it to my needs with GitHub Copilot (Agent mode) - Testing in the M365 Agents Playground - Deploying & running it directly in M365 Copilot 🎥 A full end-to-end demo — from setup to deployment. Why this matters: the ability to plug in your own custom model inside Microsoft 365 opens up a whole new world of possibilities — from specialized knowledge bases to domain-specific copilots. I’d love your take: How would you use a custom engine agent inside M365 Copilot? #Microsoft365 #Copilot #MistralAI #GitHubCopilot #AIagents

154

2 commentaires

𝐄𝐧𝐭𝐞𝐫𝐩𝐫𝐢𝐬𝐞 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞'𝐬 𝐑𝐨𝐥𝐞 𝐢𝐧 𝐁𝐮𝐬𝐢𝐧𝐞𝐬𝐬 𝐚𝐧𝐝 𝐓𝐞𝐜𝐡𝐧𝐨𝐥𝐨𝐠𝐲 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭 🎯 Too often, we get lost in the layers and boxes of a traditional Enterprise Architecture diagram. But this one? This is a different kind of blueprint. It's the 𝐜𝐞𝐧𝐭𝐫𝐚𝐥 𝐧𝐞𝐫𝐯𝐨𝐮𝐬 𝐬𝐲𝐬𝐭𝐞𝐦 of the modern enterprise, showing how EA is the vital link between strategy and every critical business function. This isn't a static model; it’s a living hub, actively engaged with the entire organization. Look at the interconnected spokes: 𝐒𝐭𝐫𝐚𝐭𝐞𝐠𝐲 🚀: EA doesn't just receive strategy; it architects it. It takes a 𝐁𝐮𝐬𝐢𝐧𝐞𝐬𝐬 𝐎𝐮𝐭𝐜𝐨𝐦𝐞 𝐒𝐭𝐚𝐭𝐞𝐦𝐞𝐧𝐭 and transforms it into a tangible, executable plan, ensuring that our vision is built on a solid foundation. 𝐏𝐥𝐚𝐧𝐧𝐢𝐧𝐠 & 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐦𝐞𝐧𝐭 🛠️: From 𝐂𝐚𝐩𝐚𝐛𝐢𝐥𝐢𝐭𝐲-𝐛𝐚𝐬𝐞𝐝 𝐏𝐥𝐚𝐧𝐧𝐢𝐧𝐠 to 𝐏𝐨𝐫𝐭𝐟𝐨𝐥𝐢𝐨 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭, EA provides the crucial architectural guardrails. It ensures every project, every program, and every investment is a deliberate step toward our strategic goals, not a siloed, reactive measure. 𝐄𝐱𝐞𝐜𝐮𝐭𝐢𝐨𝐧 & 𝐃𝐞𝐥𝐢𝐯𝐞𝐫𝐲 📦: This is where theory meets reality. EA enables 𝐏𝐫𝐨𝐠𝐫𝐚𝐦/𝐏𝐫𝐨𝐣𝐞𝐜𝐭 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭 and 𝐂𝐨𝐧𝐭𝐢𝐧𝐮𝐨𝐮𝐬 𝐃𝐞𝐥𝐢𝐯𝐞𝐫𝐲 (𝐃𝐞𝐯𝐎𝐩𝐬). It's the architect behind the scenes, designing an ecosystem that allows for both rapid innovation and reliable, seamless execution. 𝐎𝐩𝐞𝐫𝐚𝐭𝐢𝐨𝐧𝐬 & 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭 📊: After delivery, EA’s work continues. It designs the backbone for 𝐒𝐞𝐫𝐯𝐢𝐜𝐞 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧t, ensuring our processes are efficient and our operations are smooth. It’s also the key to effective 𝐆𝐨𝐯𝐞𝐫𝐧𝐚𝐧𝐜𝐞, 𝐑𝐢𝐬𝐤 𝐂𝐨𝐧𝐭𝐫𝐨𝐥, 𝐒𝐞𝐜𝐮𝐫𝐢𝐭𝐲, 𝐚𝐧𝐝 𝐂𝐨𝐦𝐩𝐥𝐢𝐚𝐧𝐜𝐞, embedding these non-negotiables into the very design of the enterprise. 𝐓𝐡𝐞 𝐅𝐨𝐮𝐧𝐝𝐚𝐭𝐢𝐨𝐧 𝐃𝐚𝐭𝐚 & 𝐏𝐫𝐨𝐜𝐞𝐬𝐬𝐞𝐬 🧱: EA provides the framework for managing 𝐏𝐫𝐨𝐜𝐞𝐬𝐬, 𝐑𝐮𝐥𝐞𝐬, 𝐚𝐧𝐝 𝐃𝐚𝐭𝐚. It's the discipline that standardizes these core components, turning chaos into order and enabling consistent, predictable outcomes. This diagram proves that Enterprise Architecture is not a department you go to; it's the intelligence embedded throughout the organization, empowering every function to operate with a unified purpose. It’s the engine of 𝐄𝐧𝐭𝐞𝐫𝐩𝐫𝐢𝐬𝐞 𝐓𝐫𝐚𝐧𝐬𝐟𝐨𝐫𝐦𝐚𝐭𝐢𝐨𝐧. What part of this interconnected hub do you find most critical for your organization's success? Let's discuss! 👇 ➕ Follow Sumeet Goenka 🔔 ♻️ Repost | 💬 Comment | 👍 Like 🚀 Visit Yallo and stay connected for more insights 👉 https://vist.ly/48ygj Credit: Intel #EnterpriseArchitecture #DigitalTransformation #StrategyExecution #BusinessAgility #Governance #ITStrategy #DevOps

82

4 commentaires