Thanks Kavita Keep learning 😃

@@Javatechie if possible, could you make a video on Microservice observability like how actually micrometre project works, how it stores api hit etc does it directly communicate with server configs (devops things) or maintaining data at its end like filter nd own db etc. If possible to show the insight of that projects 🙏.

Sure Kavita let me Deep dive more into it then i will update 🙂

No it's not there but I will plan for it .

Thanks buddy. It will work for distributed system

I don't think so as those are stored in spring boot in-memory.

Yes buddy i will do that give me sometime

@@Javatechie - Take your time brother. :)

Not getting how manifest file will help here

Sure buddy i will.

Prometheus and grafana usually people use . I have not explored more on datadog buddy will check and update you

@@Javatechie Thank you!

@@Javatechie Can you make a video on Prometheus and Grafana specially the query language , it would be really great as they are used in many good companies.

Yes buddy i will remake this

Yes but your configuration should be always external to your project so redeployment not required

Hi Sajeesh , let's take a small use case assume in ecommerce application i am loading location information from one 3rd party application but in future i want to fetch it from my DB instead of getting it from 3rd party app so i have implemented the code by pointing to DB but my project is live and i want to test my New implementation then how can I do that without decommissioning the 3rd party call? In this kind of situation the toggle switch will help you

@@Javatechie Thanks for your reply. I got your point. Only in such scenarios we can use toggle features else we can use admin setting the features.

Yes absolutely

No you can set the parameters dynamically to the toggle itself that will be my next video

Yes i believe manually we need to store past state

Hi i have tried below curl curl -d '{"name":"DISCOUNT_APPLIED", "enabled":"true"}' -H “Content-Type: application/json” -POST localhost:8080/actuator/togglz/DISCOUNT_APPLIED

Thank you so much. It's really helpful as much as cool.

No application restart won't impact much as based on your state it will behave

Even though it's multiple code still code where we are accessing feature management is the same right ?

If you will keep in the db then how do you toggle, definitely either you need to hit the api or run manual update query right?

@@Javatechie thanks for reply brother. Yes I meant having an api for this variable to toggle. Is this worse or better in terms of performance?

Buddy Single api call won't impact much on performance but still why should we go manual when we are getting this feature freely by just adding a dependency

@@Javatechie here also it's manual change only in ui or postman hit so both are manual ways in which u r enabling feature...same thing can be done in db flg which can be cached by in memory datastore which is centralised...and executing db update with central cache refresh for given feature key will reflect changes in all pods or instances...this is much more better approach than hitting postman or ui based updates on each pods or instances of application....with multi instance environment which is normal for prod...this thing if it's centralised thn only it's usable or effective else it's just not effective enough thn db centralised feature flag storage and updates in db as thts performance efficient

Aravind you have asked 3 questions in a single response 😜. Tell me which one is priority for you 😉

@@Javatechie Service now integration and enable audit tracking, Thank you

No it's not equal i will cover that

I have not used it but it is absolutely allowed as it is open source

I guess you can use builder pattern

Toggle auditing i haven't tried need to check

I think FeaureManager works with spring boot 2.7.5 not with spring boot 3.0.0

Ohh is it . I will check and update

@@Javatechie thanks for replying

Then you need to update in all replicas This is expected right

@@Javatechie is it an ideal solution in production environment ?

Yes ankith , what is the drawback? Why do you think it's not good for production?

@@Javatechie it could cause data inconsistency. For ex. If we have 3 services each with 5 replicas. Even if we fire an api to update the feature state in all 15 containers, due to network latency, pod availability or some internal error if the service doesn't update it's state it can cause request failures or could corrupt the DB. Having a central service holding these flags would be an ideal method, although there is a risk of single point of failure, there won't be data inconsistency is what I feel. How about you ?

Yes we can set discount parameters dynamically using toggle i will do that in my next video

@@Javatechie thanks

I have not tried the UI. Will check and update you

​@@Javatechie any update on this.

I will check and update not have much idea on UI

please check the unleashed and launchdarkly feature togger frameworks, that has capability of multiple technology stacks

@@Javatechie Thanks

FF4j heard something new buddy let me check

@@Javatechie Sure, FF4J is feature flags for Java. It also flips features and does kind of similar things as togglz.

Awesome thanks for sharing this info Pratyush

"Togglz" is conceptually largely identical to "FF4j", though the APIs for querying the feature flags differ significantly as Togglz relies on Java enum as its primary means. "Unleash" is virtually identical to that of FF4j, and has probably more features than these other two. Worth considering, while chosing one out of these three.

May I know what are those new technologies??

Hey sparkDev sorry for the inconveniences. By mistake it was deleted please don't mind and repost

@@sivannarayanapenumala1840 those are LaunchDarkly and unleash. Where unleash is.opensource and LaunchDarkly is paid

If you will use the database then to toggle any features you need to trigger a query right? Either manually or through api to update the flag value

@@Javatechie If you don't use a permanent storage like fiile or a database, your flag will be reset everytimie you retart or redeploy the application. Don't want people to get free discounts by accident just cause we released a new version right ?

Yes that's what I was trying to convince you to maintain your State of features external to your application like database or file