Imagine you are a start-up company planning to re-architect the current 3-tier application (built on web server, JBOSS, MySQL) into a new Microservices architecture. Like many start-ups you are confident that your startup will be the next big thing and you expect significant, rapid growth in the next few months. With this in mind, you need a cost effective solution that can keep pace and scale with growing customers base. The new architecture should -
Let's look at the existing mock architecture deployed on, on-premise hardware ( company's own server hosted at a data center)
Leveraging AWS Managed Services
- Support Service Discovery
- Should have Granularity of Microservices
- Should have data consistency across Microservices
- Should load balance the load, distributing load across instances
- Should have a robust database design (1 DB instance per microservices or 1 common DB instance)
- Should have auto scaling of microservices when load increases or decreased
- Solution should have well implemented application logging
- Solution should be such to Avoid any Downtime
- Solution should use of managed services to manage the microservices architecture on AWS cloud
Let's look at the existing mock architecture deployed on, on-premise hardware ( company's own server hosted at a data center)
Start-up Requirements & Concerns
Following are the key requirements and concerns of the startup company that the new architecture should address
Why Microservices Architecture?
The following are key points that build a case for a new Microservices architecture on AWS Cloud
Developing Microservices
The following are key devops considerations for developing a Microservices architecture.
Proposed Microservices Architecture on AWS
The following diagram shows a sample Server-less Microservices architecture on AWS Cloud
Leveraging AWS Managed Services
The following diagram shows the key features of AWSS Managed Services offering that can be leveraged by the company to deploy a well designed application utilizing the AWS server-less model
Recommended Roadmap For Microservices Architecture On AWS
Key things to consider while planning the roadmap for Microservices on AWS Cloud.
Key benefits of ASW Cloud
Key points
Manageable : By use of lifecycle Monitoring & Management tools
Secure : Proven security tools, services & template automate 360 security
Scalable: Auto scaling & high speed distributed n/w ensures scalability
High performance : Efficient use of AWS services, tools & architecture
Elastic & Efficient: Serverless architecture, Elastic EC2 & fast provisioning
Highly available & Fault tolerant: ELB & Multi zone deployment
Recoverable architecture- 4 DR models efficient & reliable Disaster Recovery
In summary
Moving from on premise to AWS
- Resources training & certification at beginning will be critical for success of program
- Leverage AWS Managed Services to define & implement cloud strategy & roadmap
- Three stage benefits by leveraging AWS, Microservices and Serverless computing
- Leverage cost benefit of cloud to launch test environments before switching code base
- AWS has multiple services, reusable templates & objects that should be leveraged
- Understand the technology changes
- Automation, Configuration Management, Design Documenting design & technology decisions is critical for success of Microservices
- Move to Microservices is an incremental process & needs training
- Design Review will ensure that we don’t create another monolith
- Reorganize development and IT teams
- DevOps teams to be empowered & recognized for adapting new development culture
Microservices Architecture - Not quite Service Oriented Architecture in new bottle! tart-up Requirements & Concs
