ES

Microservice Architecture

SNGULAR builds microservice architecture based on the distributed services that overlay our customers' core systems

Our solutions

Built on containers, they allow for the continuous deployment of complex corporate solutions while facilitating the development and innovation of an organization’s technological base.

The underlying principles shared by our architecture include:

  • Capabilities exposed as APIs and deployed in containers.

    We will create different APIs for different purposes.

  • Use of container orchestration

    Kubernetes, OpenShift.

  • Use of event/sourcing when possible

    Kafka.

  • Channel orientation

    To respect the specific nature of each channel.

  • Platform

    Orientation to platform capabilities.

  • Vendor lock-in.

    Avoiding vendor lock-in.

  • Use of API Gateway to publish, secure, and control API calls between the different solution layers

    Use of service mesh model for internal APIs.

  • Compliance with security regulations through standards and best practices

    API access management, OAuth2, JWT, data encryption, etc.

  • Operations

    Logging, monitoring, and monetization.

  • Strategy & Stack

    Respecting corporate strategy and technology stack.

Main architecture elements

  • Channels

    The points of interaction with users. Although the most common are web channels (a computer, tablet, or smartphone) and native apps, we also consider other interaction points like smart speakers or wearable devices. To adapt the user experience to the channel, it is necessary to review and customize the different domains' APIs and the data that the interface requires.

  • API Gateway/Manager

    The single point of entry for all the elements that access the system to consume or publish information. The API Gateway will determine how applications interact with the APIs through access policies. The API Manager distributes, controls, and analyzes the APIs that connect applications and data sources/destinations.

  • Domains

    Where the capabilities of the APIs are gathered. This is the central part of the architecture since it provides access for applications to use the different business competencies uniformly, while also simplifying the integrations and access to systems.

  • Internal APIs

    The layer that insulates the domain from the complexity of integration with different systems and elements of the organization. This layer provides integration capabilities by overlaying backend or legacy systems that are difficult to adapt or evolve.

  • Backend

    The backend represents the systems park that the organization uses to secure its operations. It also includes all the persistent data that solidifies the organization's information. In today's competitive environment, a corporate backend can be made up of custom developments, on-premise, PaaS or SaaS, with multiple security schemes and different integration protocols (API REST, SOAP, message queues, even file exchange with comma-separated values). 

     

© Copyright - Sngular 2021

facebook youtube instagram twitter linkedin