1 / 26

Transforming Business with Microservices

Learn how microservices can fuel innovation, break the monolith, and transform your business. Discover best practices and potential gotchas. Join us for an informative session with Anil Allewar, Director of Engineering at Synerzip.

jonell
Download Presentation

Transforming Business with Microservices

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Transforming Business with Microservices

  2. About Me! • Anil Allewar • Director Of Engineering @ Synerzip • Technology Evangelist & speaker • Core interests: Cloud, Enterprise, Mobile

  3. Agenda • What are Microservices? • Breaking the Monolith • Fueling Innovation • Best practices & Gotchas • Questions?

  4. Software Architecture Evolution http://www.kanbansolutions.com/blog/microservices-architecture-friend-or-foe/

  5. Monolith

  6. Microservices

  7. Crux of Microservices Bounded business context

  8. Agenda • What are Microservices? • Breaking the Monolith • Use Case - Fueling Innovation • Best practices & Gotchas • Questions?

  9. Why? Unintended side effects Release – 4 months Monolith Quicker competitors Go-live firefighting 3-4 months gestation Fear of release Horizontal scaling Recruitment

  10. Chipping The Monolith

  11. Key Takeaways • Attempt Microservices to transform your business • Microservices will trigger organization change • Learning organization • Deliberate & discuss – benefits v/s risks • Versioning of contracts between services • Dormant Monolith • Automation and DevOps intrinsic to Microservices

  12. Agenda • What are Microservices? • Use Case - Breaking the Monolith • Use Case - Fueling Innovation • Best practices • Gotchas • Questions?

  13. Why? • Culture of Innovation • Build MVP based on customer interactions and perceived pains • Solicit customer feedback • Shut down, Continue or Pivot the MVP based on feedback • Lots of small products – mostly independent but can have common functionality • Each product has unique problems – diverse tools and technologies

  14. Solution AWS Cloudwatch Container Orchestration Github Registry Dashboard Security Metering Config Server Registry/Discovery Log Aggregator Product B - UI Product A - UI Common Service A AWS ELB API Gateway Glue code Glue code Common Service B Product B - Webservice Product A - Webservice Glue code Glue code Load Bal Routing

  15. Key Takeaways • Monolith first - Version 1.x of system • Domain driven design– services with well defined seams • Peel off Microservices once complexity and scaling needs affect productivity & innovation • Invest in product management and QA • Containers & Orchestration

  16. Agenda • What are Microservices? • Use Case - Breaking the Monolith • Use Case - Fueling Innovation • Best practices & Gotchas • Questions?

  17. Note! • Upfront planning & decomposition of business services - else spaghetti architecture • Avoid distributed monolith – Things that change at the same time should be in the same service • Monitoring Microservices is order of magnitude harder – deployment map & health status • Centralized logging, alerting and distributed tracing - critical to debug & resolve production issues • Circuit breakers to prevent chain of failure

  18. Note! • Issue in service A could be because of input from service B or messaging queue - APM tools & strong service contracts to isolate root cause • Services graph - Dependency and version management • IT Governance – streamline tools & methodology • Track what service API gets exposed and their security • Consumer driven contracts for robust API – check out Pact / PactJVM

  19. Conclusion • Microservices - loved both by developers and by business. • It has high initial costs but if done right, the results are worth it! • Most of the large enterprises have embraced or are moving to Microservices – Netflix, Amazon, Gilt, eBay • Startups – start with Monolith and move to Microservices once scaling & agility issues surface

  20. Agenda • What are Microservices? • Use Case - Breaking the Monolith • Use Case - Fueling Innovation • Best practices & Gotchas • Questions?

  21. Contact Me

  22. AshishShanker ashish.shanker@synerzip.com @ShankerAshish +1.214.507.2843 • 22

  23. Synerzip • Accelerate the delivery of your product roadmap • Address technology skill gaps • Save at least 50% with offshore software development • Augment your team with optional on-site professionals Your trusted outsourcing partner for Agile software product development.

  24. Synerzip Clients

  25. Connect with Synerzip facebook.com/Synerzip @Synerzip linkedin.com/company/synerzip

  26. Next Webinar Preventing Botnet Attacks on Wednesday, February 15, 2017 at Noon CST Webinar Presenter: KiranRatnaker, Director IT at Synerzip

More Related