Digota - ecommerce microservice
Digota is ecommerce microservice built to be the modern standard for ecommerce systems.It is based on grpc,protocol-buffers and http2 provides clean, powerful and secured RPC interface.
Our Goal is to provide the best technology that covers most of the ecommerce flows, just focus of your business logic and not on the ecommerce logic.
TLDR; scalable ecommerce microservice.
Join our community at gitter !
Getting started
Prerequisites
- Go > 1.8
- Database
- mongodb > 3.2
- redis (TBD)
- postgresql (TBD - #2)
- Lock server (default is in-memory locker)
- zookeeper
- redis !! (thanks @Gerifield)
- etcd (TBD - #3)
Installation
From source
$ go get -u github.com/digota/digota
From docker hub
$ docker pull digota/digota:0.1
Run
$ docker run digota/digota:0.1
Or with flags
$ docker run digota/digota:0.1 bash -c "digota --version"
Check out this docker-compose for more details.
Flags:
--info Set log level to info
--debug Set log level to debug
--help, -h show help
--version, -v print the version
Cross languages
Key benefit of using grpc is the native support of major languages (C++
,Java
,Python
,Go
,Ruby
,Node.js
,C#
,Objective-C
,Android Java
and PHP
).
Learn How to compile your client right here, You can use you Makefile
as well.
Complied clients:
Flexible payment gateways
It does not matter which payment gateway you are using, it is just matter of config to register it.
Supported gateways for now:
- Stripe
- Braintree
Are you payment provider ?
Just implement the following interface and PR you changes.
Auth & Security
We take security very seriously, don't hesitate to report a security issue.
Digota is fully Encrypted (end-to-end) using TLS, That fact is leveraged also to Authenticate Clients based on their Certificate in front of the Local Certificate Authority.
Basically we are creating CA and signing any certificate we want to approve with same CA.
How about revoking certificate? The CRL approch here is whitelist instead of blacklist, just remove client serial from your config.
Create CA
$ certstrap init --common-name "ca.company.com"
Create Client Certificate
$ certstrap request-cert --domain client.company.com
Sign Certificate
$ certstrap sign --CA "ca.company.com" client.company.com
Approve Certificate
Take the certificate serial and Append the serial and scopes(WRITE
,READ
,WILDCARD
) to your config
$ openssl x509 -in out/client.com.crt -serial