ThoughtWorks engineers write about software delivery, microservices, BDD, design practice, and tools such as Talisman for catching secrets in commits.
HN links it for the NoPSD continuous design piece and the Talisman secret-scanning tool, and commenters bring up its microservices writing in discussions.
"And you know this rewrite, like others in the past, will be a significant sink of time, and likely a catastrophe."
This statement can only be true if you're using a very specific definition of "microservices". The first time I wrote about small services, in 2013 [1], I had not heard the phrase "microservices" so I used the phrase "an architecture of small apps". I was thinking of apps that talked to each via Redis, or HTTP, or didn't talk to each other and pushed everything into a database -- my idea was broad. Then in March of 2014, Martin Fowler wrote his essay on Microservices [2], which brought the phrase into widespread use. Soon after that there arose a number of startups that were promoting microservices, and they were promoting a very specific ideal: a system of apps that spoke to each other using HTTP, finding each other via auto-discovery, and offering data via a RESTful interface, with Oauth for authentication. A large number of people then began to use "microservices" for this specific set of interlocking ideas. That's fine, but it is a bit rigid. Something so comprehensive can demand a full re-write. But there is the more general idea, of slowly breaking up a monolith, and replacing small pieces with independent apps -- that does not demand a full re-write. That can be done slowly, and you have the option to keep the original monolith in a limited role, often to handle the frontend. Martin Fowler said all this in his essay, but some of the more extreme…
Here's a few:
- Walmart Labs - http://jobs.walmart.com/san-bruno/ecommerce/mobile-instore-software-(clojure)-engineer-jobs
- Staples - http://careers.staples.com/sanmateo/
- Climate Corp (now owned by Monsanto) - https://github.com/TheClimateCorporation
- RoomKey http://www.colinsteele.org/post/27929539434/60-000-growth-in-7-months-using-clojure-and-aws
- Puppet Labs - http://puppetlabs.com/blog/new-era-application-services-puppet-labs
- Soundcloud - http://blog.josephwilk.net/clojure/building-clojure-services-at-scale.html
- Netflix - https://speakerdeck.com/daveray/clojure-at-netflix
- eBay - https://www.linkedin.com/jobs2/view/26386571
- Two Sigma - https://www.youtube.com/watch?v=YHctJMUG8bI
- Consumer Reports - http://www.meetup.com/denofclojure/messages/boards/thread/47511532/
- LivingSocial - https://www.linkedin.com/jobs2/view/19995533
- Factual
- Thoughtworks - http://thoughtworks.github.io/p2/issue09/two-months-early/
- Daily Mail - http://www.pitheringabout.com/?p=1018
- MixRadio - http://dev.mixrad.io/blog/2014/10/19/Clojure-libraries/
- Prismatic - http://blog.getprismatic.com/blog/2013/1/14/bringing-functional-to-the-frontend-clojure-clojurescript-for-the-web
- Pivotal Labs - http://www.pivotaltracker.com/community/tracker-blog/generative-testing
- Beanstalk - http://blog.beanstalkapp.com/post/23998022427/beanstalk-clojure-love-and-20x-better-performance
- uSwitch
- CFPB (Credit Financial Protection Bureau) -…
Search your existing code for secrets. Review all your commits before pushing.
Some tools can help with that:
https://martinfowler.com/articles/session-secret.html
https://github.com/trufflesecurity/trufflehog
https://about.sourcegraph.com/blog/no-more-secrets
https://github.com/Yelp/detect-secrets
https://docs.github.com/en/developers/overview/secret-scanning-partner-program#joining-the-secret-scanning-program-on-github
https://github.com/godaddy/tartufo
https://github.com/GitGuardian/ggshield
https://github.com/awslabs/git-secrets
https://github.com/sirwart/secrets
https://thoughtworks.github.io/talisman/
https://gitleaks.io/
Not.
See the NoPSD movement: http://thoughtworks.github.io/p2/issue02/continuous-design/