4 ms·
You'll know your architecture is complex enough when diagrams of it land you a big raise at a new company. Until then you need more services.
by wmil 3y ago
You'll know your architecture is complex enough when diagrams of it land you a big raise at a new company.
Until then you need more services.
- karim79 3y agoDon't forget that component/service names will need to be suitably enterprisified like so, for professionalism: InterceptorWatcherCollectionClientDefinitionIteratorBroadcasterBasedObserver I always use this tool when I feel that the stuff I'm churning out is substandard: - https://projects.haykranen.nl/java/ https://projects.haykranen.nl/java/
- rqtwteye 3y agoHere is a tutorial for correct naming: https://www.youtube.com/watch?v=y8OnoxKotPQ https://www.youtube.com/watch?v=y8OnoxKotPQ
- karim79 3y agoVery informative. I only have one small gripe: I find that the 'Papaya' naming is somewhat unspecific, and somewhat ambiguous. I would have called it 'Wombat' for clarity, but overall I think these guys know what they're doing.
- _f5ah 3y agoThere is a class `ParameterizedAutoFactoryFactoryFactory`[1] in one of my pet projects. The name does correctly reflect the purpose of this class. Although I could of course have come up with another one, the temptation of `Factory`x3 was just too strong to resist. [1]: https://github.com/mykolav/unitycontainer-param-autofactory/blob/master/ParameterizedAutoFactory.Core/ParameterizedAutoFactoryFactoryFactory.cs https://github.com/mykolav/unitycontainer-param-autofactory/...
- Buttons840 3y agoParameterizedAutoFactoryCubed
- myk9001 3y agoPower types: to multiply your effectiveness on those days when product and sum types just don't add up.
- karim79 3y agoThat's even more inspired than RequestSpecificProcessorFactoryFactory from org.apache.xmlrpc.server: https://ws.apache.org/xmlrpc/apidocs/org/apache/xmlrpc/server/RequestProcessorFactoryFactory.RequestSpecificProcessorFactoryFactory.html https://ws.apache.org/xmlrpc/apidocs/org/apache/xmlrpc/serve...
- deleted 3y ago[deleted]
- jiggawatts 3y agoI was asked to review a multi-cloud architecture proposing to add several code repositories, multiple cross-cloud ETL pipelines, scalable big-data clusters, several and web and API apps -- with API management, of course! Some, but not all of that, was to be hosted on multiple Kubernetes clusters. All of that for a project being implemented by one developer to generate one report. My alternative solution was adding a single index and a PowerBI connector to the existing database. They didn't like that and went with the original approach. I didn't hear back.