Anton Zaides’ Post

After talking to hundreds of engineering leaders working on cloud-native applications, a recurring theme is the challenge of developing effective testing strategies within decentralized architectures using many microservices. Without solid strategies, continuous delivery becomes a distant goal. - As engineering teams grow, quality engineering (QE) can become a bottleneck. Shifting testing left and empowering QE to play a strategic role can be a game-changer. - How can you enable hundreds of developers to own testing effectively? Which tests should be manual, and which should be automated for maximum ROI, considering bandwidth limitations? - On the infrastructure side, how many test environments are enough? How can you reduce contention on shared environments and prevent duplication? These are common questions with complex answers. Subscribe to our blog at https://lnkd.in/gySDg9y for insights and solutions. #microservices #testingstrategies #developerexperience #kubernetes

If you are looking to get started with Continuous Delivery (CD) have a look at this great resource thanks to Bryan Finster one of my fav engineers to follow here in LinkedIn! https://lnkd.in/gdqZ_kvW Can't get enough Bryan, keep up with him on Medium. https://lnkd.in/gX3dj9DS Keep up the #CodeHustle🕺! #GovDev #TheRosieProject #VetsWhoCode 👩🏽💻👨🏿💻👩🏿💻👨💻👨🏽💻👨🏼💻👩🏾💻👩💻👨🏾💻👩🏼💻

Late Post Engineers building for engineers! 🚀 Our inaugural "The Exchange" was a huge success, showcasing the cutting-edge tools and techniques we're developing to take our software delivery - leap ahead. #rootedinnovation focussed on Productivity and Quality! What's "The Exchange?" It's our new, bi-annual internal conference designed to share knowledge and accelerate innovation across our engineering and delivery teams. Internal Utility and Software Marketplace, In-house built Code Bots integrated with IDE’s, Upgraded Developer Portal integrated with our own development framework, Actionable Productivity and Quality Dashboards, Value stream mapping, Mainframe CI/CD, FMEA Utilities, In-House DApp Development Platform and many more within our robust SDM. A big thanks to TDP (Technology Development Program) Associates. And also Big thanks to AWS for their inspiring demos on the latest cloud possibilities! 👏 This is a testament to our commitment to engineering excellence. We're not just keeping up with the times – we're pushing the boundaries of what's possible in financial services technology while giving utmost importance to our risk culture. #domoretalkless Oleksandr Rudenko Regini Lee 李晶妮 Ketan Jain Vinod Kumar V. @ganbold @lokesh Stanley Low Handi T. Aaron Chang Bharath kumar Bachina Kiran Salke Prasanna Kabra Amit Sharma Deana Teo @tan wee min Ramesh Kumar Avudaikumar Hadi Sutanto Mahinder Baweja, PMP Ramnath Sharma Salva Vilarrasa Evan Ho Lim Ker Liang Adhunik Chug Santanu Chowdhury Ko Ye Wint Nyein Raman Jee Mishra @ramkumar Annamalai and many more whom I couldn’t tag. Sid Bhandari and AWS team - 🫡 for the demos and we will continue challenging each other ;). #architectureandbeyond #productivityandquality #devops #developerexperience #Failuremodeeffectanalysis #machinecollaboration #engineeringculture #wedreamwemake #letthecodetalk #tinkeringthatworks

Refactoring is about evolution, not revolution. People focus too much on: • Rewriting systems from scratch • Trying to modernize everything at once • Adding new features without fixing existing issues But successful engineers: • Incrementally improve code to maintain stability • Prioritize essential fixes over flashy upgrades • Maintain what works and evolve what doesn’t Refactoring is about: • Building on a solid foundation • Building maintainable systems • Building trust in the codebase Remember: Small, consistent improvements lead to long-term success. The foundation is understanding the existing system. #SoftwareArchitecture #SoftwareEngineering #Refactoring #Evolution

