Tidbits | A place to put random things

Given I have two microservices: Service A and Service B.

Service A owns full customer data and Service B requires a small subset of this data (which it gets from Service A through some bulk load say).

Both services store customers in their own database.

If service B then needs to interact with service A say to get additional data (e.g. GET /customers/{id}) it clearly needs a unique identifier that is shared between the two services.

Because the ids are GUIDs I could simply use the PK from Service A when creating the record in Service B. So both PKs match.

However this sounds extremely fragile. One option is to store the 'external Id' (or 'source id') as a separate field in Service B, and use that to interact with Service A. And probably this is a string as one day it may not be a GUID.

Is there a 'best practice' around this?

update

So I've done some more research and found a few related discussions:

Should you expose a primary key in REST API URLs?

Is it a bad practice to expose the database ID to the client in your REST API?

Slugs as Primary Keys

conclusion

I think my idea of trying to keep both Primary Keys for Customer the same across Service A and B was just wrong. This is because:

1. Clearly PKs are service implementation specific, so they may be totally incompatible e.g. UUID vs auto-incremented INT.
2. Even if you can guarantee compatibility, although the two entities both happen to be called 'Customer' they are effectively two (potentially very different) concepts and both Service A and Service B both 'own' their own 'Customer' record. What you may want to do though is synchronise some Customer data across those services.

So I now think that either service can expose customer data via its own unique id (in my case the PK GUID) and if one service needs to obtain additional customer data from another service it must store the other service identifier/key and uses that. So essentially back to my 'external id' or 'source id' idea but perhaps more specific as 'service B id'.

I'm trying to create a MQTT client that'll connect to the Google Cloud IoT Core, but for some reason, it won't connect at all. Here's what I have so far

I used ask init --hosted-skill-id= to pull a local copy of my skill. Running git remote -v shows the repository is hosted on AWS CodeCommit at https://git-codecommit.us-east-1.amazonaws.com/v1/repos/.

I can't see the CodeCommit repository in my AWS account (when logged in as root user). I also can't see any IAM roles listed in my AWS account. I considered logging in as the ask_cli_default profile generated by ask configure but it only has an access key and secret; no password.

Which AWS account holds the Alexa-hosted CodeCommit repositories? Is there any way to grant access to another account?

Other potentially relevant tidbits

• Context: Yesterday I created a skill in the Alexa developer console based on a Hello World template. Now I want to share it with a friend so we can develop it together. Ideally we would both be able to push to a shared git repository, build, deploy, and test using the simulator in Alexa developer console.
• ask --version = 2.20.0
• I can git clone to another local directory using the (generated) username and password from ask util git-credentials-helper.
• a question in the AWS forums Alexa Hosted sets up a CodeCommit repository -- unanswered
• official AWS docs for setting up cross-account access to CodeCommit -- Requires access to the CodeCommit repository from AWS console. This is where I want to get to.

I'm trying to add a column to a production hours dataset that will tell if a provider who worked last week was also working three weeks earlier. The current dataset looks something like this:

I am currently trying to use Log4Net to insert logs into a MS SQL Server DB. I believe I have Log4Net at least working because I was able to use the FileAppender option/example given Here and I was able to generate a file with the stack traces. However, 8 hours of research and tutorials has me totally stomped on getting the MS SQL Server config examples given Here - same place to work.

I cannot get even their example to work. I created the table, I updated my log4net.config file from the FileAppender option to the provided MS SQL Server option and I fed it the correct connection string settings and... nothing.

I am going to post the code tidbits I believe will be helpful and a photo of proof that my DB table does exist.

CONFIG FILE

I am building a typing.NamedTuple class (see typing.NamedTuple docs here, or the older collections.namedtuples docs it inherits from) that can accept different ways of being initialized.

Why NamedTuple in this case? I want it to be immutable and auto-hashable so it can be a dictionary key, and I don't have to write the hash function.

I understand that I need to use __new__ rather than __init__ due to NamedTuples being immutable (for example, see this Q&A. I've searched and there are some tidbits out there (e.g. answers to this question on setting up a custom hash for a namedtuple), but I can't get everything working, I'm getting an error about not being able to overwrite __new__.

Here's my current code:

Edited with additional details added

I have a shapefile of 2,061 Open Street Map (OSM) road segments. Each segment in my shapefile is is identified by its OSM Way ID.

Here is an example of five segments from my data:

I have a dataset that looks like this (the Groceries dataset from the arules CRAN package)

libraries:

I have a bar chart that I'd like to:

1) On click, the selected bar changes color [The code I have works]

2) The circle div changes color based on the bar's height [I can't seem to add that to the code above]

I know