Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Apidays Paris 2023 - API Security Challenges fo...

apidays
January 09, 2024

Apidays Paris 2023 - API Security Challenges for Cloud-native Software Architects, Pierre Versali, Devoteam

Apidays Paris 2023 - Software and APIs for Smart, Sustainable and Sovereign Societies
December 6, 7 & 8, 2023

API Security Challenges for Cloud-native Software Architects
Pierre Versali, Cloud-native Software Architect | Principal Consultant at Devoteam

------

Check out our conferences at https://www.apidays.global/

Do you want to sponsor or talk at one of our conferences?
https://apidays.typeform.com/to/ILJeAaV8

Learn more on APIscene, the global media made by the community for the community:
https://www.apiscene.io

Explore the API ecosystem with the API Landscape:
https://apilandscape.apiscene.io/

apidays

January 09, 2024
Tweet

More Decks by apidays

Other Decks in Programming

Transcript

  1. ü Loose Coupling ü Integration ü Collaboration ü Standardization ü

    Developer Experience ü Testability API Benefits
  2. API Protocol Message Format Specification Synchronous SOAP XML SOAP REST

    over HTTP JSON OpenAPI GraphQL GraphQL GraphQL gRPC over HTTP/2 Protobuf gRPC Asynchronous Event Broker Pub / Sub Kafka / MQTT JSON Protobuf Avro Thrift AsyncAPI WebSockets API – Protocols | Message Formats | Specification Standards and Best Practices
  3. ü Separation of Concern ü Diversity in Technology Stack ü

    Isolation ü Reusability ü Flexibility / Scalability ü Reliability Microservices Benefits
  4. • Complexity • Security • Performance • Evolutivity • Deployment

    • Data Consistency • Resilience • Fault Tolerance • … 🤯 Microservices concerns
  5. API Conversation Pattern Synch Graph Async Messaging (Pub/Sub) Processes Data

    Consistency Eventual Consistency Choreography / Orchestration Event-Sourcing CQRS Fault-Tolerance Process Management State Management Retry / Rollback Data storage Relational Data Key-Value Event-Driven Microservices problems
  6. Node 2 Node 3 Node 1 … Container Orchestration Configuration

    Availability Provisionning Scaling Automation Resource Allocation Load Balancing Health Monitoring
  7. • Key Vault • GitOps • Platform Engineering • SRE

    • FinOps Infrastructure as Code – Going further
  8. Containers Orchestration API-First Development Reactive Microservices Cloud-native Software on Steroïds

    IaC / GitOps / FinOps Platform / SRE Dev Ops Security Domain Driven Design Observability MFA IAM
  9. There is not a single or clear way for designing

    Software Architecture Software Architecture is at the edge between Business Goals, Functional Requirements, Hardware Capabilities and… your Budget! Takeaway
  10. • Architecture decisions are tough • Architecture decisions always come

    with trade-offs • Architecture decisions always require effort (and sometimes pain) • Architecture decisions require compromise • Architecture decisions should always be balanced • Changes require to adapt Takeaway