GIDS is the gold standard conference and expo for the software practitioner ecosystem. 72,240 attendees have benefited from the platform since its founding in 2008. An essential destination for developers, architects & senior technologists, the event is five-day whirlwind of enlightening and inspiring talks by global experts, full-day workshops, exhibitions, networking and community. Several thousands have testified to the success they owe to GIDS - from individuals who turned entrepreneurs, to garage start-ups who metamorphosed into full-fledged global operations, to several thousands who have reported super positive career upgrades and shifts. Visit: www.developersummit.com
I'm working on a Django + React project, and we use GitHub Actions for CI/CD. The typical workflow when a pull request is raised involves running Selenium tests, which require a large dataset in the database to execute effectively. Once the tests pass, I merge the branch, triggering an AWS CodePipeline that goes through source, manual approval, and deployment stages. The problem I'm facing is related to database migrations when multiple developers raise pull requests simultaneously. If I run the workflows in parallel, I end up with migration conflicts that cause issues down the road. However, if I run the workflows sequentially, the deployment process gets delayed, especially when there are several pull requests in the queue. Current Setup: GitHub Actions: Runs on pull requests, runs Selenium tests, and applies migrations to a testing database. AWS CodePipeline: After tests pass and PR is merged, it handles manual approval and deployment to production. Database: I'm using a large dataset, and migrations are applied to both a testing database and the live database in different stages. Concerns: Migration Conflicts: When workflows run in parallel and developers raise pull requests with migration changes, I face conflicts when these workflows try to run migrations on the test or live databases simultaneously. Sequential Workflow: Running workflows one after another avoids conflicts, but significantly delays deployment when there are multiple pull requests waiting to be processed. My Questions: What’s the best practice for managing migrations when multiple pull requests are raised with migration changes? Is there a way to efficiently run parallel workflows without causing migration issues but still avoiding delays in deployment? How can I ensure database migrations run smoothly and prevent conflicts when multiple developers contribute changes that require schema updates? Any tips or suggestions on how to handle this situation would be really helpful!
at frame 14.51 why the Airtel logo is shown as Cloud in the left upper corner? Whoever watching this video are you guys all enterprise architect or will to become one?
Very interesting conference. Some of my highlights include: * Every architectural decision is based on a tradeoff. * If we haven't found the underlying tradeoff, it's because we haven't analyzed enough. * The tradeoff has a business translation, so the architecture decision can be driven by the business. The book is now on my reading list 🙂
Hi All, as he was saying u have to learn not only the use case but also learn one level of abstraction over the concept. I am trying to learn the abstraction by using the class files but I couldn't able to learn fully. Is there any other way to learn these abstraction or is my current approach is correct. Kindly let me know you have any idea on this. Thanks🎉
There is some good information towards the 2nd half. The analogies by the presenter are not helpful. Especially the picture analogy. Not enough technical information with examples.
