3 ms·

no why? The task of the Microservice is to convert the pdf to stardust and to return it to its sender. so no auth. Furthermore its most likely only reachable t

no why? The task of the Microservice is to convert the pdf to stardust and to return it to its sender. so no auth. Furthermore its most likely only reachable through the local network, or at least should be if you want some stranger not to be able to also make stardust from pdfs. Monitoring: are you trying to say that its a lot esaier to pick up one logfile thant lets say 15? because they should be aggregated somewhere anyway no? Deployment: Depending on anything you listed how do i do anything? Of course if have to define it but if you want a fancy example: k8s argocd canary deployments done. I literally set it up once. security? Really? Please dont get this wrong but this feels to me like whataboutism but well here i go: i implement security just the same way as i would in the monorepo. The thing/person/entity just has to look into more repositories ;) It comes down do one sentence i think: State is not shared, state is communicated.

comradesmith 5y ago
For monitoring I’d also say the alerting side of things can be done via the older monolith. That is, catch exceptions and log/re-raise them as “PdfServiceException”.
rich_sasha 5y ago
A microservice runs as some (somewhat) privileged user, you may want some auth. Can everyone internally create sales tickets? Or can everyone just query them? If a team provides a library to run, and you run it, you still only run as whatever user you have access to. Monitoring: it's easier to look at a stack trace, including some other team's external library, than a HTTP error code 500. Deployment is certainly easier when you're just shipping code and a build. You don't have to faff around with the previous instance running, maybe having some active connections/transactions/whatever, needing to launch a new one. Maybe it's not hard overall, but less fun.
- matwood 5y ago
  > A microservice runs as some (somewhat) privileged user, you may want some auth. Auth can be a very broad term in the case of services, especially in the cloud. IAM could only allow access from certain other machines, etc...

comradesmith 5y ago

For monitoring I’d also say the alerting side of things can be done via the older monolith. That is, catch exceptions and log/re-raise them as “PdfServiceException”.

rich_sasha 5y ago

A microservice runs as some (somewhat) privileged user, you may want some auth. Can everyone internally create sales tickets? Or can everyone just query them? If a team provides a library to run, and you run it, you still only run as whatever user you have access to. Monitoring: it's easier to look at a stack trace, including some other team's external library, than a HTTP error code 500. Deployment is certainly easier when you're just shipping code and a build. You don't have to faff around with the previous instance running, maybe having some active connections/transactions/whatever, needing to launch a new one. Maybe it's not hard overall, but less fun.

matwood 5y ago
> A microservice runs as some (somewhat) privileged user, you may want some auth. Auth can be a very broad term in the case of services, especially in the cloud. IAM could only allow access from certain other machines, etc...