John Weston rolling deck (info + trivia)john weston
This document appears to be a collection of slides from a Microsoft productivity event. It includes an agenda, polls, and brief technical questions. Information provided includes details on Bill Gates retiring from Microsoft, the most popular Microsoft Office command, and when GPS became available for commercial use. Contact information is also provided for following up on the event.
A Digital Conversation Meetup, June 2014. The closing presentation of the evening was shared by Adam Sefton.
Talking on the subject of complexity of the Next Web, he suggested instead of worrying about trying to organise and control this world, both digital and offline, we should embrace complexity (unicorns and all) and allow solutions to evolve and emerge naturally.
Adam Sefton is Global Executive Creative Director at Reading Room. He's been working in digital on a variety of levels for over 10 years, the last 6 in senior agency positions. He is excitable, energetic and enthusiastic about the internet, how people like to use it and what might happen to it in the future. He is returning to discuss how the emergent principles and technologies underlying the next iteration of the web should influence organisations digital strategies. What are the challenges and opportunities facing digital decision makers.
This document discusses the concept of "open" as it relates to open source software and open cloud computing. It explores different definitions of open, including the four freedoms that define open source. It also addresses questions around who benefits from openness and how business models have evolved around open source. The document encourages questioning assumptions and perspectives on openness.
Ember (along with a whole family of related open source tools) is steadily reducing the cost of shipping sophisticated applications. By making it easier to compose applications out of high-level, shared pieces, and deploy them on demand to commodity hosting, we've been sowing the seeds for a revolution in how software gets built and paid for. This is a talk about both the technical "how" -- including the latest work in the Cardstack project -- and the "why": our opportunity to grow an open, decentralized software ecosystem that can sustainably pay for open source while respecting user freedom.
Do you want to be a Cloud Architect ? Are you stuck in a Sysadmin / DBA job ,and want to transition into the Cloud? Are you interested , but do not know how/where to start ? Then, you are in the right place . This is Part 1 of a 3-Part series , where I share the secret sauce how best to get started on the journey to become a Cloud Architect , and enhance your career.
This document summarizes Andrew Clay Shafer's talk on software processes. It discusses that Agile processes like Scrum have been oversimplified and lost their original spirit. It promotes focusing on frequent delivery, automated testing, minimizing work in progress, prioritizing quality, and inspecting and adapting processes based on outcomes. Context is important in choosing a process, and processes should promote building software to fulfill a vision rather than just completing tasks. Measuring outcomes and having conversations around user stories are also discussed.
Do you want to be a Cloud Architect ? Are you stuck in a Sysadmin / DBA job ,and want to transition into the Cloud? Are you interested , but do not know how/where to start ? Then, you are in the right place . This is Part 1 of a 3-Part series , where I share the secret sauce how best to get started on the journey to become a Cloud Architect , and enhance your career.
Cloud 2.0: "Code" is no longer king - Serverless has dethroned itPaul Johnston
It is no longer how good a coder or developer you are that defines whether you will be successful in the cloud 2.0 era, but how you understand your role in the context of your Business and the value you provide to it. This is what will set apart the future Developers. This is what Serverless is all about.
John Weston rolling deck (info + trivia)john weston
This document appears to be a collection of slides from a Microsoft productivity event. It includes an agenda, polls, and brief technical questions. Information provided includes details on Bill Gates retiring from Microsoft, the most popular Microsoft Office command, and when GPS became available for commercial use. Contact information is also provided for following up on the event.
A Digital Conversation Meetup, June 2014. The closing presentation of the evening was shared by Adam Sefton.
Talking on the subject of complexity of the Next Web, he suggested instead of worrying about trying to organise and control this world, both digital and offline, we should embrace complexity (unicorns and all) and allow solutions to evolve and emerge naturally.
Adam Sefton is Global Executive Creative Director at Reading Room. He's been working in digital on a variety of levels for over 10 years, the last 6 in senior agency positions. He is excitable, energetic and enthusiastic about the internet, how people like to use it and what might happen to it in the future. He is returning to discuss how the emergent principles and technologies underlying the next iteration of the web should influence organisations digital strategies. What are the challenges and opportunities facing digital decision makers.
This document discusses the concept of "open" as it relates to open source software and open cloud computing. It explores different definitions of open, including the four freedoms that define open source. It also addresses questions around who benefits from openness and how business models have evolved around open source. The document encourages questioning assumptions and perspectives on openness.
Ember (along with a whole family of related open source tools) is steadily reducing the cost of shipping sophisticated applications. By making it easier to compose applications out of high-level, shared pieces, and deploy them on demand to commodity hosting, we've been sowing the seeds for a revolution in how software gets built and paid for. This is a talk about both the technical "how" -- including the latest work in the Cardstack project -- and the "why": our opportunity to grow an open, decentralized software ecosystem that can sustainably pay for open source while respecting user freedom.
Do you want to be a Cloud Architect ? Are you stuck in a Sysadmin / DBA job ,and want to transition into the Cloud? Are you interested , but do not know how/where to start ? Then, you are in the right place . This is Part 1 of a 3-Part series , where I share the secret sauce how best to get started on the journey to become a Cloud Architect , and enhance your career.
This document summarizes Andrew Clay Shafer's talk on software processes. It discusses that Agile processes like Scrum have been oversimplified and lost their original spirit. It promotes focusing on frequent delivery, automated testing, minimizing work in progress, prioritizing quality, and inspecting and adapting processes based on outcomes. Context is important in choosing a process, and processes should promote building software to fulfill a vision rather than just completing tasks. Measuring outcomes and having conversations around user stories are also discussed.
Do you want to be a Cloud Architect ? Are you stuck in a Sysadmin / DBA job ,and want to transition into the Cloud? Are you interested , but do not know how/where to start ? Then, you are in the right place . This is Part 1 of a 3-Part series , where I share the secret sauce how best to get started on the journey to become a Cloud Architect , and enhance your career.
Cloud 2.0: "Code" is no longer king - Serverless has dethroned itPaul Johnston
It is no longer how good a coder or developer you are that defines whether you will be successful in the cloud 2.0 era, but how you understand your role in the context of your Business and the value you provide to it. This is what will set apart the future Developers. This is what Serverless is all about.
Do you want to be a Cloud Architect ? Are you stuck in a Sysadmin / DBA job ,and want to transition into the Cloud? Are you interested , but do not know how/where to start ? Then, you are in the right place . This is Part 1 of a 3-Part series , where I share the secret sauce how best to get started on the journey to become a Cloud Architect , and enhance your career.
DevOps and the cloud: all hail the (developer) king - Daniel Bryant, Steve PooleJAXLondon_Conference
1) The document discusses the rise of microservices and DevOps approaches in application development and deployment. It notes both the promises and challenges of these approaches, including increased complexity and the need for new tooling.
2) It describes lessons learned from early adoption of microservices, such as the problems that can arise from shared data stores and monolithic upgrades.
3) The document advocates for a "safety first" mindset with DevOps, emphasizing the importance of security, compliance, and understanding where data is located in cloud environments.
The document summarizes the experiences of an implementation team at the University of Baltimore in installing and using a new discovery system called EDS. It provides quotes from team members about various aspects of the implementation process. While there were some complications, the team was able to work through issues and felt the system worked well overall for students and faculty once in place. The team highlighted effective communication and keeping the implementation simple as important factors in the project's success.
This document discusses migrating production backends with zero downtime using the example of Theseus' ship. It explains that as the planks of Theseus' ship were replaced over time, some philosophers argued the ship remained the same while others argued it was not the same ship. The document then discusses challenges in data modeling as business needs and data access patterns change over time. It argues for treating data models as temporal and contextual to deal with "ontological semantic drift".
The document provides an overview of Windows 7 and its impact on end users and businesses. It discusses key features of Windows 7 like improved performance, a simplified user interface, and enhanced security. It also summarizes new capabilities for digital media, mobility, and networking. The document then covers Microsoft Office 2010 and web-based Office applications.
The document provides an overview and summary of Windows 7 and Office 2010 from Paul Thurrott, a technology analyst.
For end users, Windows 7 improves performance and usability over Vista with a simpler interface, taskbar changes, and desktop effects. Businesses benefit from improved security, reliability, and remote access features. Office 2010 focuses on accessibility across devices with online versions of core apps and improved document sharing. The document also briefly outlines Thurrott's book "Windows 7 Secrets" and previews upcoming web versions of Office apps.
Reactive Microservice Architecture with Groovy and GrailsSteve Pember
Steve Pember gave a presentation on reactive oriented architecture with Grails and Groovy. He discussed some key points:
1. Monolithic applications will not scale well as they grow in complexity, which can negatively impact development and maintenance.
2. Service oriented architecture (SOA) and microservices can help break applications into independent components, but SOA implementations have issues like increased complexity from interconnected services.
3. Architecture choices are more important than any specific framework. Microservices aim to distill SOA principles by focusing each component on a single context to reduce complexity.
Moving to Microservices with the Help of Distributed TracesKP Kaiser
Moving away from a monolith to a microservices architecture is a process fraught with hidden challenges. There's legacy code, infrastructure, and organizational processes that all need to change, in order to make the switch successful.
But microservices come with a huge increase in infrastructure complexity. We'll see how distributed traces empower developers to work with greater autonomy, in increasingly complex deployment environments.
Tom Leach and Travis Thieman of GameChanger talk about their experiences migrating their build and deploy pipeline from being heavily based on Chef to one based around Docker.
This presentation is split in to two main sections. The first section covers the motivations for why GameChanger, as a fast-growing startup, identified a need to replace it's existing Chef-based deploy model with a model which reduces deploy-time risk and allows its engineering team to scale.
The second section is a high-level walkthrough of the new GameChanger deploy pipeline based around Docker.
It's easy to say... Microservices! Reality is we need to learn and apply concepts coming from many disciplines like SOA, EDA and DDD just to name a few! Mix them with some ALM and technical processes around Packaging and Deploying... and maybe then you get a true Microservices solution.
What is the ‘Cloud’? Today almost every self-proclaimed industry pundit who attempts to describe cloud computing talks about ‘elasticity’ or how magically new servers appear in the cloud with a swish of a magic wand!
But, is that all we get with cloud computing?! What is wrong or missing in today’s software world? Didn’t we build and run software for the past 50+ years? Why do we need this cloud computing all of a sudden? This whitepaper attempts to answer whether cloud computing is the right strategy for you and your enterprise. The intent of this paper is not to try and compare various cloud offerings (either Azure or Amazon), the objective is to sow new ideas in your mind and the intent is to explain in layman’s terms how cloud computing is silently revolutionizing our 50 year old industry.
Dewey Sasser discusses maintaining operational sanity in a cloudy DevOps world for a major gaming company that has transitioned all its services to public clouds like AWS. The company aims for 100% uptime and no maintenance downtime using a model where development teams are responsible for their services and a central cloud team provides shared tools and best practices. Key aspects are automated user access control using rules and workflows, tagging for cost control, and putting power in developers' hands while keeping responsibility with their teams.
The presentation "Agile Architecture in a Modern Cloud-Native Ecosystem" by Turja N Chaudhuri.
Recording of the presentation: https://www.youtube.com/watch?v=d4kGI3ARn5o
Details of the event: https://www.meetup.com/Cloud-Study-Network/events/283988261/
Accompanying presentation for Cloud Study Network group (https://www.meetup.com/Cloud-Study-Network/) :
Event link - https://www.meetup.com/Cloud-Study-Network/events/283988261/
hosted on 24.02.2022 , at https://www.youtube.com/watch?v=d4kGI3ARn5o
The document discusses development and QA dilemmas in DevOps. It notes that traditionally development was done separately from testing and production environments, but with DevOps there is a focus on continuous delivery through automated pipelines. It acknowledges this is a big change that makes some developers and testers uncomfortable by removing safety nets. It emphasizes that DevOps is about culture and practices, not specific technologies, and that these practices can be used on-premises. It provides examples of how to handle database schema changes and feature rollouts transparently in production. It stresses measuring outcomes through metrics and analytics to learn from users and improve products iteratively.
A Software Problem (and a maybe-solution)YangJerng Hwa
The document discusses problems in the software engineering field and proposes solutions. It identifies 4 main problems: 1) unsophisticated users require requirements analysts to create specifications, 2) non-programmers require programmers to develop minimally viable programs from specifications, 3) non-systems engineers require engineers to modify programs for scalability, and 4) a lack of standards leads to inefficient development. The document proposes addressing these by developing: A) a shared data structure, B) a user interface, C) a platform for minimal programs, D) software to generate standards-compliant applications, and E) framework extensions to guide further development. Ultimately, the document argues that vertically integrating software development from startups to enterprises could help solve large
This goal of this presentation is to present the rationale behind containers and how they can help you simplify your infrastructure and reduce cost and complexity. In this presentation I am showing the history and reasoning behind this technology which is used by world leading companies and how you can bring this technology and paradigm to bear to build distributed, fault tolerant, scalable solutions. This is only one of my many publications/solutions.
Accelerate your Application Delivery with DevOps and MicroservicesAmazon Web Services
DevOps aims to accelerate application delivery by breaking down silos between development and operations teams. It promotes continuous integration, delivery, and deployment to production through automation and monitoring. Microservices help achieve this by decomposing applications into independently deployable components to improve scalability, innovation, and failure isolation. While challenging, DevOps and microservices can help organizations deliver value faster and improve customer experiences.
The speaker discusses how Lookout has scaled its engineering organization and technical infrastructure over time. In 2011, Lookout had problems with unreliable deployments and a monolithic codebase. It introduced new tools like JIRA, Jenkins, and Git/Gerrit to improve its workflow. It also automated deployments and now has a much higher success rate. As Lookout has grown, it has moved to a more distributed architecture with over 100 microservices running on different technologies. Scaling organizational knowledge and coordinating many independent services will be ongoing challenges.
The document discusses ATMOS, a cloud-based content retrieval library. Some key points:
1) ATMOS provides the benefits of cloud computing like convenient APIs, simple metadata-based retrieval and classification, high reliability and security.
2) Using ATMOS as the basis for a content retrieval system could help solve problems with data manipulation and add more universality to retrieval, allowing both machine and manual indexing.
3) The library presented retrieves images that are visually or cognitively similar to a sample image provided by the user, ignoring weak image noises and prioritizing similar shapes and edges.
What Should I Do? Choosing SQL, NoSQL or Both for Scalable Web ApplicationsTodd Hoff
This is the slidedeck I used for a webinar (http://voltdb.com/choosing-sql-nosql-or-both-scalable-web-apps-webinar) I gave on helping people choose SQL or NoSQL for building scalabile web applications. Hint, the answer is: both.
Do you want to be a Cloud Architect ? Are you stuck in a Sysadmin / DBA job ,and want to transition into the Cloud? Are you interested , but do not know how/where to start ? Then, you are in the right place . This is Part 1 of a 3-Part series , where I share the secret sauce how best to get started on the journey to become a Cloud Architect , and enhance your career.
DevOps and the cloud: all hail the (developer) king - Daniel Bryant, Steve PooleJAXLondon_Conference
1) The document discusses the rise of microservices and DevOps approaches in application development and deployment. It notes both the promises and challenges of these approaches, including increased complexity and the need for new tooling.
2) It describes lessons learned from early adoption of microservices, such as the problems that can arise from shared data stores and monolithic upgrades.
3) The document advocates for a "safety first" mindset with DevOps, emphasizing the importance of security, compliance, and understanding where data is located in cloud environments.
The document summarizes the experiences of an implementation team at the University of Baltimore in installing and using a new discovery system called EDS. It provides quotes from team members about various aspects of the implementation process. While there were some complications, the team was able to work through issues and felt the system worked well overall for students and faculty once in place. The team highlighted effective communication and keeping the implementation simple as important factors in the project's success.
This document discusses migrating production backends with zero downtime using the example of Theseus' ship. It explains that as the planks of Theseus' ship were replaced over time, some philosophers argued the ship remained the same while others argued it was not the same ship. The document then discusses challenges in data modeling as business needs and data access patterns change over time. It argues for treating data models as temporal and contextual to deal with "ontological semantic drift".
The document provides an overview of Windows 7 and its impact on end users and businesses. It discusses key features of Windows 7 like improved performance, a simplified user interface, and enhanced security. It also summarizes new capabilities for digital media, mobility, and networking. The document then covers Microsoft Office 2010 and web-based Office applications.
The document provides an overview and summary of Windows 7 and Office 2010 from Paul Thurrott, a technology analyst.
For end users, Windows 7 improves performance and usability over Vista with a simpler interface, taskbar changes, and desktop effects. Businesses benefit from improved security, reliability, and remote access features. Office 2010 focuses on accessibility across devices with online versions of core apps and improved document sharing. The document also briefly outlines Thurrott's book "Windows 7 Secrets" and previews upcoming web versions of Office apps.
Reactive Microservice Architecture with Groovy and GrailsSteve Pember
Steve Pember gave a presentation on reactive oriented architecture with Grails and Groovy. He discussed some key points:
1. Monolithic applications will not scale well as they grow in complexity, which can negatively impact development and maintenance.
2. Service oriented architecture (SOA) and microservices can help break applications into independent components, but SOA implementations have issues like increased complexity from interconnected services.
3. Architecture choices are more important than any specific framework. Microservices aim to distill SOA principles by focusing each component on a single context to reduce complexity.
Moving to Microservices with the Help of Distributed TracesKP Kaiser
Moving away from a monolith to a microservices architecture is a process fraught with hidden challenges. There's legacy code, infrastructure, and organizational processes that all need to change, in order to make the switch successful.
But microservices come with a huge increase in infrastructure complexity. We'll see how distributed traces empower developers to work with greater autonomy, in increasingly complex deployment environments.
Tom Leach and Travis Thieman of GameChanger talk about their experiences migrating their build and deploy pipeline from being heavily based on Chef to one based around Docker.
This presentation is split in to two main sections. The first section covers the motivations for why GameChanger, as a fast-growing startup, identified a need to replace it's existing Chef-based deploy model with a model which reduces deploy-time risk and allows its engineering team to scale.
The second section is a high-level walkthrough of the new GameChanger deploy pipeline based around Docker.
It's easy to say... Microservices! Reality is we need to learn and apply concepts coming from many disciplines like SOA, EDA and DDD just to name a few! Mix them with some ALM and technical processes around Packaging and Deploying... and maybe then you get a true Microservices solution.
What is the ‘Cloud’? Today almost every self-proclaimed industry pundit who attempts to describe cloud computing talks about ‘elasticity’ or how magically new servers appear in the cloud with a swish of a magic wand!
But, is that all we get with cloud computing?! What is wrong or missing in today’s software world? Didn’t we build and run software for the past 50+ years? Why do we need this cloud computing all of a sudden? This whitepaper attempts to answer whether cloud computing is the right strategy for you and your enterprise. The intent of this paper is not to try and compare various cloud offerings (either Azure or Amazon), the objective is to sow new ideas in your mind and the intent is to explain in layman’s terms how cloud computing is silently revolutionizing our 50 year old industry.
Dewey Sasser discusses maintaining operational sanity in a cloudy DevOps world for a major gaming company that has transitioned all its services to public clouds like AWS. The company aims for 100% uptime and no maintenance downtime using a model where development teams are responsible for their services and a central cloud team provides shared tools and best practices. Key aspects are automated user access control using rules and workflows, tagging for cost control, and putting power in developers' hands while keeping responsibility with their teams.
The presentation "Agile Architecture in a Modern Cloud-Native Ecosystem" by Turja N Chaudhuri.
Recording of the presentation: https://www.youtube.com/watch?v=d4kGI3ARn5o
Details of the event: https://www.meetup.com/Cloud-Study-Network/events/283988261/
Accompanying presentation for Cloud Study Network group (https://www.meetup.com/Cloud-Study-Network/) :
Event link - https://www.meetup.com/Cloud-Study-Network/events/283988261/
hosted on 24.02.2022 , at https://www.youtube.com/watch?v=d4kGI3ARn5o
The document discusses development and QA dilemmas in DevOps. It notes that traditionally development was done separately from testing and production environments, but with DevOps there is a focus on continuous delivery through automated pipelines. It acknowledges this is a big change that makes some developers and testers uncomfortable by removing safety nets. It emphasizes that DevOps is about culture and practices, not specific technologies, and that these practices can be used on-premises. It provides examples of how to handle database schema changes and feature rollouts transparently in production. It stresses measuring outcomes through metrics and analytics to learn from users and improve products iteratively.
A Software Problem (and a maybe-solution)YangJerng Hwa
The document discusses problems in the software engineering field and proposes solutions. It identifies 4 main problems: 1) unsophisticated users require requirements analysts to create specifications, 2) non-programmers require programmers to develop minimally viable programs from specifications, 3) non-systems engineers require engineers to modify programs for scalability, and 4) a lack of standards leads to inefficient development. The document proposes addressing these by developing: A) a shared data structure, B) a user interface, C) a platform for minimal programs, D) software to generate standards-compliant applications, and E) framework extensions to guide further development. Ultimately, the document argues that vertically integrating software development from startups to enterprises could help solve large
This goal of this presentation is to present the rationale behind containers and how they can help you simplify your infrastructure and reduce cost and complexity. In this presentation I am showing the history and reasoning behind this technology which is used by world leading companies and how you can bring this technology and paradigm to bear to build distributed, fault tolerant, scalable solutions. This is only one of my many publications/solutions.
Accelerate your Application Delivery with DevOps and MicroservicesAmazon Web Services
DevOps aims to accelerate application delivery by breaking down silos between development and operations teams. It promotes continuous integration, delivery, and deployment to production through automation and monitoring. Microservices help achieve this by decomposing applications into independently deployable components to improve scalability, innovation, and failure isolation. While challenging, DevOps and microservices can help organizations deliver value faster and improve customer experiences.
The speaker discusses how Lookout has scaled its engineering organization and technical infrastructure over time. In 2011, Lookout had problems with unreliable deployments and a monolithic codebase. It introduced new tools like JIRA, Jenkins, and Git/Gerrit to improve its workflow. It also automated deployments and now has a much higher success rate. As Lookout has grown, it has moved to a more distributed architecture with over 100 microservices running on different technologies. Scaling organizational knowledge and coordinating many independent services will be ongoing challenges.
The document discusses ATMOS, a cloud-based content retrieval library. Some key points:
1) ATMOS provides the benefits of cloud computing like convenient APIs, simple metadata-based retrieval and classification, high reliability and security.
2) Using ATMOS as the basis for a content retrieval system could help solve problems with data manipulation and add more universality to retrieval, allowing both machine and manual indexing.
3) The library presented retrieves images that are visually or cognitively similar to a sample image provided by the user, ignoring weak image noises and prioritizing similar shapes and edges.
What Should I Do? Choosing SQL, NoSQL or Both for Scalable Web ApplicationsTodd Hoff
This is the slidedeck I used for a webinar (http://voltdb.com/choosing-sql-nosql-or-both-scalable-web-apps-webinar) I gave on helping people choose SQL or NoSQL for building scalabile web applications. Hint, the answer is: both.
This slide is translated version. Originally it was written in Korean. (http://www.slideshare.net/saltynut/how-do-we-drive-tech-changes )
It describes how do we drive technical changes onto our organizations had used old-fashioned java combinations(Java 1.6+Spring 3.x+MyBatis) and monolithic architecture.
Key point is what we need to do to drive changes, and I'll discuss what we did during Phase1 and what we are doing at Phase 2 for architecture, frontend, backend, methodologies/process.
Phase1
- Architecture : Frontend / Backend Separation
- Frontend : Angular.js, Grunt, Bower
- Backend : Java 1.7/Spring4, ORM
- Methodology/Process : Scrum, Git
Phase2
- Architecture : Micro-Service Architecture(MSA)
- Frontend : Content Router, E2E Test
- Backend : Polyglot, Multi-Framework
- Methodology/Process : Scrum+JIRA, Git Branch Policy, Pair Programming, Code Workshop
Slides from my DevOpsExpo London talk "From oops to NoOps".
They tell you in these conferences that DevOps is not about tools, but about culture. And they are partially right. I am going to tell you that it’s not only about culture or tools but also abstractions.
It is a lot about how you see software and its value. About our mental model of what software is: how it runs, evolves, and interacts with the other facets of an enterprise.
We used to view software as code. As a state of code. Now we think about software as change, as a flow. A dynamic system where people, machines, and processes interact continuously.
At Platform.sh we spend a bunch of time asking ourselves not “How do you build?” - or even “How do you build consistently?” - but rather “What does it mean to consistently build in a world where change is good?” A world that lets you push security fixes into production as soon as they’re available because you don’t want to be an Equifax but you do want stability.
In this presentation, I will go over what we think software is and why having the right ideas about software will help you get your culture right and your tooling aligned, as well as gain in productivity, and general happiness and well-being.
This document discusses how to maintain large web applications over time. It describes how the author's team managed a web application with over 65,000 lines of code and 6,000 automated tests over 2.5 years of development. Key aspects included packaging full releases, automating dependency installation, specifying supported environments, and automating data migrations during upgrades. The goal was to have a sustainable process that allowed for continuous development without slowing down due to maintenance issues.
The document discusses the three stages that dynamic systems go through: 1) simple content management, 2) beyond basic features like calendars and forums, and 3) building custom web applications. It also covers designing for dynamic systems by using templates and planning for user-generated content. Open source options are discussed, including choosing an existing open source project, using open source, or building your own. The benefits and challenges of using plugins and modules as well as frameworks are summarized. The key takeaways are that the web is becoming more dynamic, systems need to interconnect, and one should consider their business model.
Hand Rolled Applicative User ValidationCode KataPhilip Schwarz
Could you use a simple piece of Scala validation code (granted, a very simplistic one too!) that you can rewrite, now and again, to refresh your basic understanding of Applicative operators <*>, <*, *>?
The goal is not to write perfect code showcasing validation, but rather, to provide a small, rough-and ready exercise to reinforce your muscle-memory.
Despite its grandiose-sounding title, this deck consists of just three slides showing the Scala 3 code to be rewritten whenever the details of the operators begin to fade away.
The code is my rough and ready translation of a Haskell user-validation program found in a book called Finding Success (and Failure) in Haskell - Fall in love with applicative functors.
Zoom is a comprehensive platform designed to connect individuals and teams efficiently. With its user-friendly interface and powerful features, Zoom has become a go-to solution for virtual communication and collaboration. It offers a range of tools, including virtual meetings, team chat, VoIP phone systems, online whiteboards, and AI companions, to streamline workflows and enhance productivity.
What is Master Data Management by PiLog Groupaymanquadri279
PiLog Group's Master Data Record Manager (MDRM) is a sophisticated enterprise solution designed to ensure data accuracy, consistency, and governance across various business functions. MDRM integrates advanced data management technologies to cleanse, classify, and standardize master data, thereby enhancing data quality and operational efficiency.
Flutter is a popular open source, cross-platform framework developed by Google. In this webinar we'll explore Flutter and its architecture, delve into the Flutter Embedder and Flutter’s Dart language, discover how to leverage Flutter for embedded device development, learn about Automotive Grade Linux (AGL) and its consortium and understand the rationale behind AGL's choice of Flutter for next-gen IVI systems. Don’t miss this opportunity to discover whether Flutter is right for your project.
Graspan: A Big Data System for Big Code AnalysisAftab Hussain
We built a disk-based parallel graph system, Graspan, that uses a novel edge-pair centric computation model to compute dynamic transitive closures on very large program graphs.
We implement context-sensitive pointer/alias and dataflow analyses on Graspan. An evaluation of these analyses on large codebases such as Linux shows that their Graspan implementations scale to millions of lines of code and are much simpler than their original implementations.
These analyses were used to augment the existing checkers; these augmented checkers found 132 new NULL pointer bugs and 1308 unnecessary NULL tests in Linux 4.4.0-rc5, PostgreSQL 8.3.9, and Apache httpd 2.2.18.
- Accepted in ASPLOS ‘17, Xi’an, China.
- Featured in the tutorial, Systemized Program Analyses: A Big Data Perspective on Static Analysis Scalability, ASPLOS ‘17.
- Invited for presentation at SoCal PLS ‘16.
- Invited for poster presentation at PLDI SRC ‘16.
A Study of Variable-Role-based Feature Enrichment in Neural Models of CodeAftab Hussain
Understanding variable roles in code has been found to be helpful by students
in learning programming -- could variable roles help deep neural models in
performing coding tasks? We do an exploratory study.
- These are slides of the talk given at InteNSE'23: The 1st International Workshop on Interpretability and Robustness in Neural Software Engineering, co-located with the 45th International Conference on Software Engineering, ICSE 2023, Melbourne Australia
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian CompaniesQuickdice ERP
Explore the seamless transition to e-invoicing with this comprehensive guide tailored for Saudi Arabian businesses. Navigate the process effortlessly with step-by-step instructions designed to streamline implementation and enhance efficiency.
Most important New features of Oracle 23c for DBAs and Developers. You can get more idea from my youtube channel video from https://youtu.be/XvL5WtaC20A
UI5con 2024 - Keynote: Latest News about UI5 and it’s EcosystemPeter Muessig
Learn about the latest innovations in and around OpenUI5/SAPUI5: UI5 Tooling, UI5 linter, UI5 Web Components, Web Components Integration, UI5 2.x, UI5 GenAI.
Recording:
https://www.youtube.com/live/MSdGLG2zLy8?si=INxBHTqkwHhxV5Ta&t=0
E-commerce Development Services- Hornet DynamicsHornet Dynamics
For any business hoping to succeed in the digital age, having a strong online presence is crucial. We offer Ecommerce Development Services that are customized according to your business requirements and client preferences, enabling you to create a dynamic, safe, and user-friendly online store.
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...Crescat
Crescat is industry-trusted event management software, built by event professionals for event professionals. Founded in 2017, we have three key products tailored for the live event industry.
Crescat Event for concert promoters and event agencies. Crescat Venue for music venues, conference centers, wedding venues, concert halls and more. And Crescat Festival for festivals, conferences and complex events.
With a wide range of popular features such as event scheduling, shift management, volunteer and crew coordination, artist booking and much more, Crescat is designed for customisation and ease-of-use.
Over 125,000 events have been planned in Crescat and with hundreds of customers of all shapes and sizes, from boutique event agencies through to international concert promoters, Crescat is rigged for success. What's more, we highly value feedback from our users and we are constantly improving our software with updates, new features and improvements.
If you plan events, run a venue or produce festivals and you're looking for ways to make your life easier, then we have a solution for you. Try our software for free or schedule a no-obligation demo with one of our product specialists today at crescat.io
Revolutionizing Visual Effects Mastering AI Face Swaps.pdfUndress Baby
The quest for the best AI face swap solution is marked by an amalgamation of technological prowess and artistic finesse, where cutting-edge algorithms seamlessly replace faces in images or videos with striking realism. Leveraging advanced deep learning techniques, the best AI face swap tools meticulously analyze facial features, lighting conditions, and expressions to execute flawless transformations, ensuring natural-looking results that blur the line between reality and illusion, captivating users with their ingenuity and sophistication.
Web:- https://undressbaby.com/
8 Best Automated Android App Testing Tool and Framework in 2024.pdfkalichargn70th171
Regarding mobile operating systems, two major players dominate our thoughts: Android and iPhone. With Android leading the market, software development companies are focused on delivering apps compatible with this OS. Ensuring an app's functionality across various Android devices, OS versions, and hardware specifications is critical, making Android app testing essential.
Artificia Intellicence and XPath Extension FunctionsOctavian Nadolu
The purpose of this presentation is to provide an overview of how you can use AI from XSLT, XQuery, Schematron, or XML Refactoring operations, the potential benefits of using AI, and some of the challenges we face.
Unveiling the Advantages of Agile Software Development.pdfbrainerhub1
Learn about Agile Software Development's advantages. Simplify your workflow to spur quicker innovation. Jump right in! We have also discussed the advantages.
2. Before we answer the questions that start with
What and How,
Let us ask the harder questions starting with Why
Why triggers Why not, and the answers will make What and How more
meaningful...
3. But before I start with the Talk, there is just one thing I want to say -
this talk is not only about yakking why Micro Services are the greatest thing that
has ever happened, and why everyone should discard everything in and jump
in;No this talk is more about Systems Engineering than System Architecture; and
a possible solution to the problems of Enterprise SW product development.
Yes, Systems Engineering -a term that needs more focus, has to do with people,
team organization,product/release management, system design and basically
when we talk about MicroServices we are talking about a way of Systems
Engineering!
4. Some Questions that we will try to answer ?
A .Why not Tired Architecture/Application Servers /DB Tier, Web Tier ?
B .Why is this widely adopted or gaining popularity in all high profit companies;
Amazon, NetFlix, Google ? /will we be more profitable if we adopt ?
C. Will This too Pass /do I really need to listen zzZZ ? will you talk about the
wonders of Serverless next ?
(COM, CORBA,EJB, ESB, SOA --SOAP.. REST? what REST ???
E. What has to change for this ?
5. Slide 5 -There is just one more story I want to share, before I
start.. Andy Tanenbaum was a professor and OS researcher, held in high esteem and his books are
very popular; here is an old but interesting debate with Linus Torvalds (note Linux Kernel is Monolithic)
>1. MICROKERNEL VS MONOLITHIC SYSTEM
From: ast@cs.vu.nl (Andy Tanenbaum)
Subject: Re: LINUX is obsolete
Date: 30 Jan 92 13:44:34 GMT
I still maintain the point that designing a monolithic kernel in 1991 is a fundamental error.
Be thankful you are not my student. You would notget a high grade for such a design :-)
From: torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds)
Subject: Re: LINUX is obsolete
Date: 29 Jan 92 23:14:26 GMT
Organization: University of Helsinki
Well, with a subject like this, I'm afraid I'll have to reply True, linux is monolithic, and I agree that microkernels are nicer. With a
less argumentative subject, I'd probably have agreed with most of what you said. From a theoretical (and aesthetical)
standpoint linux looses.If the GNU kernel had been ready last spring, I'd not have bothered toeven start my project: the fact is that it
wasn't and still isn't. Linux wins heavily on points of being available now. -
http://www.oreilly.com/openbook/opensources/book/appa.html
6. let us start the talk (finally) with a thought
The Problems you don’t know you have, are usually
your biggest Problems.
Most of us fall into two categories
1. Everyone thinks their System is tiered, service oriented, message based , superbly designed...
CLOUD based..
2. Or they think; damn my system is not containerized, not cloud based, not written in Go or Erlang or
whatever, hmm
No architect, or developer is thinking if there is a problem
somewhere, a bigger problem
7. What could be the Problem ?
Maybe your System Architecture is beautiful, theoretically
right, academically correct, full marks slide(5) ?
But if you take a year to release a small feature to
your end customer ?
If we are so slow in feature delivery ?
If we turn estimates into deadlines, and have to then race to deliver on time, but
create horrendous messes in product delivery ?
8. Maybe most SW houses follow a System
Engineering model that is better in producing packed
Noodles than Software ?
We yearn for order and repeatability; but features are usually complex
This is an exaggerated comparison, but most business borrow heavily from
industrial practises. ( Lean from Toyota, Kanban ?)
9. Or maybe our System Architecture has evolved as
per our organization structure ?
Organizations which design systems are constrained to produce
designs which are copies of the communication structures of these
organizations -- Conways law “How Do Committees Invent"
http://www.melconway.com/research/committees.html
This is a problem as basically every team has to throw the ball and
part of the responsibility to another team till it release.
Humans love each other; Teams don’t lose much love between them ?
10. Amazon realized they had a problem around 2001
“If you go back to 2001,” stated Amazon AWS senior manager for product management Rob Brigham, “the Amazon.com
retail website was a large architectural monolith.”
“Now, don’t get me wrong. It was architected in multiple tiers, and those tiers had many
components in them,” Brigham continued. “But they’re all very tightly coupled together,
where they behaved like one big monolith... that monolith is going to add overhead into your process, and
that software development lifecycle is going to begin to slow down.”
we measured the amount of time it took a code change to make its way through that
deployment lifecycle, across a number of teams. When we added up that data, and looked at
the results, and saw the average time it took, we were frankly embarrassed. It was on the order of weeks.”
For a company like Amazon that prides itself on efficiency — for a company that uses robots inside of our fulfillment
centers to move around physical goods, a company that wants to deploy packages to your doorstep using drones — you
can imagine how crazy it was,” he said, “that we were using humans to pass around these virtual bits in our software
delivery process.. (https://thenewstack.io/led-amazon-microservices-architecture/)
11. Amazon turned to SOA ....Jeff Bezos style
Here is a post from ex Amazon Google employee Steve Yegge's that that got published accidently; herecalls that one
day Jeff Bezos issued a mandate, sometime back around 2002 (give or take a year)
● All teams will henceforth expose their data and functionality through service interfaces.
● Teams must communicate with each other through these interfaces.
● There will be no other form of inter-process communication allowed: no direct linking, no direct reads of another
team’s data store, no shared-memory model, no back-doors whatsoever. The only communication allowed is via
service interface calls over the network.
● It doesn’t matter what technology they use.
● All service interfaces, without exception, must be designed from the ground up to be externalizable. That is to say,
the team must plan and design to be able to expose the interface to developers in the outside world. No exceptions.
The mandate closed with:
Anyone who doesn’t do this will be fired. Thank you; have a nice day!
https://apievangelist.com/2012/01/12/the-secret-to-amazons-success-internal-apis
http://www.businessinsider.com/jeff-bezos-makes-ordinary-control-freaks-look-like-stoned-hippies-says-former-engineer-2011-10?IR=T
12. Service oriented architecture promised modular components each providing a web
interface API to interact with it.
A lot of other companies and products embraced SOA as
well;
it was heavily marketed; SOA, Web Services and the like;
But many missed the crucial parts of why they did what they
did. Again
13. Amazon adopted SOA and was working on*
Continuous Delivery
So that they could use SOA and make feature
releases faster and faster....
Remember slide(5); System architecture is not the
end goal; System Engineering has to be
transformed as well..
*http://www.allthingsdistributed.com/2014/11/apollo-amazon-deployment-engine.html
14. We have come to the What Part
Microservices as term was coined around 2011, but was a progression from SOA.
Martin Flower, the famous Thoughtworks consultant had documented many
aspects of this. There is no one definition. Here is one that highlights the why part
into the what :- MicroService is an enabling technology, for continuous
product deployment,using immutable containerized software
modules, that adhere to typed versioned interface and lightweight inter
module communication mechanism.
Typically container management, centralized log and performance collection and
continuous deployment pipeline are needed for a practical robust solution
15. What the *** ?
Yes it was a mouthful as definitions go, I got the liberty and I thought I would make
a bigger one, why not
Now you know why there is no one definition for anything in Software, that
everyone understand in the same way. Here is a better one
https://martinfowler.com/articles/microservices.html
As we are talking about definitions what do you think is a Scrum Master ?
A Master Craftsman in Scrum ? a Master in Scrum ? or a Master of Scrum
(commanding Scrum Slaves)?
... the trouble with humans, everyone has a completely different take on
anything slightly abstract...
16. How do you create a MicroService ?
A. An application is decomposed to smaller set of functionality, each as a
software module exposed over the network usually over HTTP wrapped in a
container
Q But won’t this mean that there will be lot of interactions between services, if we
use WSDL and XMLs the performance ?
Q. Wait HTTP, it does not compress, oh even if I use JSON and REST it will be a
problem, what about the hundreds of connections ?
Q. You mean to say that I have to put TomCat, JBoss, WebSphere.. Xxx
Application platform in each container, this is going to be really heavy ??
17. Still further questions
Q. What, over the network ? What about NW calls , latency , headless master
syndrome, Distributed Computing fallacies ??
Q. Over the network, really, the coding horror of checking if any damn router acts
up ?
Q. Really continuous delivery, my stack depends on xx version of yy so that it will
only work with my neighbours component that uses yy version of xx ....
18. There would be lot more questions as well
If we know all our Problems up-front will we ever start ? It is good to think and
uncover some? and stop thinking and handle some as it comes
Companies that moved to this sort of system engineering were companies that
solved most of these, and though some of this like CD is a definite commercial
advantage and not discussed much
the good new is that many of the solutions they have Open-Sourced
19. Rapidly Changing Interfaces of components needs a versioned and typed
Interface between modules/micro services
REST is good and delivered us all from the horrors of WSDL. But REST has very
poor interface semantics; good for web servers; not for services;( I love REST and
the Stateless Server Concept of REST & HTTP Inventor Roy Fielding!)
Lightweight efficient communications between modules is solved by GRPC &
Protocol Buffer v3 - Feb 2015 - Today, we are open sourcing gRPC, a brand new framework for handling
remote procedure calls. It’s BSD licensed, based on the recently finalized HTTP/2 standard, and enables easy
creation of highly performant, scalable APIs and microservices in many popular programming
languages and platforms https://developers.googleblog.com/2015/02/introducing-grpc-new-open-source-http2.html
20. There is a lot more to GRPC...
There are 201 slide here
https://www.slideshare.net/borisovalex/enabling-googley-microservices-with-http2-
and-grpc
Suffice to say that Netflix moved its 10 billion microservices to GRPC
Really ? Hmm, seems so - We’ve also undergone a huge evolution of our Runtime Platform. From
replacing our old in-house RPC system with gRPC ..
https://medium.com/netflix-techblog/neflix-platform-engineering-were-just-getting-started-267f65c4d1a7
(July 5 2017)
https://www.forbes.com/sites/janakirammsv/2017/03/01/grpc-the-protocol-of-microservices-joins-the-cloud
-native-computing-foundation/#288c270f4b0a
21. Why Containers ?
First why VMs ? HW virtualization; Plonk a big Server and create as many VM’s as
you wish ? Each VM is a JAILED OS; provisioned CPU, RAM DISK
Why Container? To Start with Containers are a JAILED process;
A process that is isolated and had limited CPU, memory, Resources - Control
Groups (cgroups) based on chroot? Released in 2006 by Google, merged to Linux
Kernal 2.6.24
Each microservice is usually one GRPC process; You can have Tomcat , JBoss
and what ever you like in the Container; But with GRPC it is acutally serverlss
22. If it is so much why did it become pretty popular
I don’t know
But I would say how Docker did Container Management is the key and its perfect
delivery vehicle for Micro Services
It is not really well appreciated; But each layer in a Dockerfile build Docker Image
is immutable
Docker is delivering the promise of immutable infrastructure.
Many of the things of Continuous Deployment works because
of this like rollback, easy upgrade etc...
23. There is a lot more about Docker
Think about it,if you have a zillion services will it be practical to have the overhead
of virtual machines
Do you know that Docker containers can easily emulate your favorite distribution
which can work on any Linux OS ?? (as long as it is x86 based)
That you can map volumes, and devices of the host into it
And Docker Registry
24. Before I stop
Things which are very relevant in this space but which we did not talk about
Service Discovery - Consul
Container Management - Kubernetes, (OpenShift)
Parting words
How To - GRPC, Docker , Consul Kubernetes, No shared nothing
Why to - Decoupled /decentralized fast feature delivery. Polyglot Stack, Freedom
Problems - Monolithic Frontends ? ...