carapace

README

carapace

Reusable, core functionality for building microservices.

Definition: a bony or chitinous case or shield covering the back or part of the back of an animal (such as a turtle or crab).

Description: A learning project to build the components of a microservice that are often covered handled 'under the hood' in Java by frameworks such as Spring Cloud or Micronaut.

• Like those projects, the intent is to make a reusable library for other projects down the line.
• As the name suggests, there is a slant toward security and overall service hardening, ie, an exoskeleton that can house and provide functionality to any operational/business logic.

Language Choice: I chose Go because it is like the 'Sport Mode' version of an automatic transmission. You get a lot of the same control you get with a stick shift, but the standard library is really robust so there is a lot that (in security) is easy to to mess up and difficult to implement successfully.

• The secondary challenge of the learning project is to use as few 3rd party libraries as possible and over time get rid of all of them.

Library Components (thus far):

1. Health endpoint
2. mTLS Server
3. mTLS Client
4. SQL connection
   • Maria DB
   • Included because a distributed service will need to persist security artifacts like session tokens, access tokens, csrf tokens, etc.
5. ECDSA Certificate Generation
   • CAs
   • Leaf
6. Field level encryption for sensitive service data using AES GCM 256.
7. Service to Service login credential validation.
8. Jwt Mint:
   • signs
   • verifies
9. Service to Service http call templates
   • Adds service and user tokens if exists
   • deserializes json response or error