Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
14 views1 page

Cloud Native Application

Cloud-native architecture leverages cloud computing for flexibility and scalability, utilizing microservices and containerization. For an airline ticket booking system, a microservices approach allows for independent handling of unique airline payment requirements, enhancing resilience and scalability. This architecture enables faster development and easier updates, ensuring a better experience for users and developers.

Uploaded by

pirateking16921
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
14 views1 page

Cloud Native Application

Cloud-native architecture leverages cloud computing for flexibility and scalability, utilizing microservices and containerization. For an airline ticket booking system, a microservices approach allows for independent handling of unique airline payment requirements, enhancing resilience and scalability. This architecture enables faster development and easier updates, ensuring a better experience for users and developers.

Uploaded by

pirateking16921
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
You are on page 1/ 1

Cloud-Native Application: Definition

Cloud-native architecture is a modern approach to building and running applications that take full
advantage of cloud computing. Unlike traditional monolithic architectures, which bundle all
components into a single unit, cloud-native applications are designed with flexibility and scalability
in mind. They are typically built using microservices, containerization, and managed services
provided by cloud platforms.

Benefits of Cloud-Native Architecture:


• Scalability: Applications can scale up or down based on demand, making them more
efficient.
• Resilience: If one part of the application fails, the rest continues running, reducing
downtime.
• Flexibility: Developers can update and deploy individual features without affecting the
entire system.
• Faster Development: Smaller, independent services allow teams to work on different
features simultaneously.

Application Architecture for Airline Ticket Booking System


For the flight ticket booking system, using a microservices architecture is the better choice. This is
because different airlines have unique payment requirements, and a monolithic system would make
it harder to accommodate such variations without making the code complex and harder to maintain.

Proposed Architecture:
1. Frontend Service (UI): A separate service responsible for handling the user interface and
interactions.
2. Payment Service: A microservice dedicated to processing payments, which can handle
different rules based on airline requirements.
• Airline A: Only PayPal allowed
• Airline B: No online payments (booking is manual)
• Airline C: PayPal and debit card payments allowed
3. Booking Service: Manages flight reservations and availability.
4. Customer Service: Handles customer-related operations, including support and profile
management.

Why Microservices?
• Each airline's payment logic can be handled independently without affecting others.
• Future changes (e.g., adding new payment methods) can be done without modifying the
entire system.
• If one service fails (like payments), the booking service can still function.
• Easier to scale each component separately based on traffic.
By following a microservices approach, the airline booking system remains scalable, adaptable,
and resilient, ensuring a better experience for both users and developers.

You might also like