Mallesh Panthagani

Just finished the course “DevOps Foundations: Continuous Delivery/Continuous Integration” by Ernest Mueller and James Wickett! Check it out: https://lnkd.in/ge5MwSbw #devops #continuousintegrationandcontinuousdeliverycicd.

2

1 Comment

The last day to register for Nebraska.Code() without a Late Fee is July 3rd! https://lnkd.in/dsKrsic #SoftwareDesign #development #deployment #AI #machinelearning #frontenddevelopment #opensource #technology #EmergingTrends #practicalagile #DevOps #SecurityMeasures #careerdevelopment #softwarecraftsmanship #Nebraska #TechnologyConference

4

If anyone tried to e-file their taxes with H&R Block desktop software, over 24 hours (Sunday, April 14th until midday April 15th), they would have failed. https://lnkd.in/gycJmDDN Let me break this down for you - this is a CLASSIC n-phase commit issue. I would NOT be surprised if they are using threads to meet this need and of course, they are failing spectacularly! Why? Because as much as I love threads, I have been using threads since 1994 or earlier, large-scale, heterogeneous systems architecture is never to be built with threads! Threads mean you hope you can control the spanning and the response times. Otherwise, the countless waiting threads chew up cycles, timing, and the overall machines, until you have system starvation. The proper way to manage unbounded interactions is to use non-blocking (event-based) architectures. This allows the backend to manage the many disparate systems it needs to interact with and ensure they are completed and the customer knows the final outcome. I stress, the last point - you can have the best backend system out there but unless the customer interaction model is equal to the backend model, the customer will not know what happened. If the backend is trying to do many things in an async manner but uses a sync user interaction model then the customer does not know what happened. The customer may be trying to e-file their taxes, which is at least two steps, charge the card and file the taxes with at least one government system, maybe more. If that interaction on the backend is done async, and then it fails, the customer's interaction model will also fail, and now the customer is left in a place where they do not know what happened! Many customers, in this case with HRBlock, actually had their e-file work, but they never knew it! Eventually, the Federal Government emailed them saying that the taxes were filed. Which is a horrible user interaction. The main point here is that all complex user-facing interactions on the backend need to have a user model where the customer knows what happened and if they can try again! Failure is NOT an IF it is just a WHEN. One MUST build their architecture embracing failure. In the end, persistent orchestration, using things like Airflow of Amazon Steps, along with idempotency is the only way to ensure that the customer will get the outcome they desire. System failures is expected, systems not giving the customer a final understanding of where they stand on such important transactions is a failure. If the user experience is clear in stating that the user's request is being handled and then the backend fails, but the user experience is not tied - directly - to that backend, then that one level of abstraction allows the experience to do retries and poll for the state of the backend's final outcome. Best wishes to all for success and much better outcomes than my annoyances this week!

17

2 Comments

Automate anything, anywhere with Redwood Software's extensive suite of automation fabric solutions. 🌟 Follow Redwood Software to stay updated on the latest trends, insights and success stories in the world of automation. Trust me, you don't want to miss out on this journey towards a more efficient and effective future. 🚀 Stay connected 👉 Redwood Software #Automation #Innovation #Productivity #RedwoodSoftware

8

Just finished the course “Microservices: Design Patterns (2020)” by Frank P Moley III! Check it out: https://lnkd.in/gXJZ2sHr #softwaredesignpatterns #microservices.

1

Webinar: Successfully apply AI for application modernization Generative AI has the power to transform the process of Application Modernization through code reverse engineering, code generation, code conversion from one language to another, defining modernization workflow, and other automated processes. This webinar is designed to equip technology leaders with the knowledge and understanding necessary to evaluate your technology estate, assess the opportunity and chart a path forward. https://lnkd.in/e8NybGTW

8

Just finished the course “Learning Cloud Computing: Serverless Computing” by David Linthicum! Check it out: https://lnkd.in/gxWruEcn #serverlesscomputing.

5

🔧 Exciting News! I just completed the Liquibase and the CI/CD Process course!  🎓 This course is perfect for anyone eager to integrate Liquibase seamlessly into their CI/CD pipelines. I delved into core DevOps and CI/CD concepts, learned how Liquibase fits into the process and explored automation tools to streamline database changes. Plus, I mastered source control management best practices and database testing for the Liquibase build environment. If you're diving into CI/CD and #DevOps, don't miss out on how Liquibase can level up your database automation! 🚀 #Liquibase #DatabaseAutomation #TechSkills

7

App modernization is already a priority for most organizations. And yet, according to McKinsey, 70% of change programs fail. Why? Here are some of the common reasons I���ve seen as to why organizations' previous modernization efforts have failed 👇 #AppModernization #DigitalEngineeringServices #SutherlandDES

67

2 Comments

I've written an article along with my colleague Sahana Y S on GraphQL technology and API development using GraphQL and Spring Boot. GraphQL is an alternative to the ubiquitous REST API architecture. This article should be helpful for any architect looking to design data-driven APIs using GraphQL or any Java developer who wants to start developing their first GraphQL API. The article:

20

Key enhancements in Java 22: Project Amber: Introduces language features like statements before super(), unnamed variables and patterns, string templates, and implicitly declared classes for more expressive and concise code. Project Loom: Offers concurrency improvements with structured concurrency and scoped values to simplify concurrent programming. Project Panama: Enhances native interoperability with a new Foreign Function and Memory API and an improved Vector API for better performance. Core Libraries & Tools: Updates include a Class-File API, multi-file source-code program launcher, and Stream Gatherers for enhanced developer productivity. https://lnkd.in/gpu9m4Gm

1

Business credit scores are an important aspect of your company’s financial health. They can impact everything from investor relationships to insurance costs and eligibility for funding. There are several ways you can establish and influence your company’s credit score, such as by using a business credit card responsibly and paying all your bills on time. Learn more about how to increase your company’s credit score to support its success and growth.

1

Just finished the course “Site Reliability Engineering: Service-Level Agreements and Objectives” by Laura Stone! Check it out: https://lnkd.in/g-w48qJs #servicelevelagreements #sitereliabilityengineering.

The only things that have changed are the number of processors and amount of available RAM.

3

How can the value provided at #OutperformwithPROS benefit your business? Find out what PROS VP of Design and User Experience, Ravi Singh has to say to someone who says they can't afford to take a week off work to attend. Don't miss out! 📆 May 20-22, 2024 📍 Orlando, FL 🔗 pros.com/outperform Welcome to #GenerationAI - let's embrace the future, to be part of the narrative. #PROSAI #ProfitableGrowth #B2B #Airlines #AI

1