+1 954 414-4600 info@beesion.com

BSS Components Built with Microservices

Cloud-Native Applications Designed for Fast Change

Beesion builds low-code, cloud-native applications with microservices, or loosely coupled software components that perform specific business tasks. Each microservice is continuously developed and maintained independently. Added together, they compose the enterprise BSS application. The benefits of this decoupled strategy include:

  • Scalability -Smaller components take up fewer resources and can be scaled faster
  • Resiliency – If one component fails, the other parts of the solution are still available
  • Agility – Small teams work in parallel to build each component, shortening cycles
  • Maintainability – Developers can find faults easily and deploy fixes fast

Beesion or systems integrators build the microservices using cloud-native architecture to manage identity management, transaction coordination, service discovery and API mediation. This helps to simplify and shorten development.

Step 1
Map the Microservices

Determine which microservices are needed for the BSS solution, and how they’ll communicate with each other (User Interfaces, Messaging or APIs).

Plus, set up teams to construct each microservice.

Define all the microservices and establish their development teams

Step 2
Define the Technologies

Each microservice is built with the most optimal technology to execute its business task. The microservices developer has a wide range of choices and can select relational databases  – Oracle, Microsoft SQL Server, MySQL; non-relational databases – MongoDB, Elastic Search, Cassandra; and languages such as NodeJS, Java, C+, C#. The Beesion platform will then generate the code for each microservice in the selected technologies.

Select databases, APIs and technologies for each microservice

The microservices leverage well-known technologies to simplify the development cycle.

Open standards tools used for the development of each microservice

Step 3
Define Deployment Environments

The microservices team chooses the technologies, administrators, and management rules for each deployment environment. Plus, it sets up a clear, automated path to deploy microservices to each environment.









Step 4
Map the Data

Beesion has created its own graphical mapping tool, Blockie, to map and transform the data, housed in each microservice. The microservices database analyst uses this tool to transform data and even replicate it to other microservices.

Blockie eliminates many of the problems incurred with complex data mapping and transformation.

Map the data graphically with Blockie. View code generated (in black)

Step 5
Model the Business Logic

Each microservice has its own business logic.  The microservices business analyst uses the business rules editor (Blockie), business process management (BPM)  and business procedural logic editor to create the business logic. He/she also creates the workflows.

Business logic is built with Blockie

Workflows are built graphically, too.

Step 6
Model the Screens

For each microservice, the microservices UX expert determines the layouts, styles, and look and feel for every screen. He/She also creates responsive designs, tablet, desktop, laptop, using the UI editor. Reports are also constructed.

Step 7
Test and Validate the Solution

Because microservice development is done in parallel, release times are significantly shorter than monolithic development. The focus: continuous delivery.

Less dependencies. Business functions are built in parallel, reducing complexity.

Step 8
Deploy Into Production

Revise each microservice as needed, without disrupting the others. Plus push incremental changes into production much faster.

New microservice to replace existing one

Follow us: