A4: To design in a way which fosters agility and speed. A clear architecture/direction is good, but not to the expense of innovation, speed and agility. There will be much more focus on enabling change, rather than implementing rigid structures. #SASChat#EnterpriseArchitecture
@JOchiaiBrown Yeah, that's a really tough one. The combination of how to interpret legal aspects, and "what do we feel comfortable with". Is really one of the toughest (and most important) nuts to crack.
A3: Before we talked about Outsourcing, now we talk about XAAS. Before Service Oriented Architecture, now microservices. Before virtualization, now containers. Even though the toolbox has evolved the main drivers have stayed the same. #SASChat#EnterpriseArchitecture
A2: It has changed from planning for a future we think will come, to plan for agility. More focus on building something now that is adaptable, rather than putting months or years of planning in something that might never happen. #saschat#EnterpriseArchitecture
A2: Both for it-systems and the organization the focus is on independent parts with clear purpose (and interface to each other). This moves monoliths to microservices, and clearly defined roles/processes to self-organizing teams. #saschat#EnterpriseArchitecture
A1: IT, business, customers. Everyone.
Having the possibility to adapt to customer needs in an efficient, cost effective and flexible manner is key to be able to provide services that quickly evolves with changed customer behaviors and needs. #SASchat#EnterpriseArchitecture
Today is the day! See you in a few hours for our #SASchat on #EnterpriseArchitecture. We will explore how business and technology strategists are driving business value through stronger alignment. https://t.co/1iyfjUzQF3
🇸🇪 There is no contradiction between open and proprietary software - both types are needed says SAS's Kristoffer Nilsson. To find out the similarities and differences between the two read more here on Computer Sweden: https://t.co/q5h6ed1WO3
Thanks for a really fun chat. Always a really interesting experience to see all different views on a subject lile this. Now back to the Swedish summer :) #saschat
A5: Focus on additional value generated and not only current cost savings. Things like flexibility and agility can be just as important,. The cloud migration is not only to cover what the requirements are today, but also to enable what they will be tomorrow. #saschat @CoreCompete
A4: Where the input/output of data and decisions are more decoupled, such as systems where data is batched on a regular frequence, the analytics workload could be moved to cloud earlier to get the benefits on the scalability and flexibiity the cloud deliver. #saschat @CoreCompete
A4: In a tightly coupled environment the analytics workload is in the same place at the cloud adoption maturity as the system that feeds it/the systems the analytics does feed. #saschat @CoreCompete
@macoopma @CoreCompete I totally agree. I think it will vary, but hybrid will probably be more and more common, since having everything running on cloud is a really far journey for most companies.
@macoopma @CoreCompete Interesting point, which is a hard one. Gives much more freedom and flexibility, but will it affect peoples ability to regain energy when always available?
A3: Since analytics should follow the data it also opens up for more requirement regarding cloud/hybrid architectures, allowing for data residing in anything ranging from on premise mainframes to cloud data lakes. #saschat @CoreCompete