Hidden GEM is here
- World Class Team (Microsoft, Y Combinator, Nvidia, Visa, IBM, etc)
- Already listed on some TOP Exchanges, waiting for BINANCE
- High transparency: Update reports every 2 weeks, regular videos made by the Founder on Twitch to show progress
- Strong network and top class VCs. Mentioned by Willy Woo, Pentoshi, Birb, Moonwalker, StackingUSD, Martini Guy, etc
Big Buying Opportunity
Radix is a solid and unpumped layer one protocol and will do a full unlock tomorrow! It is a huge buying opportunity before smart contracts and ecosystem come into the play. I personally expect a dump happening within a few days given the fact of there are early investors but it will create a very good entry point for the new ones!
Be part of our community:
JOIN RADIX TELEGRAM GROUP: https://t.me/radix_dlt
100x potential is the truth
For more information:
Links:
Website: https://www.radixdlt.com/
Twitter: https://twitter.com/RadixDLT
Discord: https://discord.gg/WkB2USt
Suppose this contrived case: SRE team members are assigned to perform automated reliability checks on recent applications before they reach the production environment. So we would anticipate any issue before support tickets are created after deployment.
For these checks to be scalable, what type of development pipeline steps would you consider adding for an automated reliability review?
For example,
- implement probes (synthetic monitoring) in the development pipeline step to perform the main user journey / workflow / business flow before deploying to production? (So we would anticipate any issue before support tickets are created.)
- if the application has blueprints in JSON or YAML format, automate the check of service dependencies to determine if dependencies still exist or if they were deprecated or discontinued.
- if the company has journeys documented (in sequence or component diagrams) and the application changes will affect a part of the customer journey, automate the check if the development team has provided updated UML diagrams showing the TO-BE changes in the workflow.
My team will be responsible for managing the expiry of certs on some of our network gear going forward. If they lapse, the entire network goes down due to the deployment design. What best practices and protocols do you use to make sure these expirations don’t get missed? We can set email reminders to an AD Group/distro but these things are liable to change or disappear over the years.
Just asking out of curiosity. Is my question even correct?
