github.com/GameWorkstore/async-network-engine

Async Network Engine

Application Http requests made easy to interoperability with Go Lang Backend + Google Protobuf functions!

Supported Cloud Functions:

• Google Cloud Functions
• Amazon Web Services Lambdas

Use at your own risk!

CppSDK

Visit this repo for more info: https://github.com/GameWorkstore/async-network-engine-cpp

GoLangSDK

Visit this repo for more info: https://github.com/GameWorkstore/async-network-engine-go

UnitySDK

How to install

At package.json, add these 3 lines of code:

"com.gameworkstore.asyncnetworkengine": "https://github.com/GameWorkstore/async-network-engine.git#0.2.4",
"com.gameworkstore.googleprotobufunity": "https://github.com/GameWorkstore/google-protobuf-unity.git#3.15.2012",
"com.gameworkstore.patterns": "https://github.com/GameWorkstore/patterns.git#1.2.0"

And wait for unity to download and compile the package.

or update package for a newer version, update end of line from 0.2.1 to any released version on Releases.

Usage Examples

You can find usage examples on Assets/Tests/ folder, for each cloud.

FAQ

Uploading to Google Cloud Functions

on upmsync, the job 'upload_gcp' illustrates a possible way to upload your functions into GCP. Requires a service account to enable it to upload.

Uploading to Amazon Web Services

on upmsync.yaml, the job 'upload_aws' illustrates a possible way to upload your functions into AWS. Requires a service account to enable it to upload.

You need to set the template 'cloudformation_function.yaml' public in your bucket repository to enable AWS::Stack to read from it.

GCP Troubleshoot

My function is returning ErrorProtocol for any input. if you don't give access public for your function it might fail

AWS Troubleshoot

CloudFormation is returning errors

Verify all variables, !Ref and links, you might be forgetting something. CloudFormations is very sensitive to linkage errors.

My lambda is returning error 500 Internal Server error.

If you are receiving this and error object is returning null, it might be a bad configuration causing your lambda to not run. Verify if you function is running by adding a fmt.Println("test") at main() function to ensure the function is starting. Some issues that may prevent the start of function:

• The functions ins't at correct path when extracted from the zip.
• The function package name isn't main where main() function is declared.
• lambda.Start() is never begin called to initialize the function.
• The function is crashing upon initialization

If the function is working normally, them you might receive error 500 - ErrorInternalServer with AWSError, when specified by the programmer.

Contributions

If you are using this library and want to submit a change, go ahead! Overall, this project accepts contributions if:

• Is a bug fix;
• Or, is a generalization of a well-known issue;
• Or is performance improvement;
• Or is an improvement to already supported feature.

Also, you can donate to allow us to drink coffee while we improve it for you!