ProcessManager | multiplayer game about killing processes | Game Engine library

Essentially Im using the socketserver python library to try and handle communications from a central server to multiple raspberry pi4 and esp32 peripherals. Currently i have the socketserver running serve_forever, then the request handler calls a method from a processmanager class which starts a process that should handle the actual communication with the client.

It works fine if i use .join() on the process such that the processmanager method doesnt exit, but thats not how i would like it to run. Without .join() i get a broken pipe error as soon as the client communication process tries to send a message back to the client.

This is the process manager class, it gets defined in the main file and buildprocess is called through the request handler of the socketserver class:

I'm playing with the flink python datastream tutorial from the documentation: https://ci.apache.org/projects/flink/flink-docs-master/docs/dev/python/datastream_tutorial/

My environment is on Windows 10. java -version gives:

Please help in troubleshooting python3 logging from multiple processes into same log file. i have dameon main script, which runs in back ground, and calls few other pythons scripts every 15seconds, and each python script is written with same TimedRotatingFileHandler attributes, and all logs are written into same log file.

everything works fine, except log rotation.

I have been exploring Microservice Architecture, and even though the technologies I use are in Microsoft Domain, the question is generic.

I get the Idea of API Gateway esp for things like Authentication. The pattern I am roughly following is based on CQRS + Event Sourcing

Request-> Command ##CommandBus##->CommandHandler -> Change Aggregate State->Store Events-> PublishDomainEvents ->Publish Integration events ##Event Bus## -----> Update Read Models

Many times initial Command will be handled by ProcessManager (consumer) to Orchestrate workflow.

All Microservices Application Layer consume Command from Bus and work on changing Aggregate state. Once done, the Read model store is updated. Currently, there is only a single Read Database which is updated

When I started with Command Bus, The REST API per microservices were for mainly Get requests ( Read ), which would dip into the same Read Database as all other Services and rest for accepting Command from Gateway.

Based on my current Scenario, Is there a logic in having REST API's per Microservice? I know we can do Async with Rest API to push commands, but what is the point when I am already using a Bus.

But now I am thinking of not having API per Service but rather API's based on usage. It's then not limited to single Gateway but few Gateway API projects.

Are there any Cons/ pitfalls with this approach?

Edit 2-- **Trying to rephrase if it gives context ** My microservice structure is very similar (to what @mrdnk commented) . As you In I will introduce technology to make it more clear. I use Mass transit over RabbitMQ for inter service communication.

As of now I have API gateway used by client applications, which would then call appropriate microsservice API to push a command object. the API method itself acts as a Command Handler (acting as Application layer) calls Aggregate and make it undergo changes. Domain Events based on the change are published within the process with Mediatr. Any events that outside (microservice) world needs to know is published on the bus. I started to look at the communication and said to myself why not use the Bus also for commands (as command bus). That way I can have more reselient and async process.

Application layer will listen to command and handle appropriately. This way I feel the service is more encapsulated. On API side (individual microservce) I dont need to expose any rest api for use by gateway. API in Gateway wil listen to request and create command object. this will be queued to bus. Consumer (command handler) on Microservice will consume Command and so on.

Currently all Writes are eventsourced (mongodb). Reads go to SQL Server. I can create API just for Queries from Read side. No more need to have Http API from Microservice at all.

I know technically it would work but Dont know if there are any pitfalls.

Regards, Mar

I'm looking for advice on how to structure namespaces in a CQRS structured application.

Currently the command-side and the query-side are in the same namespace in each bounded context, but as complexity is growing, it is starting to create problems.

Currently the structure has the following folders which each contains the implementation:

problem java.lang.ClassCastException: java.lang.Object[] cannot be cast to android.content.Intent[]

code show as below： frida-js:

I got this error:

(I can give more info from inspector)

System.ComponentModel.Win32Exception: 'access denied'

The exception was originally generated in this call stack:

System.Diagnostics.ProcessManager.OpenProcess(int, int, bool)

System.Diagnostics.Process.GetProcessHandle(int, bool)

System.Diagnostics.Process.GetProcessTimes()

System.Diagnostics.Process.StartTime.get()

ConsoleApp1.Program.Main(string[]) on Program.cs

There is the code:

(I was running this program as administrator since the beginning)

The correct answer is how to ignore exceptions, because the error occurs because certain processes cannot be read even if you have administrator privileges

Problem

When I instantiate an instance of the Service class - derived from the ServiceBase class - the constructor I create for the Service class is skipped during instantiation. Then when the line "private ServiceController controller..." is hit, it fails because the ConfigStream object is never passed to the Service class variable _configstream. I don't have issues with constructors being skipped elsewhere in my code. Is this related to the use of the base class ServiceBase?

I've tried including the base class constructor like:

I have this map map> processmapram where the key is an integer and the value is the class object. This is how values are inserted to it.