Pola Arsitektur Tanpa Server
Jelajahi dan terapkan pola arsitektur tanpa server yang umum, seperti fan-out, scatter-gather, dan sumber peristiwa, untuk menyelesaikan masalah bisnis yang kompleks secara efisien.
Pola Arsitektur Tanpa Server adalah pelajaran Serverless AWS Lambda Development gratis di CoddyKit. Ini adalah pelajaran 3 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Serverless AWS Lambda Development, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Serverless AWS Lambda Development mencakup 4 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
What are Serverless Patterns?
In serverless development, we often encounter similar challenges. Architectural patterns are proven, reusable solutions to these common problems.
They help us design scalable, resilient, and maintainable serverless applications by providing a blueprint for interaction between different services.
The Fan-Out Pattern
The Fan-Out pattern is when a single input event triggers multiple parallel processes or actions. Think of it like a ripple effect from one stone thrown into water.
This pattern is excellent for decoupling services and performing concurrent tasks. For example, a new file upload might need to be processed in several different ways at once.
Fan-Out: Image Processing Example
Imagine uploading an image. A Lambda function could 'fan out' this event, triggering separate processes for creating a thumbnail, adding a watermark, and extracting metadata—all in parallel.
Here's a conceptual Python example simulating this fan-out logic:
def process_image_event(image_id):
print(f"Processing image: {image_id}")
# Simulate publishing to different services
print(f" - Publishing to Thumbnail Service for {image_id}")
print(f" - Publishing to Watermark Service for {image_id}")
print(f" - Publishing to Metadata Service for {image_id}")
def main():
print("--- Fan-Out Simulation ---")
image_id = "img-12345.jpg"
process_image_event(image_id)
print("--- Simulation Complete ---")
if __name__ == "__main__":
main()The Scatter-Gather Pattern
The Scatter-Gather pattern involves sending a request to multiple recipients (scatter), collecting all their responses, and then aggregating them into a single response (gather).
This is often used for operations like searching across multiple data sources or comparing prices from different vendors.
Scatter-Gather: Product Search Example
When you search for a product, a Lambda could 'scatter' the query to various vendor APIs, then 'gather' and combine their results to show you the best options.
This example simulates querying different vendors and finding the cheapest product:
def get_product_info(vendor_name, product_id):
# Simulate calling a vendor API
print(f" - Querying {vendor_name} for product {product_id}...")
if vendor_name == "VendorA":
return {"vendor": "VendorA", "price": 100, "stock": 5}
elif vendor_name == "VendorB":
return {"vendor": "VendorB", "price": 95, "stock": 10}
elif vendor_name == "VendorC":
return {"vendor": "VendorC", "price": 110, "stock": 3}
return None
def main():
print("--- Scatter-Gather Simulation ---")
product_id = "PROD-XYZ"
vendors = ["VendorA", "VendorB", "VendorC"]
all_results = []
print(f"Searching for product {product_id} across vendors:")
for vendor in vendors:
result = get_product_info(vendor, product_id)
if result:
all_results.append(result)
print("\n--- Aggregated Results ---")
if all_results:
for res in all_results:
print(f" Vendor: {res['vendor']}, Price: ${res['price']}, Stock: {res['stock']}")
cheapest = min(all_results, key=lambda x: x['price'])
print(f"\nCheapest option: {cheapest['vendor']} at ${cheapest['price']}")
else:
print("No results found.")
print("--- Simulation Complete ---")
if __name__ == "__main__":
main()The Event Sourcing Pattern
Event Sourcing is an architectural pattern where all changes to application state are stored as a sequence of immutable events. Instead of just storing the current state, you store how you got to that state.
This provides a complete audit trail, allows rebuilding past states, and is foundational for complex event-driven systems.
Event Sourcing: Order Management Example
In an e-commerce system, instead of updating an Order record, you record events like OrderCreated, ItemAdded, OrderShipped. The current state is then derived from applying these events in order.
Here's a simulation of recording events for an order:
import datetime
def record_event(event_type, payload):
timestamp = datetime.datetime.now().isoformat()
event = {
"eventId": f"evt-{datetime.datetime.now().timestamp()}",
"eventType": event_type,
"timestamp": timestamp,
"payload": payload
}
# In a real system, this would write to a database stream (e.g., DynamoDB Streams, Kinesis)
print(f"Recorded Event: {event['eventType']} at {event['timestamp']}")
print(f" Payload: {event['payload']}")
return event
def main():
print("--- Event Sourcing Simulation ---")
# Simulate an order creation
order_id = "ORD-001"
record_event("OrderCreated", {"orderId": order_id, "customer": "Alice", "initialItems": []})
# Simulate adding an item
record_event("ItemAdded", {"orderId": order_id, "itemId": "SKU-A", "quantity": 1})
# Simulate updating an item quantity
record_event("ItemQuantityUpdated", {"orderId": order_id, "itemId": "SKU-A", "newQuantity": 2})
# Simulate shipping the order
record_event("OrderShipped", {"orderId": order_id, "shippingProvider": "UPS"})
print("\n--- Event Stream Recorded ---")
if __name__ == "__main__":
main()Benefits of Serverless Patterns
These patterns offer significant advantages for serverless applications:
- Scalability: Easily handle increased load by adding more parallel processes.
- Decoupling: Services operate independently, reducing dependencies and improving resilience.
- Resilience: Failures in one part of a fan-out or scatter-gather workflow don't necessarily stop the entire process.
- Auditability (Event Sourcing): A complete history of changes is invaluable for debugging, compliance, and analytics.
Choosing the Right Pattern
Selecting the correct pattern depends on your specific problem:
- Use Fan-Out when one event needs to trigger multiple independent, parallel actions.
- Use Scatter-Gather when you need to query multiple sources and aggregate their responses.
- Use Event Sourcing when you need a complete, immutable history of changes, or complex temporal queries.
Often, these patterns can be combined within a larger serverless architecture.
Pattern Challenge
A new e-commerce platform needs to process customer orders. When an order is placed, the system must:
- Update inventory.
- Send a confirmation email.
- Generate a shipping label.
- Process payment.
Which serverless architectural pattern is best suited for coordinating these independent tasks after an order is placed?
Patterns Recap
We've explored key serverless architectural patterns: Fan-Out for parallel processing from a single event, Scatter-Gather for aggregating responses from multiple sources, and Event Sourcing for maintaining an immutable history of state changes.
Understanding these patterns helps you design robust, scalable, and resilient serverless applications, choosing the right tool for each complex problem.
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Pola Arsitektur Tanpa Server” gratis?
Ya — teks lengkap “Pola Arsitektur Tanpa Server” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Serverless AWS Lambda Development, upgrade ke CoddyKit PRO. Kursus Serverless AWS Lambda Development mencakup 4 pelajaran total.
Apa yang akan aku pelajari di “Pola Arsitektur Tanpa Server”?
Jelajahi dan terapkan pola arsitektur tanpa server yang umum, seperti fan-out, scatter-gather, dan sumber peristiwa, untuk menyelesaikan masalah bisnis yang kompleks secara efisien. Kamu berlatih Serverless AWS Lambda Development dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.
Apakah aku perlu pengalaman untuk memulai Serverless AWS Lambda Development?
Tidak diperlukan pengalaman sebelumnya. Serverless AWS Lambda Development di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 3 dari 4.
Berapa lama pelajaran “Pola Arsitektur Tanpa Server” memakan waktu?
Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.
Bisakah aku menulis dan menjalankan kode dalam pelajaran Serverless AWS Lambda Development ini?
Ya. Setiap pelajaran Serverless AWS Lambda Development menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.
Semua pelajaran dalam kursus ini
- Penerapan Canary dan Blue/Green
- Membangun Sistem Tanpa Server yang Tangguh
- Pola Arsitektur Tanpa Server
- Optimasi Biaya dalam Arsitektur Tanpa Server