Krish Dinesh

Пікірлер

@asiridissanayaka6849 21 сағат бұрын

Thank You for sharing the insights. Interesting.

@HowPortal Күн бұрын

These types of low hanging fruit videos will not suffice for your channel, especially since you are producing them in English. There are ton of videos of this kind with much better quality and animations. You are just adding noise to the internet.

@krish Күн бұрын

Thank you for the feedback. :)

@navodyasara567 Күн бұрын

insightful

@lakshanmadhuranga8527 Күн бұрын

Great

@nuwanniroshan 2 күн бұрын

Great content Krish

@ransandu 2 күн бұрын

Thanks for sharing this. It sounded like the flow sometimes influenced by the team structure as well. e.g in pre-develop PRs review by tech leads and develop senior TL or architect. Also I noticed that all the way up to release is about only the merge happened. What's your experience with rebase, squash-merged etc.. Appreciate if you can add a comment on those techniques and their usage based on your experience. Thanks again for this valuable video series. Cheers

@krish 2 күн бұрын

i will explain those when I get time. yes when deal with 100+ engineers commits having prior review from a TL is helps architects as then they don’t need to deal with minor oblivious issues

@kalingaranasinghe8601 2 күн бұрын

Branching is continuous isolation, for continuous integration you should use Trunk Based Development, and use feature flags to turn off partially develop feature. Trunk Based Development is the required practice for CI/CD

@krish 2 күн бұрын

thank you sharing the idea. will do an other video regarding feature rolleouts

@kalingaranasinghe8601 2 күн бұрын

@@krish I see lots of devs misunderstand CI/CD. CI is not entirely your build pipeline. CI is when everyone's code get merged into master/main (trunk) branch hence the term in integration. It's is recommended to merge the feature branch at least per day, hence the term continuous. so what's happen when developer code is not ready, that's ok you disable the feature and continue to merged the code master. Next come CD, so your feature disabled/enabled code continuously release to other environment. when you are ready you can simply enabled the feature. Next level is progressive delivery, you can enable the feature visible to 30% user and the measure the error rate. if no error you increase it to 50% and so on. Continuous is faster than people think here. This the modern DevOps practice. When you have separate log living branch you are doing continuous isolation(think about the time you have to spent to review code for each of these branch merges), you have build more than once. When you do Trunk Based Development you build once and deploy anywhere. When you do continuous integration and deployment this way you don't need release schedules.

@HowPortal 3 күн бұрын

What is the best branch strategy for managing multiple versions of the same software? For example, a basic version and a pro version, where the pro version includes all the features of the basic version plus some additional features.

@vivekagrawal5608 3 күн бұрын

We are also following the same convention. However, there are minor changes which worked for us. All the day to day development (features) is merged to "develop" branch. The develop branch is deployed in dev env. All the changes from develop branch gets merged into master branch every 2 weeks. This branch is deployed in qa env and all the test cases run on top of it. Now, the production deployment happens from Master. For any HF, the changes needs to be merged in dev and then in master. The master would get deployed in production. We tried release tag, however, it was too much overhead to maintain 3 branches.

@krish 3 күн бұрын

Thank you for sharing. yes this almost same. but better keep a tag for every release as that making sure we have "copy of the production code"

@vivekagrawal5608 3 күн бұрын

@@krish Yes sir, we need to have a tag for every release. If something needs to go immediately, then the best way is to create a branch on the release tag and deploy it to production from there. I am a big fan of your work and really appreciate your series on microservices.

@bernardobuffa2391 3 күн бұрын

we follow a different approach for hotfixes they went the usual hotFixBranch -> develop -> QA branch promotions, and to appy the hotfix in production environment we cherrypick the commits

@vipulgulhane4934 3 күн бұрын

What is branching staragey for everyday release

@krish 3 күн бұрын

same. create new release branch along with previous release deploys and put the commit to that. BTW what sort of usecase for daily releases? how do you manage QA / UAT sign off?

@vipulgulhane4934 2 күн бұрын

@@krishthat why I wanted how do we deal with this situation. Imagine the the use case of stock market related or zerodha kite goes every day updates in the night with release.

@RusiruNethmina-jb6zl 3 күн бұрын

thank you

@TCHewagama 3 күн бұрын

👍

@kasunsudarshana4727 4 күн бұрын

Good content as always

@sanujamethmal9188 5 күн бұрын

Whats that bottle? Did he just drink straight from a flask? 🫨

@newtonsazzad748 5 күн бұрын

great content

@csnawwa 5 күн бұрын