𝐃𝐞𝐯 𝐓𝐞𝐬𝐭𝐢𝐧𝐠 𝐢𝐧 𝐃𝐢𝐬𝐭𝐫𝐢𝐛𝐮𝐭𝐞𝐝 𝐄𝐧𝐯𝐢𝐫𝐨𝐧𝐦𝐞𝐧𝐭𝐬: 𝐀 𝐌𝐞𝐬𝐬𝐲 𝐘𝐞𝐭 𝐂𝐫𝐮𝐜𝐢𝐚𝐥 𝐓𝐚𝐬𝐤 🔍 As software engineers, we’re familiar with the challenges of testing in a distributed environment, especially when dealing with event-driven architectures. It’s a complex and often messy process, where issues like race conditions, data consistency, and event ordering can make it feel like trying to untangle a web of interconnected threads. 𝐁𝐮𝐭 𝐰𝐡𝐲 𝐢𝐬 𝐢𝐭 𝐬𝐨 𝐜𝐡𝐚𝐥𝐥𝐞𝐧𝐠𝐢𝐧𝐠? 🤔 1. 𝐂𝐨𝐧𝐜𝐮𝐫𝐫𝐞𝐧𝐜𝐲 𝐈𝐬𝐬𝐮𝐞𝐬: With multiple services running in parallel, synchronizing state across the system becomes a nightmare. 2. 𝐄𝐯𝐞𝐧𝐭 𝐎𝐫𝐝𝐞𝐫 𝐒𝐞𝐧𝐬𝐢𝐭𝐢𝐯𝐢𝐭𝐲: A slight change in the order of events can lead to unexpected behaviors and hard-to-reproduce bugs. 3. 𝐃𝐞𝐩𝐞𝐧𝐝𝐞𝐧𝐜𝐲 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭: Mocking dependencies and ensuring consistent test environments across multiple microservices is no easy feat. Despite these challenges, it’s essential to have robust testing strategies in place to ensure system reliability. Embrace the mess, and let’s keep pushing the boundaries of what’s possible with distributed systems! 💪 How do you tackle testing in distributed systems? #SoftwareEngineering #DistributedSystems #EventDrivenArchitecture #Testing #DevLife

'The hidden cost of microservices is integration failures' This is what 100% of the CTOs I have met warn their teams about. 4 reasons I feel smart CTOs are not underestimating the cost of moving to a service oriented architecture 1️⃣ Downstream changes ➡️ Upstream failures In a fast paced environment, rapidly changing services cause upstreams to fail in unexpected ways, without notice. Further unknowable if dependent services (upstreams) are too many or dependencies are unclear to devs. 2️⃣ Collaboration in a multi-service set-up not easy Difficult for devs to collaborate in a large team over changes that involve multiple services. What gives? frequent changes and too many services 3️⃣ Debugging nightmare Super hard for devs to debug these problems because there is no easy way to reproduce origin and path of the failing request, hopping over multiple services. Most dev struggle to answer 'where did this mess start from?' 4️⃣ Writing integration tests harder than development Devs mostly write unit tests, which are never enough. Second, testing integrations means simulating or mocking dependencies which is never easy to get right TAKEAWAY CTOs know integration failures are unavoidable in a multi-service set-up #1 reason devs are forced to do late night fixes, spend excessive time debugging production failures and go slow in shipping new changes. HyperTest is trying to make this uncertainty go away by making integration testing easy for developers. Teams should never leak integration failures. More details on how we make this happen for teams: hypertest.co #microservices #integrationtesting #devs #productivity #quality #automation

Revolutionizing Software Development: The High-Tech Assembly Line Discover how automated pipelines transform software development, enabling swift releases and minimizing bugs. By aligning developers, testers, and operations seamlessly, we can adapt to the complexities of machine learning and keep pace with change in an evolving landscape. Experience the future of software development! #SoftwareDevelopment #TechInnovation #Automation #MachineLearning #DevOps #AgileMethodology #SoftwareEngineering #ContinuousIntegration #CodeQuality #TechTrends

🚀 New feature alert! Need to share project info with teams outside of OpsLevel? Now you can generate a CSV report directly from your Services page! Users can filter by attributes such as languages, teams, and tags to create a shareable list. 😎 A small yet mighty we're making the lives of our engineering leaders even better. Check out our docs to learn more: https://lnkd.in/gj9KRfj5 #devops #engineering

Slash Your Dev Time: Stop letting manual testing eat 40% of your development cycles. Learn how top teams cut testing time from 2 weeks to 8 hours with automated pipelines. Key wins: 70% faster testing 90% fewer errors 3x quicker releases check out the article here : https://lnkd.in/d-MRreWq #DevOps #Engineering #isentryTechnologies #innovation

For the most part, I have built monolithic server-side applications where every piece of the software lives on the same server and the means of interaction from sign-up to wallet creation is a few imports away. I share this school of thought about monolithic applications. A lot of the applications that I have shared and worked on were monoliths, and many times in the past I wondered how I would scale and break the application down into microservices and maintain communication across the system. In 2023 I got to work in a microservice environment which relied heavily on docker and Kubernetes for development and serving the application in instances. During this process, i got to see first-hand how interprocess communications in a microservice environment can be carried out. In this article, titled "Product Engineering: Interprocess Communication via message queues with FastAPI" I discussed how interprocess communication between two separate servers occurs in achieving the specified tasks. "Product Engineering: Interprocess communication via message queues with FastAPI" https://lnkd.in/dujgizQC #fastapi #software #product