The document discusses functional reactive programming (FRP) using RxJava, detailing its concepts, benefits, and implementation techniques. It highlights the use of observable patterns to handle asynchronous data streams and event-driven programming styles. The content includes practical code examples and applications in server development, emphasizing the integration of RxJava with web services and reactive data handling.
??? ?? ??? ???? ?? ??? ??? ????, ???? ???? ???? ??? ???? ?????? ?? ?? ??? ?? ?????. ????? ????? ????? ??? ???? ??? ? ?? ??? ???? ??? Kubernetes service? ??? ?? ??????? | To understand Docker's underlying technology, we look at Docker's history and learn about the core concepts of Kubernetis, which operates a container environment in a cluster environment. Lastly, I will introduce Naver's cloud platform Kubernetes service, which allows you to easily create and manage Kubernetes clusters, through a demo.
[BRK30136] Windows ?? ??? ???? ?? ???? ???? / Introduction to Containers For ...Jung Hyun Nam
?
Demo videos available at https://1drv.ms/u/s!Aj231qrFhIQxqbxbJCrSsQw443FOoA?e=nYebBM
? ????? Windows ?? ??? ?????? ????? ?? ??? ???????? ??? ??????? Windows ???? ???? ???????? ??? ???? ?????.
In this session, I will detail how Windows-based back-end application developers can migrate their existing back-end or command-line applications to a Windows container base.
This document discusses refactoring, which involves restructuring existing code without changing its external behavior or functionality. It provides definitions of refactoring and describes best practices for refactoring code, such as taking small, incremental steps and verifying that automated tests still pass after each change. Specific refactoring techniques are also explained, like extracting duplicate code into methods, removing unnecessary complexity or duplication, and consolidating conditional expressions for clarity. The document cautions against fixing bugs during refactoring and emphasizes making changes in a way that simplifies the code and removes code smells.
The document summarizes DevOps Day 2013 that was held in Silicon Valley from June 21-22, 2013. It provides details about the event location, participants, sessions covered, and goals of attending. Specifically, it discusses learning about DevOps practices, differences from agile development, and continuous quality approaches in a community-focused event with presentations from consulting and solution providers.
The document summarizes a conference called Velocity 2013 Conference. It provides details about:
- The purpose of attending the conference was to learn about reference architectures for build/deployment systems, monitoring, and mobile deployment.
- The conference covered topics like mobile performance, operations, and web performance. It included technical sessions on solving performance and operational issues in large-scale environments.
- Some of the sessions discussed tools for packaging, log collection, monitoring metrics, testing methods, lessons learned from projects, and scaling load balancing infrastructure to over a billion users.
This document outlines an Agile planning and estimating workshop presented by Joshua Partogi. The workshop covers Scrum concepts like timeboxing, product backlog creation and ordering, estimating work in story points, sprint planning, and monitoring progress via burn down charts and velocity. Participants work through exercises to practice these techniques in planning and estimating the work for a mobile tourism app project over multiple sprints and releases.
The document discusses the concept of "unicorns" in software innovation. It defines unicorns as people who can perform multiple specialty functions and solve a broad set of problems for their team. It explains that many startups are desperately seeking "unicorns" due to changes in software development that require more cross-functional skills. It outlines eight attributes of standout tech companies, including having empathy for customers, making opinionated products, learning quickly through doing rather than textbooks, and being good communicators. The document argues that success in software innovation is now defined more by cultural fit and attitude than specific skills or educational background.
This document discusses the role of an architect in agile development. It compares waterfall and agile architecture approaches. The architect's responsibilities in agile include incrementally documenting designs, communicating with the team, embracing change, and removing impediments. Best practices for agile architecture include inviting peer review, challenging assumptions, and learning from mistakes. The architect must understand coding and know how to work with people as technology alone is not enough.