chatie / io

Chatie Cloud Input/Output Service

Chatie IO

Image Credit: https://switchon.io/

Cloud IO for Chatie.

This module is a component of the Chatie service.

Links

• The Objective-C Programming Language - Selectors
• Objective-C Succinctly: Methods - Selectors
• JSON-RPC 2.0 Specification
• Getting Started with Redux, tutorial video made by it's creator Dan Abramov
• Making redux-inspired backend real
• Simple service bus for sending events between processes using amqp
• Lessons Learned Building Distributed Systems with CQRS and Event Sourcing - Patrick Lee Scott
• The unfinished guide to Event-Sourcing, CQRS and DDD [Unreleased, RAW] + notes about Uber
• Learning these 5 microservice patterns will make you a better engineer
• Complicated patterns aren’t always that complicated. Usually it’s the simple ones that bite you.
• Talk Video: Matt Walters - How to CQRS in Node: Eventually Consistent, Unidirectional Systems with Microservices
• CQRS + Event Sourcing – Step by Step
• Talk Video: GOTO 2015 • DDD & Microservices: At Last, Some Boundaries! • Eric Evans
• Talk Video: GOTO 2014 • Event Sourcing • Greg Young
• gRPC Wait for Ready Semantics

Json RPC

• node-json-rpc - A simple and lightweight NodeJs JSON-RPC 2.0 implementation including object wrapping
• json-rpc-protocol - JSON-RPC 2 protocol messages parsing and formatting
• HOW I SOLVED THE PERFORMANCE NIGHTMARE (RXJS, JSON-RPC AND MORE)

Service Discovery

• DNS Service record (SRV record)
• Open-Source Service Discovery

Related Projects

• reSolve - Full stack CQRS, DDD, Event Sourcing framework for Node.js

Event Driven Architecture

• Programming Without a Call Stack – Event-driven Architectures, @Gregor Hohpe, 2006

History

master v0.9

1. Discovery puppet service schema rename: ip to host. (ip will be kept for compatible before Dec 31, 2022)

v0.8

Fix chatie/server#49: Refactoring the sockets management system

1. Remove Listag module due to memory leaks

v0.7 (2019)

Useable version

v0.1 (May 2017)

Init version

Author

Huan LI (李卓桓) [email protected]

Copyright & License

• Code & Docs © 2017-now Huan LI (李卓桓) <[email protected]>
• Code released under the Apache-2.0 License
• Docs released under Creative Commons

io's Issues

Test host/port connection: set host as `127.0.0.1` if not

To make the local token easy to use:

When a user runs wechaty gateway on a server that can not be visited from the internet, we set the host to 127.0.0.1 for them to be easily connected to their private service on localhost.

Keep service discovery information after the websocket disconnect for a while

If a Puppet Service Server is restarting, the WebSocket connection to the io will be lost for a while.

We should keep the old information available for a period of time, so that:

1. It will be able to be discovered between the restarting of the service server,
2. It will timeout after a period of time.

The exact timeout number needs to be investigated. (we can refer to the configuration of etcd or zookeeper)

CC @windmemory

Remove listag to prevent memory leak

Refer to Chatie/server#49

Puppet WXWork Service unreachable

Interesting find out:

https://api.chatie.io/v0/hosties/puppet_wxwork_xxx

{"host":"127.0.0.1","ip":"x.y.217.105","port":8788}

It seems that the service discovery thinks that the Puppet Service Service IP is not public accessible.

Related source code:

io/src/server/io-manager.ts

Lines 362 to 375 in 17c715f

	/**
	* Huan(202201): test whether the puppet service server host/port
	* can be visited by the internet
	*/
	const isReachable = await isPortReachable(port, {
	host,
	timeout: 5 * 1000,
	})
	const data = {
	host: isReachable ? host : '127.0.0.1',
	ip: host, // <- `ip` is deprecated, use `host` instead. Will be removed after Dec 31, 2022 Huan(202108)
	port,
	}

Originally posted by @huan in Chatie/server#96 (comment)