Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Application Centric Microservices Architecture

1,093 views

Published on

The future of you application development platforms, the ability to create applications that are cloud native with elastic services and network aware application policies, and microservices is strategic to your company. When the decision to build you next product is made, Openstack and Microservices became central to your application architectures and becomes strategic to your vision.

Published in: Technology

Application Centric Microservices Architecture

  1. 1. Application Centric Microservices Ken Owens, CTO Cisco Intercloud Services Spark Room – spark-at-ciscolive@cisco.com “Please add me to the DEVNET-1137 room” kenowens12 DEVNET-1137
  2. 2. • Introduction • Why Application Centric • What is Microservices Infrastructure • How do you enable Microservices in the enterprise, cloud, and multiple clouds? • Introducing Shipped • Conclusion Agenda
  3. 3. • Vision of Intercloud • Cisco as a Service • Platform for IoE Introduction Public Clouds Cloud Services and Applications Intercloud Partners VM Portability. Application Centric Policy Control. Partner Ecosystem. Data Virtualization. Open Standards
  4. 4. Why Application Centric?
  5. 5. Developers are Driving the Market  Elastic and “Web-Scale”  Flexible  Reduced time to market for apps  Loosely-coupled components  “Ruthlessly Standardized”
  6. 6. Alignment to Customer Value (Business Outcomes) Services vs Legos Product Alignment vs Project Alignment Fail Fast Organizational Aspects Software Defined Disruption
  7. 7. Practical Examples In The Cloud Cloud must enable application integration, development, and deployment Cloud Native Cloud Valid Legacy Architecture 8
  8. 8. What is Microservices Infrastructure
  9. 9. • Software architecture style • complex applications are composed of small, independent processes communicating with each other using language-agnostic APIs. • Application services are small, highly decoupled and focus on doing a small task. • SOAish • Quick Comparison Microservices Definition
  10. 10. Microservice Advantages (Top of Mind)  Scalability  Resilience / fault isolation  Individual service deployment  Small code base with well defined boundaries.  Flexibility to choose best languages and technologies  Independent development, build and deployment cycle of each Microservice  Enables faster features iteration  Less resistance path to adopt newer technology in future
  11. 11. Micro Services Infrastructure – 0.3
  12. 12. Micro Services Infrastructure
  13. 13. MicroService-1 MicroService-1MicroService-1 (Github repo) MicroService-1 MicroService-1MicroService-2 (Github repo) MicroService-1 MicroService-1Dependency-1 (Marketplace App) MicroService-1 MicroService-1 Dependency-2 (Marketplace App) Deploy Env. (Prod2) Microservices Deployment Layout MicroService-1 (Github repo) MicroService-2 (Github repo) Dependency-1 (Marketplace App) Dependency-2 (Marketplace App) Project MicroService-1 MicroService-1MicroService-1 (Github repo) MicroService-1 MicroService-1MicroService-2 (Github repo) MicroService-1 MicroService-1Dependency-1 (Marketplace App) MicroService-1 MicroService-1 Dependency-2 (Marketplace App) Deploy Env. (Prod1) MicroService-1 MicroService-1MicroService-1 (Github repo) MicroService-1 MicroService-1MicroService-2 (Github repo) MicroService-1 MicroService-1Dependency-1 (Marketplace App) MicroService-1 MicroService-1 Dependency-2 (Marketplace App) Deploy Env. (Staging) Support Namespace aware ( Secure Isolation ) • Deployments • Service Discovery and Wiring. • Load-Balancing Docker containers Mesos – Marathon (MS-Infra) Release [ Build Tag + Config Snapshot ]
  14. 14. Service Discovery & Load Balancer MicroService-1 MicroService-1MicroService-1 (Github repo) MicroService-1 MicroService-1MicroService-2 (Github repo) MicroService-1 MicroService-1Dependency-1 (Marketplace App) MicroService-1 MicroService-1 Dependency-2 (Marketplace App) Docker containers Mesos – Marathon (MS-infra) Deploy Env. (Staging) (MS-Infra) (MS-Infra) Consul Template HAProxy Consul (DNS) Registrator 1. Registrator monitors Docker events 2. Registrator adds docker instances host:port to service-name mapping to consul. 3. Consul exposes information via inbuilt DNS 4. Consult templates watches changes in Consul 5. HAProxy configuration is updated based on changes in consul 6. Namespace naming convention environment.project.service.shipped.com
  15. 15. • Intense focus on application and developer centric Service Design • Exciting new community projects – Build with us:  Project Shipped  microservices-infrastructure  Container networking  OpenStack Congress Application Intent (Policy) It’s NOT just about where Cisco is going. - It’s a movement • Partnering with leading DevOps tool providers: • HashiCorp • Mesosphere • OpenShift PoC and Contribute: • https://github.com/CiscoCloud/microservices- infrastructure • http://developer.cisco.com/Shipped
  16. 16. How do you enable Microservices in the enterprise, cloud, and multiple clouds?
  17. 17. Not so easily… • Organization • Process • It take weeks to create a development environment? Too much cost, red tape, politics • Non-prod environments are so different than prod? • Tests aren’t always accurate • Versioning, updates are way too difficult • Developers can’t get easy access to backend services (databases, security, etc.) • Hard it is to build new and innovative apps at #dayjob? • Software Defined Challenges
  18. 18. Software Defined Developer Challenges Develop • Run multiple services. • Multiple language /technology stack. • Run multiple storage backend. Build • SDLC admin control CI flow bottleneck. • Flexible/dynamic build slaves. • Consistent packaging and version. Deploy • Increased deployment complexity. • Traditional ops to Devops. • Distributed systems. • Service discovery. • Internal load balancing • Multiple tech stack.
  19. 19. • Develop Private and Build and Deploy Everywhere – No Lock- in/No Compromise • Build through CI/CD flow designed for multi-cloud and “bring your own” with consistent packaging and versioning • Easy to deploy with service discovery and automatic service availability • Manage you application and all services from a single interface across private and multi-cloud environments
  20. 20. Introducing Shipped
  21. 21. Video
  22. 22. Demo
  23. 23. Conclusion
  24. 24. • Application Centric • Composible Applications/Microservices • Platform for IoE = Project Shipped
  25. 25. • Experience Project Shipped @ Cisco Live! • Hands on - Hackathon  Use the product  Meet the entire engineering team  Get free GitHub and Bintray private repos Software-Defined Distribution = Project Shipped
  26. 26. 28 Experience Cloud @ Cisco Live Attend other cloud breakout sessions, visit the Cloud Booth in the Cisco Campus (World of Solutions), and in the DevNet Zone
  27. 27. Breakout Session Title Date and Time PSOCLD-1006 Cisco Cloud Architecture on OpenStack Rohit Agarwalla, Technical Lead, OpenStack Tues, Jun 9, 2:30 - 3:30 PM – 23C Upper Level BRKCLD-2003 Building Hybrid Cloud Applications with Intercloud Fabric, Ben Del Vento Wed, Jun 10, 8:00- 10:00 AM 7A Upper Lvl DEVNET-1109 Cisco Executive Panel: All about the Cloud Cisco's Executives Lew Tucker, Faiyaz Shahpurwala and Ken Owens discuss the current and future opportunities around public, private and hybrid clouds. Wed, Jun 10, 9:30 - 10:30 AM DevNet Theater PSOCLD-1004 Cisco OpenStack® Private Cloud (Formerly Metacloud) Niki Acosta, Marketing Manager Wed, Jun 10, 9:30- 10:30 AM – 28D Upper Level BRKCLD-2001 Building Scalable and Highly Available Enterprise Applications on Cisco Cloud Services: Chandra Venkatapathy, Ken Schroeder, Technical Staff, CSG Wed, Jun 10, 1:00- 3:00 PM 25C Upper Level Cisco Live 2015 Cloud Breakout Sessions Breakout Session Title Date and Time BRKCLD-1004 End-to-end Cloud Management: A holistic approach for developing and managing the platform and service offerings that transform IT: Ben Del Vento Wed, Jun 10, 3:30- 5:00 PM 24C Upper Lvl BRKCLD-1002 Cloud Onboarding - Jeff Minson; Abhi Sing, Technical Solutions Architects, CMS Thurs, Jun 11, 8:00- 9:30 AM, 30E Upper Lvl BRKCLD-1828 Designing Hybrid Cloud operations with ServiceGrid and Intercloud Fabric Ben Del Vento Thurs, Jun 11, 8:00- 9:30 AM 25C Upper Lvl BRKCLD-1003 A Practical Introduction to DevOps Practices and Tools: Christopher Jackson, Vallard Benincosa Thurs, Jun 11, 1:00- 2:30 PM 28C Upper Lvl LTRCLD-2011 Intercloud Fabric - Configuring and Deploying Hybrid Cloud Solutions: Chris Martin
  28. 28. Cloud @ DevNet Sessions Theater Classroom
  29. 29. Thank you

×