Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Explore the idea of running this adaptor into its own container #1

Open
ddragosd opened this issue Sep 22, 2015 · 0 comments
Open

Explore the idea of running this adaptor into its own container #1

ddragosd opened this issue Sep 22, 2015 · 0 comments

Comments

@ddragosd
Copy link
Member

There are a few benefits when running the ZMQ adaptor into a separate container :

  • the apigateway container is smaller and it doesn't have to monitor an extra process
  • it's easier to update the implementation of the existing adaptor;
  • it allows other adaptors to be implemented; if we want to try a ZMQ adaptor using Go bindings we don't have to struggle which one makes it into the GW container
ddragosd added a commit that referenced this issue Sep 22, 2015
@ddragosd
#1 WIP: added a Dockerfile; also update the logging to print to stder…
ce89e1d 
…r messages during container startup. stdout prints messages according to its own buffer setting.
2mia pushed a commit to 2mia/api-gateway-zmq-adaptor that referenced this issue May 30, 2018
@mstefane
Add monitoring support (adobe-apiplatform#1)
3ce70c4 
* Add socket monitoring support

* Add support for more ZMQ events

* Prefix text messages with timestamp

* Ignore IDE files

* Disable stdout & stderr buffering; replace printf with fprintf

* Address code review comments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ddragosd