The overall Flipt server architecture is shown in this diagram:
Arrows indicate request or connection initiation direction, not necessarily dataflow direction.
As shown in the above diagram, the Flipt application is made up of three main components:
- Flipt Backend Service
- Flipt REST API
- Flipt Web UI
All three of these components run side by side in a single binary. The UI and REST API are served on the same port (
8080 by default) and the GRPC Backend Service is served on
9000 by default.
The Flipt Backend Service is the main entrypoint to the application and implements all of the business logic for Flipt. This is what users of the gRPC client SDKs will communicate with, allowing for fast, efficient communication with your applications.
The Flipt REST API is implemented on top of the Backend Service using gRPC Gateway (described below).
The REST API is served under
/api/v1 and allows all actions that the client SDKs allow.
A guide to using the UI for the first time can be found in the Getting Started documentation.
Flipt is built using several amazing open source technologies including:
A brief description of why each technology was chosen is below.
From the Go documentation:
Go makes it easy to build simple, reliable and efficient software.
These are all goals that Flipt also aspires to. Flipt was written in Go mainly because of it's ability to produce bulletproof systems software as as single binary for multiple architectures.
This allows Flipt to easily be deployed in almost any environment since it's as simple as copying a compiled binary.
gRPC is a high performance, open source RPC framework created by Google. gRPC allows Flipt to be performant by eliminating much of the overhead incurred by using standard HTTP for communication.
gRPC also has the benefit of being able to generate client SDKs in many different languages from a single Protobuf file.
This allows you easily integrate your services with Flipt regardless of the language they are written in.
While awesome, gRPC might not be for everyone. gRPC Gateway is a reverse-proxy server which translates a RESTful JSON API into gRPC. This allows Flipt to implement a REST API as well as the gRPC API described above.
This means that the REST API follows the same codepaths as the gRPC service that Flipt implements, allowing for reduced bugs and a simpler architecture.
The Flipt UI is also built on top of the REST API provided by gRPC gateway.
From the SQLite documentation:
SQLite is a C-language library that implements a small, fast, self-contained, high-reliability, full-featured, SQL database engine. SQLite is the most used database engine in the world.
Two of the major goals of Flipt are to be 1) Fast and 2) Self contained. SQLite allows us to accomplish both. By embedding the datastore 'within' the application, we eliminate the need to communicate to an external database. This results in faster performance with is required if putting calls to Flipt in the 'hotpath' of your applications.
Using SQLite means that you do not need to run an additional client/server RDBMS such as Postgres or MySQL in order for Flipt to store and retrieve your data. This means it's easy to get up and running with Flipt without having to install any additional software.
And since a SQLite database is just a file, you can easily backup your data using traditional file backup methods.
Bulma is a free, open source CSS framework based on Flexbox. It makes it easy to create nice looking user interfaces with minimal CSS.
Buefy creates lightweight UI components for Vue.js based on Bulma. The Flipt UI was built using several Buefy components that greatly enhanced the speed of development.