ContentBox RSS Feed https://www.ortussolutions.com Ortus Solutions, Corp (www.ortussolutions.com) http://www.rssboard.org/rss-specification FeedGenerator Sat, 04 Apr 2026 19:47:06 GMT Sat, 04 Apr 2026 19:47:06 GMT AI agents are transforming how we build software. Unlike traditional chatbots that just answer questions, agents can reason about what tools they need, decide when to use them, chain multiple actions together, and remember what happened earlier in a conversation. https://www.ortussolutions.com/blog/how-to-develop-ai-agents-using-boxlang-ai-a-practical-guide Fri, 03 Apr 2026 21:28:00 GMT lmajano@ortussolutions.com (Luis Majano) BoxLang Community Into The Box News Releases https://www.ortussolutions.com/blog/how-to-develop-ai-agents-using-boxlang-ai-a-practical-guide A chatbot with no memory isn't a conversation — it's a series of isolated queries. Every message starts from scratch. The user has to re-explain who they are, what they're working on, and what was just said. It's exhausting, and it signals that the AI isn't really listening. https://www.ortussolutions.com/blog/boxlang-ai-deep-dive-part-7-of-7-mcp-the-protocol-that-connects-everything Fri, 03 Apr 2026 21:27:00 GMT lmajano@ortussolutions.com (Luis Majano) BoxLang Community Into The Box News Releases https://www.ortussolutions.com/blog/boxlang-ai-deep-dive-part-7-of-7-mcp-the-protocol-that-connects-everything A chatbot with no memory isn't a conversation — it's a series of isolated queries. Every message starts from scratch. The user has to re-explain who they are, what they're working on, and what was just said. It's exhausting, and it signals that the AI isn't really listening. https://www.ortussolutions.com/blog/boxlang-ai-deep-dive-part-6-of-7-memory-systems-rag-building-ai-that-remembers Fri, 03 Apr 2026 21:26:00 GMT lmajano@ortussolutions.com (Luis Majano) BoxLang Community Into The Box News Releases https://www.ortussolutions.com/blog/boxlang-ai-deep-dive-part-6-of-7-memory-systems-rag-building-ai-that-remembers Vendor lock-in is the silent killer of AI projects. You pick OpenAI, build everything against the OpenAI API, and then GPT-5 launches at three times the price. Or a competitor launches a model that's faster for your use case. Or you need to self-host for compliance. Or your client is on AWS and wants Bedrock. https://www.ortussolutions.com/blog/boxlang-ai-deep-dive-part-5-of-7-one-api-17-providers-the-provider-architecture-deep-dive Fri, 03 Apr 2026 21:25:00 GMT lmajano@ortussolutions.com (Luis Majano) BoxLang Community Into The Box News Releases https://www.ortussolutions.com/blog/boxlang-ai-deep-dive-part-5-of-7-one-api-17-providers-the-provider-architecture-deep-dive Agents make live LLM calls. They invoke real tools. They have non-deterministic outputs. Standard unit testing approaches fall apart. You can't mock every provider. You can't replay a conversation from three weeks ago. You can't confidently tell stakeholders that the agent you deployed today behaves the same way it did when you signed off on it. https://www.ortussolutions.com/blog/boxlang-ai-deep-dive-part-4-of-7-middleware-the-missing-layer-in-every-ai-framework Fri, 03 Apr 2026 21:23:00 GMT lmajano@ortussolutions.com (Luis Majano) BoxLang Community Into The Box News Releases https://www.ortussolutions.com/blog/boxlang-ai-deep-dive-part-4-of-7-middleware-the-missing-layer-in-every-ai-framework The problem with most multi-agent frameworks is that the orchestration layer is bolted on — you're managing agent references manually, passing outputs between them by hand, and hoping you haven't introduced a cycle. There's no concept of hierarchy. No cycle detection. No way to ask "who's in charge here?" or "how deep in the tree am I?" https://www.ortussolutions.com/blog/boxlang-ai-deep-dive-part-3-of-7-multi-agent-orchestration-building-ai-teams-that-work Fri, 03 Apr 2026 07:34:00 GMT lmajano@ortussolutions.com (Luis Majano) BoxLang Community Into The Box News Releases https://www.ortussolutions.com/blog/boxlang-ai-deep-dive-part-3-of-7-multi-agent-orchestration-building-ai-teams-that-work Function calling is where most AI frameworks look deceptively simple on the surface and turn into a mess underneath. You define a tool, pass it to the LLM, and when the LLM calls it — who handles the lifecycle? Who fires observability events? Who serializes the result? Who resolves the tool by name when the only thing you have is a string? https://www.ortussolutions.com/blog/boxlang-ai-deep-dive-part-2-of-7-building-a-production-grade-ai-tool-ecosystem Fri, 03 Apr 2026 07:29:00 GMT lmajano@ortussolutions.com (Luis Majano) BoxLang Community Into The Box News Releases https://www.ortussolutions.com/blog/boxlang-ai-deep-dive-part-2-of-7-building-a-production-grade-ai-tool-ecosystem Every AI framework eventually hits the same wall: your system prompts start drifting. Agent A has a slightly different version of the SQL rules than Agent B. The tone policy on your support bot is three weeks behind the tone policy on your documentation bot. Someone copy-pasted the wrong version. Nobody noticed. https://www.ortussolutions.com/blog/boxlang-ai-deep-dive-part-1-of-7-the-skills-revolution Fri, 03 Apr 2026 07:23:00 GMT lmajano@ortussolutions.com (Luis Majano) BoxLang Community Into The Box News Releases https://www.ortussolutions.com/blog/boxlang-ai-deep-dive-part-1-of-7-the-skills-revolution AI is no longer an optional feature it’s a necessity. But as the ecosystem grows, developers are often left juggling multiple SDKs, wrestling with vendor lock-in, and managing complex orchestration. It shouldn't be your problem to solve. https://www.ortussolutions.com/blog/join-our-webinar-intro-to-boxlang-ai-one-api-to-rule-them-all-part-ii Thu, 02 Apr 2026 11:51:00 GMT mherrera@ortussolutions.com (Maria Jose Herrera) https://www.ortussolutions.com/blog/join-our-webinar-intro-to-boxlang-ai-one-api-to-rule-them-all-part-ii It's been a while since we've shipped something this big. BoxLang AI 3.0 is a ground-up rethink of how AI agents, models, and tools work in the BoxLang ecosystem — and it lands with ten major features at once. https://www.ortussolutions.com/blog/boxlang-ai-v3-has-landed-multi-agent-orchestration-tooling-skills-and-so-much-more Thu, 02 Apr 2026 08:41:00 GMT lmajano@ortussolutions.com (Luis Majano) BoxLang Community Into The Box News Releases https://www.ortussolutions.com/blog/boxlang-ai-v3-has-landed-multi-agent-orchestration-tooling-skills-and-so-much-more March brought exciting momentum across the Ortus ecosystem, from new BoxLang tooling and cloud deployments to continued platform enhancements. We shared fresh insights on modernizing CFML systems, improving JVM performance, and integrating AI into development workflows. https://www.ortussolutions.com/blog/ortus-boxlang-march-recap-2026 Tue, 31 Mar 2026 17:53:33 GMT vcampos@ortussolutions.com (Victor Campos) https://www.ortussolutions.com/blog/ortus-boxlang-march-recap-2026 BoxLang Cloud Servers are designed for modern cloud environments — and now you can deploy them in minutes directly from your preferred marketplace. A Simpler Way to Run Modern Applications in the Cloud Deploying and managing application runtimes in the cloud shouldn’t be complex. Yet many teams still spend significant time on: configuring environments aligning infrastructure across teams maintaining consistency between dev, staging, and production BoxLang Cloud Servers simplify this process by providing ready-to-run, standardized environments that align naturally with modern cloud workflows. Introducing BoxLang Cloud Servers BoxLang is a modern JVM-based runtime designed to help teams build, run, and evolve applications with flexibility and control. With BoxLang Cloud Servers, you can now deploy directly from: Amazon Web Services Marketplace Microsoft Azure Marketplace Google Cloud Platform Marketplace This means faster access, simplified procurement, and immediate alignment with your existing cloud infrastructure. Key Benefits 🚀 Deploy in Minutes Get started instantly with pre-configured environments. No manual installation No complex setup No environment drift You can move from idea to running environment in minutes. ⚙️ Consistent, Production-Ready Environments Every deployment is standardized and aligned with best practices. predictable behavior across environments easier collaboration across teams reduced deployment errors ☁️ Built for Modern Cloud Workflows BoxLang Cloud Servers integrate naturally with: CI/CD pipelines container-based architectures scalable infrastructure They are designed to fit into how modern teams already work. 🧾 Streamlined Procurement Deploying through cloud marketplaces offers clear advantages: faster internal approvals consolidated billing with your cloud provider no need for complex vendor onboarding This is especially valuable for enterprise teams. 🧠 Flexibility and Control BoxLang gives teams the ability to: evolve their architecture over time integrate with modern JVM ecosystems maintain control over their runtime and deployment strategy A Better Starting Point for Cloud Projects Whether you're: launching new applications modernizing existing systems standardizing environments across teams BoxLang Cloud Servers provide a clean, efficient foundation to build on. Available Across Major Cloud Providers Choose the platform that fits your organization: Deploy on Amazon Web Services Run on Microsoft Azure Scale with Google Cloud Platform Same experience. Same consistency. Anywhere. Get Started BoxLang Cloud Servers are designed to reduce friction and accelerate your path to production. launch quickly standardize your environments simplify your operations Explore the marketplaces and deploy your first BoxLang environment today. https://www.ortussolutions.com/blog/deploy-boxlang-in-minutes-boxlang-cloud-servers-now-available-on-aws-azure-google-cloud-marketplaces Thu, 26 Mar 2026 18:18:00 GMT cristobal@ortussolutions.com (Cristobal Escobar) https://www.ortussolutions.com/blog/deploy-boxlang-in-minutes-boxlang-cloud-servers-now-available-on-aws-azure-google-cloud-marketplaces Many organizations know they need to modernize their legacy applications. They see the risks. They feel the operational pressure. They understand the long-term impact. But the initiative never starts. Not because the problem is unclear. Because the budget is. The Real Problem Is Not Technology. It’s Budgeting. In many organizations, especially in enterprise or public sector environments, modernization competes with multiple priorities: new product initiatives compliance requirements operational costs short-term revenue drivers As a result, modernization is often treated as a large, one-time project that requires significant upfront investment. And that is where things get stuck. No approved budget. No clear starting point. No progress. Meanwhile, the system continues to age. Why Big Modernization Projects Rarely Get Approved Traditional modernization proposals often fail for predictable reasons: they require large capital investment the scope is difficult to define upfront ROI is long-term and hard to quantify there is fear of disruption to business operations From a leadership perspective, the risk of starting feels higher than the risk of waiting. So the decision is delayed. A Different Approach: Think in Monthly Investment Instead of asking: “What is the full cost of modernization?” A more practical question is: “What is the most valuable work we can do each month within a defined budget?” This shifts modernization from a capital project to an operational investment. Examples: €5K per month €10K per month €15K per month Over a period of 6 to 12 months. This model aligns much better with how organizations actually plan and approve spending. What Can You Achieve with a Monthly Budget? Modernization does not need to happen all at once. With a structured approach, meaningful progress can be made every month. Months 1–2: Understand and Stabilize Platform assessment and risk identification Identification of critical vulnerabilities Quick wins in security and stability Months 3–4: Reduce Immediate Risk Fix high-impact instability issues Improve performance bottlenecks Address fragile components Months 5–6: Improve Operational Foundation Introduce CI/CD pipelines Improve logging and observability Standardize environments Months 6–12: Enable Long-Term Modernization Refactor key components Improve architecture incrementally Prepare for containerization or cloud adoption Progress happens step by step, without disrupting daily operations. Why This Approach Works in the Real World A monthly budget model solves several common challenges: It fits within existing operational budgets It avoids large upfront commitments It delivers visible progress early It reduces risk continuously instead of delaying it It creates alignment between business and engineering Most importantly, it is approvable. From Technical Debt to Controlled Progress Legacy systems accumulate technical debt over time. Trying to eliminate all of it at once is unrealistic. A better approach is to reduce risk in controlled steps. Each month focuses on: removing a specific risk stabilizing a specific area improving a specific capability Over time, these incremental improvements compound into meaningful transformation. How Teams Prioritize Work Under Budget Constraints When working within a fixed budget, prioritization becomes critical. Effective teams focus on: high-risk areas first single points of failure components that affect stability or security areas that unlock future improvements The focus shifts from adding features to reducing risk and increasing capability. Where Modern Runtimes Fit In As systems become more stable, some organizations begin to evaluate modern runtime options that better align with current JVM ecosystems. Platforms such as BoxLang provide a modern dynamic language environment while maintaining compatibility with existing CFML applications. This allows teams to improve performance, adopt modern development practices, and reduce operational complexity without rewriting their core business logic. For some organizations, upgrading within their current platform is the right decision. For others, evaluating newer runtimes becomes part of their long-term strategy. The Most Important Shift: Think in Time, Not Scope One of the most effective mindset shifts is this: Stop asking: “What can we build?” Start asking: “What is the highest risk we can eliminate this month?” This change alone makes modernization more practical, measurable, and achievable. Start Small. Move Forward. Reduce Risk. The biggest risk for most organizations is not having a legacy system. It is delaying action until the system forces a crisis. Modernization does not require a massive project to begin. It requires a clear starting point and a realistic plan. If your organization is facing budget constraints but knows modernization cannot be postponed indefinitely, a monthly-budget approach can provide a practical way forward. At Ortus Solutions, we help teams structure and execute modernization efforts within real-world budget constraints, focusing on what delivers the most impact over time. Contact us. https://www.ortussolutions.com/blog/how-to-modernize-legacy-applications-with-a-fixed-monthly-budget-without-a-big-rewrite Wed, 25 Mar 2026 22:10:00 GMT cristobal@ortussolutions.com (Cristobal Escobar) https://www.ortussolutions.com/blog/how-to-modernize-legacy-applications-with-a-fixed-monthly-budget-without-a-big-rewrite Most ColdFusion systems don’t fail because of traffic Most ColdFusion applications don’t break under load. They break under change. A small update triggers unexpected side effects. A deployment introduces instability. A simple feature takes weeks because no one wants to touch certain parts of the codebase. This isn’t a performance problem. It’s an architecture problem. And in many mature CFML environments, the root cause is the same: 👉 A fragile monolith that has grown without structure. The hidden cost of monolithic ColdFusion applications Monolithic applications are not inherently bad. Many started as fast, productive solutions. But over time, without clear boundaries and patterns, they evolve into: Tightly coupled components Shared state across unrelated features Unclear ownership of logic Increasing fear around deployments The result? Slower development cycles Higher risk with every release Difficulty onboarding new developers Growing technical debt And most importantly: 👉 Every change becomes a potential incident. Why rewriting everything is rarely the answer When teams recognize these issues, the first instinct is often: “We need to rebuild this from scratch.” In reality, full rewrites almost always fail or stall because they are: Expensive Time-consuming Risky for business continuity While the rewrite is happening, the existing system still needs to run, evolve, and support users. So the real question is not: ❌ How do we replace the system? ✔️ How do we evolve it safely? The smarter path: Progressive modularization Modernizing a ColdFusion application doesn’t require a “big bang.” It requires controlled, incremental change. Progressive modularization focuses on: Isolating responsibilities Extracting reusable services Introducing clear boundaries between components Reducing coupling over time Instead of breaking production, you reshape it gradually. This allows teams to: Continue delivering features Reduce risk step by step Improve maintainability without disruption Applying modern CFML architecture patterns This is where experienced architecture matters. Using frameworks like ColdBox, teams can introduce: Clear MVC separation Service layers for business logic Modular application design Event-driven patterns These patterns don’t just improve code organization — they: Reduce unintended side effects Make systems easier to reason about Enable parallel development across teams Over time, the monolith becomes structured, predictable, and scalable. CI/CD and consistent environments: The missing foundation Architecture alone is not enough. Many ColdFusion teams still struggle with: Differences between dev, staging, and production Manual deployments Lack of repeatability This is where CI/CD pipelines and environment consistency become critical. By introducing: Automated builds and deployments Containerized environments Version-controlled infrastructure Teams eliminate the classic: “It worked in dev, but failed in production.” And move toward: Faster releases Safer deployments Higher confidence in every change Real scalability vs temporary fixes When performance issues appear in monolithic systems, the typical response is: Add more CPU Increase memory Add caching layers These can help temporarily. But without architectural changes, they are just patches on top of deeper problems. True scalability comes from: Decoupled components Independent scaling of services Efficient resource usage Clear system boundaries 👉 In other words: architecture, not hardware, determines scalability. What modernization actually looks like in practice A successful modernization journey typically includes: Assessment Understanding current architecture, bottlenecks, and risks Stabilization Fixing critical issues and reducing immediate fragility Modularization Introducing structure and separating concerns Modernization Adding CI/CD, containers, and scalable patterns Each phase builds on the previous one — without disrupting production. Final thought: Evolution beats replacement ColdFusion systems don’t need to be replaced to become modern. They need to be restructured, stabilized, and evolved. The teams that succeed are not the ones that attempt massive rewrites. They are the ones that: Introduce structure where there was none Reduce risk with every iteration Build toward a modular, scalable future Want to explore what this could look like for your system? If you’re dealing with a fragile monolith, slow delivery cycles, or risky deployments, it might be worth taking a step back and evaluating your architecture. At Ortus Solutions, we help teams modernize ColdFusion applications without breaking production — through structured, phased approaches that reduce risk and improve long-term scalability. Feel free to reach out if you’d like to explore your options or get a second opinion on your current architecture. https://www.ortussolutions.com/blog/from-monolith-to-modular-modernizing-coldfusion-architecture-without-breaking-production Tue, 24 Mar 2026 11:09:00 GMT cristobal@ortussolutions.com (Cristobal Escobar) https://www.ortussolutions.com/blog/from-monolith-to-modular-modernizing-coldfusion-architecture-without-breaking-production Not everyone can make it on-site and that’s exactly why Into the Box 2026 Virtual Edition exists. This year, we’re bringing the full conference days experience online, so you can tap into the same insights, sessions, and innovation no matter where you are in the world. https://www.ortussolutions.com/blog/into-the-box-2026-goes-virtual-watch-on-demand-from-anywhere Mon, 23 Mar 2026 22:40:00 GMT vcampos@ortussolutions.com (Victor Campos) https://www.ortussolutions.com/blog/into-the-box-2026-goes-virtual-watch-on-demand-from-anywhere