CardCash’s View of Microservices
CardCash’s View of Microservices
There are tremendous benefits to the cost of building out the supporting architecture, infrastructure, and processes for microservices.
Join the DZone community and get the full member experience.Join For Free
Containerized Microservices require new monitoring. Read the eBook that explores why a new APM approach is needed to even see containerized applications.
Thanks to Thomas Butt, CTO, CardCash for sharing his thoughts on the current and future state of microservices.
How is your company involved in the creation or use of microservices?
At CardCash we’ve been building and deploying microservices for more than two years. A major portion of our production system is now running as microservices on AWS.
What do you see as the most important elements of microservices?
The key benefits are: 1) isolation of responsibility - simpler to build and maintain microservice code; 2) fault isolation - any microservice can crash and restart without causing a service outage; and, 3) fine grain scaling - each service can scale independently and rapidly.
Which programming languages, frameworks, and tools do you, or your company use, to build out microservices?
How have microservices changed application development?
More frequent deployments. Less manual testing, more automated testing. Zero downtime deployment. Easier to rollback. Greater need for automated testing and deployment.
What kind of security techniques and tools do you find most effective for securing microservices?
JSON Web Tokens, Amazon Virtual Private Cloud, and API Gateway pattern.
What are some real-world problems you, or your clients, are solving with microservices?
CardCash provides an online marketplace where anyone can go to buy or sell pre-owned discounted gift cards. Our marketplace handles a high volume of web e-commerce transactions rapidly and securely through our microservice architecture.
What are the most common issues you see affecting the implementation of microservices?
The stated benefits come at a cost of having to build out the supporting architecture, infrastructure, and processes. This means the upfront investment in both time and money is higher, before you begin to see the benefits.
Do you have any concerns regarding the current state of microservices?
There is still a lot of tooling you need to build out yourself, but this is rapidly changing.
What’s the future for microservices from your point of view - where do the greatest opportunities lie?
The move to on-demand compute resources and serverless architectures will strengthen. Better tooling for rapidly building and deploying microservices will eliminate the need for a large upfront investment. Richer third-party microservices that are easy to integrate into a microservice ecosystem will allow companies to offer more advanced capabilities more quickly.
What do developers need to keep in mind when working on microservices?
Without a solid underlying communications architecture, the distributed nature of the system is complex - more complex than a traditional monolithic architecture.
Is there anything you’d like to know about what software developers are doing with regards to microservices?
Keeping up with the tooling and techniques is always a challenge. A simple way to stay current would be valuable.
Opinions expressed by DZone contributors are their own.