I was using Rabbitmq events in my consumer side and Process seems overloaded some time and I can implement this pattern with smaller window. very informative content , Thank you lot...

@rakeerakee 5 күн бұрын

If there is a person if he don't know about something and also he don't know that he don't know he's a fool, also there is a person if he know about something and also he don't know that he know he's a fool, But there is a person if he don't know about something and also he know that he don't know he's a inteligent

@DailyDoseofRise 6 күн бұрын

Thank you

@anuradhanisharanga719 7 күн бұрын

Very valuable content keep it up sir❤ Thank you!

@TCHewagama 7 күн бұрын

@TharinduFernando99 7 күн бұрын

😍😍

@nandikajeevantha1364 7 күн бұрын

😍

@thisalma 7 күн бұрын

Krish, I have never worked with you. I got to know you from a friend of mine who used to work at Virtusa sometime back. All your videos great and I learn so much from them! You clearly are making a great impact on our field! Cheers mate! Thank you!❤

@krish 7 күн бұрын

🫂 ❤️

@HowPortal 8 күн бұрын

These type of videos are kind of unique and i like them. But think about making a video series about engineering something for example:, a framework backend/frontend, design system and etc. And make it public on your github.

@ishan1095 8 күн бұрын

Thanku. I know this is not a IT related Question. What is the Hex Code of your walls?

@krish 7 күн бұрын

you mean for the color?

@ishan1095 7 күн бұрын

@@krish yahh

@userx0r 8 күн бұрын

❤

@ThanujaFernando-vu5dh 8 күн бұрын

Thank you krish, good content as always!

@krishanmadushanka9521 8 күн бұрын

Does HTTP/2 make websockets obsolete?

@krish 8 күн бұрын

good question. will talk about it. quick answer is NO

@lakshanchamod1208 9 күн бұрын

wow

@xlogan6041 9 күн бұрын

❤❤

@harshathirimanna 9 күн бұрын

This is a fantastic explanation! Please keep up the excellent work, Krishantha. We watch your videos all the time.

@rakeerakee 9 күн бұрын

Great Advice. It is matching to me. I started preparing myself.

@mohamedabdullah3733 9 күн бұрын

Thank you so much for this.... This is what I'm searching for past 6 months

@harshaliyanachchi5638 10 күн бұрын

Valuable video. Thank you.

@TCHewagama 10 күн бұрын

👍

@RamithD 11 күн бұрын

Good content 👍

@danujagreru 11 күн бұрын

Very informative series Mr.Krish

@ozdadev 12 күн бұрын

😍

@user-jk3pu5kf8h 12 күн бұрын

Thank you Krish for sharing ! appreciate if you could share what went wrong with the DNS.

@Cyber_Lanka 13 күн бұрын

Haha this analogy is very nice. Thanks for the nice video as always

@ImeshMadushanka-um6fe 14 күн бұрын

Why not a queue service?

@namilaperera5649 15 күн бұрын

I have seen some SQL DBs have "SELECT FOR UPDATE" feature.... once a transaction reads a record, it is blocked for other transactions until the first one commits, I guess it could also be helpful in scenarios like this :)

@userx0r 15 күн бұрын

As always, a fantastic video!

@udarasan8216 15 күн бұрын

Thanks for sharing. can you make a long video for concurrency practice? any recommended resources?

@krish 15 күн бұрын

will try to do a video. ref: read concurrency in practice book

@Cyber_Lanka 15 күн бұрын

Thanks for the very educational video. Could you also do a video about how or when companies usually decide to go with micro services rather than monoliths?

@krish 15 күн бұрын

i thought about this today morning 😶‍🌫️ it may probably come in next week

@TCHewagama 15 күн бұрын

Thank you Krish

@rukshannet 16 күн бұрын

What about do not touch the code if it is working.. 😆

@krish 15 күн бұрын

😂 thats golden rule… 🫣🫣

@RasanSamarasinghe 16 күн бұрын

Thanks for highlighting such an important topic! This discussion will be beneficial for many in the software development industry. While software architecture is often considered an advanced subject, it is still covered at a basic level in many undergraduate degrees. It is important for any developer aiming for long-term growth. If your current job role or designation restricts you from thinking and contributing like an architect and instead enforces you to merely implementing and maintaining software, writing code, and solving day-to-day development problems, it's time to reconsider your career path.

@krish 16 күн бұрын

exactly…

@nareshn6628 16 күн бұрын

Great content, thank you Sir

Ең жақсы KZfaq

Пікірлер