In today’s rapidly advancing digital landscape, securing microservices architecture is paramount to the success and resilience of modern organizations. At Keyhole Software, we understand the critical imperatives of protecting against unauthorized access and safeguarding sensitive data. This guide explores key strategies to fortify your microservices architecture’s security, highlighting the comprehensive services we offer to help you navigate and implement these …
Architectural Assessment: Migration to Microservices
A senior Keyhole Consultant led an architectural assessment for a cash flow management client. The goal was for the consultant to lay out a roadmap for the incremental migration away from legacy Ember.js front-end and Rails-based monolithic architecture to a microservices and React front-end implementation.
Microservices Architecture: The Good, the Bad, and Testing
Itโs important to thoroughly consider both the benefits and drawbacks of microservices architecture before you implement it. Itโs also important to implement robust testing strategies to ensure the reliability and quality of the overall system.
Over the course of this blog, Iโll explore the good, the bad, and the testing side of microservices. My hope is that this will give you a starting point as you consider whether microservices architecture is right for your project.
Cloud Native & Microservices Readiness Assessment
The project included an assessment of an existing monolithic application and recommendations for modernizing it to achieve the goals of the initiativeโmainly a cloud-first, performant, and microservices-based implementation. Specific technology suggestions were proposed in addition to the reasoning behind each recommendation. While proprietary details cannot be shared, generalized takeaways are included. Client Consulting Relationship The client was a global leader …
Updating Microservices with Netty 5, Kafka 3, and React: Whirlpool Revisited
Back in 2015 and 2016, I wrote two blogs that went step by step to develop a microservice/Netty architecture with fully working code called Whirlpool.
A lot has changed in the years since, so recently I decided to come back to the project, update it with the latest versions of Kafka and Netty, and add a React UI to it (rather than the vanilla JavaScript version it used before). In addition, I also added Windows Subsystem for Linux (WSL) scripts in addition to the Mac and Linux scripts that were there before and made all of the scripts more robust.
This blog will be about the work that went into all of those updates, plus a look at the new React UI. This provides an excellent view into what it takes to update an outdated microservices application implemented with Kafka (version .9 –>3.0) and Netty (4.1.3->5.0.0-alpha2), bringing all versions up to date and adding a React UI. By the end youโll be familiar with the latest versions of these frameworks, know some โgotchasโ to avoid, as well as understand how to integrate WebSockets into React.