How many usersat what time ?
- Resources needs to be scaled quickly enough !!!
8.
• Businesses todayuse a host of SaaS applications — the average
business uses 137, according to Blissfully’s 2020 SaaS Trends report.
• Those applications generate terabytes of data.
• Also, the data in multiple platforms can be related — such as an
address on a credit card used for an ecommerce purchase, which is
also useful as an address for a shipping platform — and that
ecommerce transaction itself can be tracked by a company’s analytics
platform.
• Businesses have two broad choices when it comes to rolling out
technology stacks: deploy a single platform that combines many
functions, or take a best-of-breed approach that uses microsystems to
integrate discrete services from different vendors.
9.
What is monolithicarchitecture?
• Monolithic applications are designed to handle multiple related tasks.
They’re typically complex applications that encompass several tightly
coupled functions.
• For example, consider a monolithic ecommerce application. It might
contain a web server, a load balancer, a catalog service that services up
product images, an ordering system, a payment function, and a
shipping component.
• As you can imagine, given their broad scope, monolithic tools tend to
have huge code bases. Making a small change in a single function can
require compiling and testing the entire platform, which goes against
the agile approach today’s developers favor.
10.
What are microservices?
•In contrast to the monolithic approach, a microservices architecture
involves smaller applications deployed independently as loosely coupled
services, tied together through application integration.
• With microservice applications, the business logic may encompass multiple
platforms, including software as a service, on-premises databases, and in-
house-developed applications that meet needs that no application
handles.
• From a software engineering perspective, microservices can be simpler to
develop. They’re smaller in scope and therefore smaller in size, which
makes it easier for developers to improve them through continuous
integration and continuous delivery (CI/CD). They can be written in any
programming language. And they can communicate with other
microservices through APIs.
Business Drawbacks
▶ One-waycommunication
▶ Customer is in control
▶ Website is idle when user is idle
▶ Limited window of opportunity to interact
▶ Reduced scope for ancillary revenue
18.
Technical Drawbacks
▶ Resultsin dependencies
▶ Failure affects everything
▶ Change is slow
▶ Scale is expensive (minor features require unilateral scale)
▶ Steep learning curve
▶ Technology stack is limited to specific skillsets
▶ Introduces legal pitfalls (PCI DSS, Compliance)
▶ Duplicated components due to lack of explicit boundaries
▶ Rigid – likely to break under pressure
Business Benefits
▶ Two-waycommunication
▶ We’re in control (think Google)
▶ APIs are always working
▶ Unlimited opportunities to interact
▶ Broader scope for ancillary revenue
25.
Technical Benefits
▶ Eliminatesdependencies
▶ Failure is isolated
▶ React to change quicker
▶ Scale is less expensive (APIs scale individually)
▶ More intuitive learning curve
▶ Technology stack is not limited to specific skillsets
▶ Shielded from legal pitfalls
▶ Reusable components
▶ Flexible – will bend rather than break under pressure
![[WSO2Con EU 2017] Microservices for Enterprises](https://cdn.slidesharecdn.com/ss_thumbnails/buildingapragmaticmicroservicearchitecture-171108114640-thumbnail.jpg?width=560&fit=bounds)
