4 ms·
most of us had experience with traditional development only, so we had to adopt devops mentality to be really effective, the company had ~4 system engineers who
by _shadi 8y ago
most of us had experience with traditional development only, so we had to adopt devops mentality to be really effective, the company had ~4 system engineers who were working on the monolith full-time, so we had to take care of the microservices we built ourselves.
by AWS services I meant things like cloudformation, packer, ansible, consul, the nitty-gritty of ELB, EC2, S3, docker, hardest part for me was IAM and vpc/subnets, dealing with multiple caches instead of a big one, also distributed sessions(in the end we got rid of sessions and used identifiers and a key-value store).
Jenkins jobs to deploy and test every single service on its own, and for deploying everything to a test environment and run integration tests.
UAT for testing all services on test environment.
There is much more than that but these are the things I remember from the top of my head.
- drbojingle 8y agoSounds pretty complex! What are you making if you don't mind me asking?
- _shadi 8y agoI'm no longer at that company, I would rather not share more personal information, but the product was a sort of a marketplace implementation.
- drbojingle 8y agoThat's cool, I'm not interested in personal info. I am curious how many developers were working on your back-end at any given time and how many services you had at any given time.