Key Concepts

Main > Key Concepts

A small group of core concepts balances the many aspects dealt by Liquid and determines its general shape and strengths.

#Architectural Strategies

• Platform abstraction layer: using the best from PaaS offerings yet avoiding vendor lock-in;

• Leveling up platform providers: ensuring top functionality in the market even if a particular vendor has not yet reached the level of the others;

• Business logic separation: avoiding mixing domain (business) logic along with underlying platform (technical) logic;

• DevOps for microservices: giving this fine-grained unit of software an easier way of being built, deployed and tested in a continuous fashion.

#Prescriptive Programming Model

• REST APIs as (formal) object models: leveraging the abstraction and formality of a well-formed REST API as a way to avoid code redundancy and error propensity;

• Encapsulated domain (business) logic: putting domain logic in a format (of classes) independent of the protocols used to access it;

• Business error handling: defining a simple yet comprehensive way of dealing with business logic deviation;

• Microservice sizing: giving shape to the various parameters of a well-designed microservice.