DevOps

DevOps
Modernizing Customer-Facing App DevelopmentModernizing Customer-Facing App Development

This Pulse survey of 100 IT and engineering leaders uncovers how companies are prioritizing and optimizing customer-facing application development.

0 views
Related Tags
What are your thoughts on SaaS management platforms (SMP)?

Top Answer :

11 views
0 comments
2 upvotes
Related Tags
Business Application Development
Architecture & Strategy
Maintenance
Requirements & Design
Testing, Deployment & QA
Mobile Development
Development
Selection & Implementation
Business Analysis
Applications Vendor Landscapes
Optimization
Backup
Data Center
Public and Hybrid Cloud
Telephony
Network
Compute
Storage
Business Applications
Cloud
Crisis Management
Data & Business Intelligence
Artificial Intelligence
Business Intelligence Strategy
Data Management
Enterprise Integration
Integrations
Machine Learning
Governance
Data Lake
Big Data
Data Warehouse
Disruptive & Emerging Technologies
5G
Blockchain
Cryptocurrencies
Virtual Reality
IoT
Reality
Digital Innovation
Bots
Augmented Reality
End-User Services & Collaboration
Collaboration solutions
End User Equipment
End-User Computing Devices
Endpoint management
Productivity tools
Document Management
End-User Computing Applications
End-User Computing Strategy
Mobile
Voice & Video Management
Continuous Integration
Technical Product Management
DevOps
Continuous Deployment
Development
Quality Assurance
Customer Relationship Management
Enterprise Content Management
Customer Success
Enterprise Information Management
Finance
Enterprise Resource Planning
HR
Legal
Marketing Solutions
Retail
Human Resource Systems
Marketing
Product Recommendation
Sales
Risk Management
GDPR
SOX Compliance
Governance, Risk & Compliance
Infrastructure & Operations
Cloud Strategy
I&O Finance & Budgeting
Operations Management
Network Management
DR and Business Continuity
Server Optimization
Leadership
Attract & Select
Cost & Budget Management
Engage
Culture
Manage Business Relationships
Innovation
Organizational Design
Program & Project Management
Train & Develop
Values
Talent management
Performance Measurement
Organization Structure
Manage & Coach
Availability Management
Financial and Vendor Management
Reporting
Service Desk
Management Tools
Enterprise Service Management
People & Process
Process Management
Asset Management
Project & Portfolio Management
Portfolio Management
Project Management Office
Pulse
Security
Confidentiality, Integrity, Availability
Secure Cloud & Network Architecture
Endpoint Security
Data Privacy
Identity and Access Management
Security Operations Center
Security Strategy & Budgeting
Security Vendor Landscapes
Threat Intelligence & Incident Response
Threat & Vulnerability Management
Vendor Management
Infrastructure Vendor Landscapes
Budgeting
Roadmap
Outsourcing
Strategy & Operating Model
Business Continuity
Architecture Domains
Strategy
Tool Recommendation
Streamlining Application DevelopmentStreamlining Application Development

Without an agile platform, application development can be a resource bottleneck for IT teams. The Pulse CIO community shares why.

Changing DevOps SpendChanging DevOps Spend

As budgets tighten, how is DevOps spending changing? We surveyed hundreds of executives to find out.

0 views
Related Tags
How have your developers been affected by remote working?

Top Answer : At the company I was working with last year, we found that because the developers were remote, there were less interruptions for them. They were more able to focus. So whilst we may have lost some ground in things like user acceptance testing (UAT) and activities like that, we found we made up for it in terms of the developers’ increased ability and the productivity of the developments.

What’s the top priority: securing your code or your infrastructure?

Top Answer : There are multiple solutions for both separately, but more and more people are trying to create a single solution set to solve both problems simultaneously.

Should vendor landscapes shift into an industry-wide standard architecture model?

Top Answer : I used to lead the solutions architecture team at WSO2 for more than 10 years. While working with architects I identified a bunch of issues that they are facing. First, people are looking at a mismatch of reference architecture because most of them are reference implementations. I call it a reference implementation because most are bound to a specific vendor. It's explaining how you build something using that particular vendor technology. I wanted to make a vendor and technology-neutral architecture. Second, people are blindly moving to microservices. They are not looking at the complications they face in production systems and enterprises, or how to use microservices correctly. And there's a need to group or federate microservices but there's no standard to do that. In addition to that I saw a gap between the architecture, development, and deployment—basically between the architect, developer, and DevOps engineer. There was nothing common that you could take from architecture into development, and into deployment. So I wanted to build an architecture construct that can take throughout the development life cycle. I call the architecture construct a ‘Cell’ in the reference architecture.   That's where cell-based architecture (CBA) came into the picture. I saw that the concept of cells in biology was very fitting because cells create complex systems, and in an enterprise, you see the same thing. I studied system biology a bit and looked at parallels between biology, system biology, and the system architecture to create this architecture style. For example, each cell should have a gateway, like the membrane of a biological cell that controls it. After I released a paper on this in 2018, many other parallels came on the market. Uber is using a concept called Dorma, a domain-oriented microservices architecture, which is the same concept. A number of our customers use this concept to plan, build and run their cloud-native microservice deployments. We are planning to inherit some of the concepts in our internal product development in this low-code and pro-code platform as well. You can read the complete spec from https://git.io/fpwtf, released under CC-4.0 so feel free to contribute, comment and even criticize.