.NET 기반 비즈니스 응용 프로그램의 현주소와 방향
•Download as PPTX, PDF•
0 likes•41 views
.NET 기반 비즈니스 응용 프로그램의 현주소와 방향
Recommended
More Related Content
Similar to .NET 기반 비즈니스 응용 프로그램의 현주소와 방향
Similar to .NET 기반 비즈니스 응용 프로그램의 현주소와 방향 (20)
More from 명신 김
More from 명신 김 (20)
.NET 기반 비즈니스 응용 프로그램의 현주소와 방향
- 1. Visual Studio 2013 제대로 파헤쳐 보기! 11월의 주제 .NET 기반 비즈니스 응용프로그램의 현주소와 방향 -한국 마이크로소프트 기술 에반젤리스트 김명신 부장 - Facebook/Twitter : @himskim
- 4. 비즈니스 응용프로그램의 .NET 사용현황
- 5. 웹 사이트 개발에 사용하는 프레임워크
- 6. .NET 성장 트렌드
- 8. 개발 플랫폼 Client Software Browser, Native mobile, Desktop Infrastructure services Storage, App, App/Web server, Identity & access, Instrumentialization & monitor Deployment environment On Premise, Private Cloud, Public Cloud ALM& DevelopmentTools Application services Web Presentation/UI Services, Services, Collaboration and portals, Custom application platform, Messaging, Business products and platforms
- 14. Services Devices + + Emerging patterns 응용 프로그램 개발 패턴의 변화 Servers Client Established patterns
- 15. Established application patterns Foundational applications for the business Web and desktop applications Centered on existing business processes Modern 비즈니스 응용 프로그램 Small/Medium Business Applications Productivity Easy to get started Large Mission-Critical Business Applications Long-Term Core-Business Emerging application patterns End-user centric Innovation Mobility & Cloud Foundational Business New Experiences Extending Fixed On-Premises Elastic Cloud and Hybrid Evolving
- 16. 중소 규모 비즈니스 응용 프로그램 대규모 Mission-Critical 비즈니스 응용 프로그램
- 17. Why .NET: 중소 규모 비즈니스 앱 Productivity Easy to get started
- 18. Why .NET: 중소 규모 비즈니스 앱 Rapid time to market; easy to get started; quality out-of-the-box Tools: Visual Studio is the best IDE and ALM environment available Common dev-platform across environments (On-prem. & Cloud)
- 19. Why .NET: 대규모 Mission-Critical 앱
- 20. Why .NET: 대규모 Mission-Critical 앱 Top QoS and great fit for loosely coupled architectures .NET languages (C# and F#) are ahead of the competitors Sustained productivity in large development projects
- 21. Why .NET: 대규모 Mission-Critical 앱 Complete Visual Studio Testing environments for the enterprise One consistent dev-platform across environments (On-prem. & Cloud) Tools and technologies for the entire application lifecycle
- 22. 마지막으로 마케팅 슬로건이 아니라, 실제 사실에 근거하여 개발언어 하나만을 놓고 비교해 보아도, JAVA 언어는 C#보다 5년 정도 뒤쳐져 있는 것으로 보인다.
Editor's Notes
- Device
- As you can see from this char from Forrester, 57% of custom developed applications use .NET.
- As you can see from this char from Forrester, 57% of custom developed applications use .NET.
- And when you start looking for growth trends, Gartner’s projecting expanded uses of .NET for large, mission critical applications (shown as Extreme Enterprise on the chart). Source: Gartner—Examining Java EE and Microsoft Software Platforms: Competitive Trends and Future Directions Published: 22 November 2011 Enterprise & Large core-business
- Device
- Device
- .NET empowers today’s established business applications, for any organization and size. .NET enables application modernization, extending on-premises applications to the cloud and new experiences across devices. Nowadays, there is a new era of application development in order to stay competitive. Businesses need is to create innovative and compelling systems that reach directly to customers through new connected multi-device channels (or even omni-channel, that is, they work everywhere instead of just developing traditional business applications for a concrete type of client computer. What is a Modern Application? Modern applications span multiple devices, contextualize data from multiple sources, can be rapidly built and deployed, are always up to date, and always available. Based on this definition, one of the core characteristics is that the application must cross the boundaries of the enterprise and offer a direct engagement to end users and other entities (such as partners or providers). Because of that direct engagement, mobility and “reaching the person” (including through social networks), are the most important differentiators here. Though, you must also be concerned about modernizing your backend systems from on-premises to cloud, and scale-out as needed in order to support unpredictable scalability needs coming from these new users and channels using those modern applications. This is why a modern business application goes much further than simple systems of engagement or isolated mobile apps. Examples of these kinds of applications are mobile online banking, engaging mobile catalog apps for sales forces, business dashboards for touch devices like tablets and smartphones, and mobile real-time follow-up systems. Essentially, this boils down to applications especially made for concrete and quite narrow and specialized business scenarios, such as looking for new channels and possibilities. But new mobile business apps cannot be successful on their own—it is not just a matter of creating apps for smartphones and tablets. Mobile business apps must be part of the larger enterprise ecosystem and must really extend those foundational business applications. It doesn’t matter if those foundational systems are established and legacy applications or they are new large mission-critical applications built from scratch with new, scalable and elastic services. At some point, the mobile apps must rely on the foundational business applications while at the same time evolving the legacy applications toward updated and more elastic back-end systems. The goal is to modernize the foundational business applications rather than to simply create mobile apps. Modern Applications Therefore, the foundational business applications are really the pillars of end-to-end modern applications, as shown above in Figure 3‑5. This also illustrates the difference between simple consumer Mobile-Apps versus Modern Business Applications (which is really the whole figure). Modern Business Applications not only cover mobile client applications but also use Continuous Services relaying on the foundational business applications. The .NET ecosystem and frameworks are fundamental when building those continuous services. Finally, it must evolve toward hybrid IT scenarios. Those Hybrid IT scenarios integrate elastic and highly scalable cloud services (like Windows Azure) with actual on-premises enterprise infrastructure. Because of new innovative channels and new mobile users (many times, unpredictable amount of users), elastic services are needed more than ever. A modern business application must be able to have infrastructure elasticity in order to have the ability to scale up (or down) on demand, which means that application-infrastructure sizing is now also an iterative activity, thanks to the cloud elasticity, which helps contributes to reduced upfront costs. Traditional applications didn’t have that advantage. Going further, modern business applications must not be isolated in the cloud. They must be able to integrate to on-premises systems in order to have end-to-end control. That is why hybrid IT (cloud integration) is also a critical part of the business application modernization process. You should be considering how your app will compete in the rapidly changing technological landscape. Even if you decide not to cloud-enable or build a mobile version of your app in the short term, Microsoft technologies can help you modernize and keep in step with the industry. But, make no mistake about it, you should already be considering those new experiences and channels. The software development landscape is changing rapidly. It is really a revolution of the devices and the cloud. You’ll need to be on board in order to survive.