Posts

Showing posts with the label MACH Architecture

Multi-Agentic AI deployment with ADK (Agent Development Kit) and MCP (Model Context Protocol) - [Meridian Platform]

Image
Overview Meridian Lite is a purpose-built demonstration of multi-agentic AI capabilities, deployed in the context of UK mergers and acquisitions intelligence. It coordinates a hierarchy of six AI specialists — each with distinct tools and domain expertise — to evaluate acquisition targets, assess market dynamics, and synthesise deal recommendations from private in-house and live public data. The Lite designation is deliberate. This build strips away third-party data overhead and SaaS complexity, isolating the core agentic patterns — specialist  agent orchestration  routing, function tool-calling, session state sharing ,  and resilient failover — in a form that is legible, testable, and safe to demonstrate. The underlying infrastructure is production-grade:  hardened access control , security, token budgeting, and session persistence. The data coverage is intentionally constrained. Objectives - Multi-agent orchestration with intelligent specialist routing:   a ro...

Securing Network Traffic with Anthos (Istio) Service Mesh

Image
  Overview Anthos Service Mesh's security features are designed to prevent unauthorized access and data breaches by ensuring that all communication between workloads is securely authenticated and encrypted, thereby mitigating the risks posed by insiders. A specific method called PERMISSIVE mode mTLS (a type of mutual authentication in which two parties in a connection authenticate each other using the TLS protocol) is used to enable mutual authentication between services, which means that plaintext (unencrypted information pending input into encryption algorithms) and mTLS traffic can both be accepted from clients. This allows for a gradual adoption of mTLS. To enhance security further, STRICT mode mTLS is enabled across our service mesh, which ensures that only mTLS traffic is allowed to access Istio-injected services.  Here's an example configuration we explore that demonstrates the authentication options available through Istio. Objectives Enforcing a higher level of securi...

Migrating a Monolithic Web Application to Microservices (MACH Architecture) on Kubernetes Engine (GKE)

Image
Overview In this session we explore the advantages and disadvantages of migrating from a monolithic application to a microservices (MACH) architecture. Microservices offer benefits such as being able to independently test and deploy, implementing different technologies, and being managed by different teams. Microservices can also be designed for failure more easily, and Kubernetes is a platform that facilitates managing, hosting, scaling, and deploying containers, which are well-suited to the microservices pattern. However, microservices can lead to increased system complexity, security concerns, performance issues due to latencies, and difficulty in observing system behaviour. A monolithic application is a single, self-contained unit whereas microservices are a network of different services that interact in ways that may not be immediately apparent. As a result, understanding how the system behaves in production can be challenging. Istio is a solution that can be used to address some ...