Presentation for taste of it 2014 wide - no clients
0 likes646 views
The document discusses the concept of Platform as a Service (PaaS), highlighting its advantages such as flexible deployment of applications and consumption-based economics. It outlines best practices for adopting cloud services, offers insights into emerging management systems like Azure, and emphasizes the importance of structured training and support. The presentation concludes by encouraging initial small-scale pilots to refine the approach and ensure successful implementation.
Presentation for taste of it 2014 wide - no clients
- 1. us.sogeti.com1 Why Platform as a Service November 12, 2014 Bob LeRoy Vice President – Software Development Sogeti USA 4445 Lake Forest Dr. Wuite 550 Cincinnati, OH 45242 513-884-3612 Email: robert.leroy@us.sogeti.com
- 2. us.sogeti.com2 Introduction • 30 Years in App Dev • VP of Software Development for Sogeti • 500+ Team Members • Experience with large systems based on Microsoft and Java Sogeti Labs Fellow and one of 600 Capgemini ExpertConnect Members
- 3. us.sogeti.com3 New Models for Applications Delivered Rapidly Updated Frequently Responsive Multi- Device Open & Integrated Distributed Features Lightweight Adaptable Intuitive Beautiful Feature Sets Rich Client Mobile Device API Membership Sign-up Member Admin Panel Share text, photos, etc. Tagging Advertising Module Private Messaging Statistics Search Polls
- 4. us.sogeti.com4 Definition of Platform as a Service Infrastructure •Virtual Server •Operating Environment and applications are deployed •Can include Storage-as-a- service Platform •Operating Environment included •Development with Windows/.Net or Linux/Java •Databases, Communications and Frameworks •3rd party services Software •Operating Environment is irrelevant •Fully functional applications •CRM, ERP, Email
- 5. us.sogeti.com5 Consumption Economics – Why “as-a-Service” $0 $1 $2 $3 $4 $5 $6 Consult Design Implement Integrate Maintain Manage Adopt CapEx OpEx Plan Design Implement Integrate Maintain Manage Adopt Buy Use Total Spend Is equal Buy and Use
- 6. us.sogeti.com6 Evolution of Sogeti Patterns ASP.Net MVC • Sogeti Application Reference Architecture (SARA) MVVM • Modified to become SARA2 PaaS • Transition away from Patterns to Architecture Guidelines Waterfall Iterative Agile
- 7. us.sogeti.com7 Leaders in Platform-as-a-Service • Development Environments are provisioned in the cloud • Traditional languages are still supported • Latest frameworks are immediately available • Most still use existing IDE’s Java.NetOther
- 8. us.sogeti.com8 Model Driven Development 0 2 4 6 8 10 12 14 16 18 Hours per Function Point Modeling Java C#
- 9. us.sogeti.com9 New Management Systems – BlueMix
- 10. us.sogeti.com10 New Management Systems - Azure
- 11. us.sogeti.com11 New Management Systems – OneShare
- 12. us.sogeti.com12 What to Expect when using PaaS -- How to Get StartedDATAPROVIDEDBYSTANDARDS Expertise, best practices & training for moving/building in the cloud Continuous improvement for cloud apps & offerings Drive, align & monitor cloud adoptionIdentify, assess & recommend cloud adoption opportunities What is in our scope? Where do we start? When can we go? How do we get there? Is this better? Why are we doing this?
- 13. us.sogeti.com13 What to Expect when using PaaS – By Domain Domain Impact Resolution People Learning Curve Follow existing standards Structured education plans Disagreement on Guidelines Document the decisions with pros and cons Process Fragmented framework usage Set guidelines early Update the SDLC process Project charters, Testing, Deployments Changes to deployment/monitoring Work with your Infra team Technology Unexpected performance issues Test thoroughly unit, functional and load Missing components Plan for unexpected delays Limited support Purchase support plans from vendors
- 14. us.sogeti.com14 What to Expect when using PaaS - Azure • Applications read data from a read- only data cache. • Application clients post changes to a queue. • The queue is read and changes are dispatched to applications/services, which change their own data. • Changes to data (or triggers) are placed on a queue. • The data changes are posted to the read-only data.
- 15. us.sogeti.com15 Sogeti Accelerators - Azure • Multithreaded queue manager • Better resource utilization • $ Savings Queue Manager • Highly secure SAS Service for accessing Blobs • Validations for file extensions • Name smudging SAS Service • WCF Services availability analyzer • Service Load analyzer • Rerouting and balancing logic Custom Load Balancer • Client Id Generator Service • Token generator Service • API Access validation against the Token API Hosting Service •Storage •Wire •Authorization •Auditing HBI Data Handlers •Claim Unaware to ClaimAware application transformation •Use of Standardized Authentication Service •Common Code for the authentication ClaimAware Component •Azure resource creation automation •Multitenant Service •Usage of PowerShell Desired State Configuration (DSC) Infrastructure as Code (IaC) •Script for Software load balancer configuration •Sticky session configuration for Tridion etc. IIS ARR Configurator
- 16. us.sogeti.com16 Next Steps After This Presentation Proof of Concept •Set Expectations •Unknown Results Rationalizations •Review Backlog •Select Platform Pilot •Start Small •Iterate Quickly SDLC Updates •Configuration Management •Test Processes Center of Excellence •Maintain Guidelines •Team Education The secret of getting ahead is getting started. Mark Twain Outcomes Based
- 17. us.sogeti.com17 Continue the conversation on everything Sogeti and IT: Like us on Facebook; follow us on Twitter @Sogeti_USA, @robert_leroy. Read our blog at http://labs.sogeti.com IT is Possible™ … Now let’s get started.
Editor's Notes
- #3: Funny Start Sogeti Commercial Part of the Capgemini Group 130,000 Sogeti has 20K, USA Head Quarters in Dayton, USA has 2,000 Cap focuses more on business strategy, we are technology focused. They travel 100% of their time, we are local providers We go across the entire SDLC from Analysis, Design, Development, Testing and Infra using a wide variety of tools and technologies.
- #4: Apple changed the game for Software Engineers. Clients want everything fast with frequent updates. Think Minimally Viable Product. The applications must run everywhere. This was Java’s promise. Solutions are open & integrated to each other. Salesforce. Features are distributed by platform but must be designed for extended use (explain the table). No one wants heavy, monolithic applications, We want solutions to be lightweight and free. Oh and they better be attractive or I’m not interested.
- #6: Author of Consumption Economics is JB Wood, Todd Hewlin, Thomas Lah, Technology Services Industry Association Capital expenditures are hard to secure, take time to implement. We have buy them long before we use them. SaaS is a just-in-time model. Buy only what you need, when you need it. Highlight the ability to drop test/dev and save money when not being used. Note that total spend will cross if use of all environments is heavy for a long durations.
- #7: Maybe talk about years Key message is that we’re less strict now Describe the difference between SARA source code and Sogeti guidelines
- #8: Strengths and weakness of the tools in a visual manner? Maybe talk about the languages supported?
- #9: Producer/consumer model. We’ve been here before. Why now? Make it funny.
- #10: BlueMix status site
- #11: Azure Status Page
- #12: OneShare. Unique Sogeti application to shutdown applications when they are idle between specific time periods.
- #13: Start with big picture then go into the data
- #14: Lots of data here, pick a couple to highlight.
- #15: Talk through the process and highlight why this is an issue.
- #16: Pick two or three key components; discuss the issues and the benefits Mention that Microsoft hasn’t already addressed these.
- #17: Talk about all phases but go deep on only a few. Address the benefits at each step.