4 ms·
You're 100% right about discipline. I work for a very undisciplined and border-line incompetent company that decided to roll out a microservices architecture, c
by blackbeard 11y ago
You're 100% right about discipline. I work for a very undisciplined and border-line incompetent company that decided to roll out a microservices architecture, continuous delivery and devops culture into a behemoth enterprise product. This has simply been a disaster because the incumbent methodology has been hack it until it mostly works.
However, with respect to technology, some technologies do not lend themselves to these processes. .Net I'm looking at you here; you're a tangled build nightmare, a deployment clusterfuck, require too many resources to lift light tasks and most of your core as API is a mess of obsolete ideas,impossible to test abstractions and a bunch of dubious hand grenades (ReaderWriterLockSlim for example which has deadlocked on me numerous times and is the basis for concurrent collections).
- rjbwork 11y agoWe do just fine w/ DevOps on .NET. We auto build on push, publish a versioned Octopus Deploy package to our TC NuGet feed,and deploy to our dev environment many times every day. We haven't had to actually touch our build/deployment process in over 4 months, except to click the single button to move from environment to environment. It really is fantastic.
- blackbeard 11y agoThat works for simple deployments but when you start having to deal with signing, licensed components and stuff like ours (55 deployable packages) then it gets hairy. Also managing windows infrastructure is hell.
- rjbwork 11y agoFair, though we've got a few things now. We're all on azure and all our stuff is @ platform level, and built to throw away, so it's a bit different.
- blackbeard 11y agoOk you're lucky to be on Azure PaaS!