The team is happy to announce the official release of CrowdSec v.1.0 which introduces several improvements to the previous version, including a major architectural change: the introduction of a local REST API.
This local API allows all components to communicate together in a more efficient way, supporting more complex architectures, while keeping it simple for mono-machines users. It also makes the creation of bouncers (the remediation component) much simpler and renders them more resilient to upcoming changes, limiting the necessary maintenance time.
New architecture
In the new 1.0 release, the CrowdSec architecture has been deeply remodeled:
All CrowdSec components (the agent reading logs, cscli for humans, and bouncers to deter the bad guys) can now communicate together via a REST API, instead of reading or writing directly in the database. With this new version, only the local API service will interact with the database (supports SQLite, PostgreSQL and MySQL).
What it brings to the table
The benefits of having a REST API for bouncers are major:
- Bouncers become truly stateless, making it possible to build new ones for serverless/lambda environments
- Future changes in DB schemas won’t impact bouncers, and API versioning ensures smooth control over this
- Bouncer implementation becomes really quick and easy: just one HTTP GET request with an API token is needed
Much more details about this new release benefits can be found in the product announcement here.
We would love to hear your feedback about this latest release. If you are interested in testing the software or would like to get in touch with the team, here are a few useful links:
Hope to hear from you soon!
The CrowdSec team
Top comments (0)