redpesk® microservices architecture
- Services are like applications
- Applications and services are running isolated one another by their security context
- The communication between applications is controlled by policy (framework, firewall, gateway, OAuth, OpenID Connect)
- Access to service features is controlled by permission enforcement mechanism (Cynagora, OAuth, Barier token)
- Microservices can be written in multiple languages: C/C++, Python, Lua, NodeJS, Rust
The Binder
- Enforcing policy and permissions
- Linking services together
- Connection transport
- - HTTP and HTTPS
- - WebSocket (WS and WSS)
- - DBUS
- - AFB protocols
- - Coming soon SOME/IP
- Integration JSON and FLATBUFFER
Key benefits
- No licence tainting
- HW vendor / Tiers 1 / Cloud provider independence
- Several actors can develop simultaneously several services
- Cloud & edge ubiquity
- Openness to others worlds (Autosar, Zephyr, Android…)
- Monitoring & auditability
- Native development enablement
- Allows developers to focus on their own business logic
