4 ms·
Would this be easier if you needed to integrate with user-provider-service, timestamp-conversion-service, image-storage-service (which also stores videos these
by jeroenhd 4y ago
Would this be easier if you needed to integrate with user-provider-service, timestamp-conversion-service, image-storage-service (which also stores videos these days, though HEIFF and h.265 has obviously been moved to iOS-image-storage-service so customers can be billed for the special software that requires patents) to upload a signed SecuredApplicationPackage file to InternalExternalSoftwareManager so that it can be included in the application_distributor next time ReleaseMgr decides to update its endpoints?
What, you forgot to integrate with the SecondaryDataValidationService? How is it supposed to work without SecondaryDataValidationService? Are you even a real programmer?
God forbid you use the old DataValidationService or ReplacementDataValidationService, those have been deprecated for years. And you don't want to make a fool of yourself by using ImageStore instead of image-storage-service, ImageStore is clearly for operating system images not pictures! And what are you doing touching IntermediateDataLayer? That's only for enterprise customers, shouldn't that be obvious? It'd like adding a dependency to CachingLayerV2 to a ServerSideSoftware deployment package, simply ridiculous!
If you have a forest of microservices to browse through, it doesn't matter if they're named after pokemon or if some engineer came up with a descriptive name. You need a guide either way, because half of the services that sound like they may be relevant do something completely irrelevant or have been put in maintenance only mode years ago anyway.
- xeyownt 4y agoCouldn't have said it better. Overall, common sense should be the rule, not "always descriptive / always cute".
- beckingz 4y agoThe thing about common sense is that sense isn't common. Also, more accurately, the environmental information used for our common sense naming changes out from under us.
- Draiken 4y agoNot only that, but half of those services would become acronyms very quickly. Would this be easier if you needed to integrate with UPS, TCS, ISS (which also stores videos these days, though HEIFF and h.265 has obviously been moved to iOS-ISS so customers can be billed for the special software that requires patents) to upload a signed SAP file to IESM so that it can be included in the AD next time RM decides to update its endpoints?
- danparsonson 4y agoYes that would absolutely be easier - I don't understand why this is controversial? If you have a bunch of services, some of which are relevant, some are not, and domain knowledge is required to understand which to use at which times, then that problem exists independently of their names, as you say. Naming them after Pokemon obviously makes it more difficult to learn which is which; how can it not? Do you really think that user-provider-service, timestamp-conversion-service, image-storage-service is no easier to follow than bulbasaur, charmander, squirtle ? After ten minutes of 'eevee depends on charizard, which in turn requires mewtwo' I would be utterly lost.