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

Serverless - the way microservices should be - ...

Serverless - the way microservices should be - OdessaJS

Ivan Jovanovic

July 07, 2018
Tweet

More Decks by Ivan Jovanovic

Other Decks in Technology

Transcript

  1. Monolith - Pros • Setup • One app to maintain

    • Deployment • Shared memory between functionalities • Monitoring, logging • Adding new functionalities
  2. Monolith - Cons • Extending app without breaking other stuff

    • Slow delivery and deployments • Large codebase to maintain • Hard to understand • Slower development as it evolves
  3. Microservices - Pros • Service independence • Async communication between

    services • Independent deployment • Easier to understand, develop and test • Speeds up development • Enables continuous delivery and deployment
  4. Serverless computing is a cloud- computing execution model in which

    the cloud provider dynamically manages the allocation of machine resources.
  5. Serverless - Pros • Setup, no provision needed • Simplifies

    packaging and deployment • Cost is small • Reduces the complexity • Automatic scaling
  6. Serverless - Cons • Vendor lock in (but doesn’t need

    be) • No guarantee where will function be executed • Takes some time to handle first request - cold time
  7. How does serverless “kill” DevOps? • No need to write

    any setup code, no containers, orchestration, nothing • Simple deployment • Functions are so small, no space for mistakes • It doesn’t “kill” DevOps, it just takes it to the next level
  8. Conclusion • Serverless, not just a buzzword • Pick provider

    and tools that you want • Free autoscaling • Have you infrastructure as a code • Fast development, deployment and delivery