Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I have read this interesting article from Talend on using Talend ESB & Auto-scaling on AWS.
I want to utilize this architecture design for our application setup in AWS.
Here is a brief overview of our application, currently in the development phase.
Now, I have these following questions with regards to leveraging Unlimited Scale Using Talend ESB & Auto-scaling on AWS for our application:
Thanks.
ESB is dead. my humble opinion
I'm not a huge fan of ESB, I love the conceptual (outdated) thoughts but I tend to lean more to the seperation of concerns design.
Could you elaborate a little on the purpose and what you are trying to achieve with this type of architecture?
Technically it would fit... so does a Mainframe... we need to have a little background so help us out.
- Whats your biggest/major 'business' challenge?
- How is "separation of concerns" utilized now? are we talking enterprise architecture? or domain?
- Is it primary focused on statistics or data-logistics?
- Are multi co-location data-centers involved, business in Japan, Europe and South America? Any geo specific requirements?
- Data (base) storage? What type of cold-storage or active storage or (nosql) databases where (functional) data is stored ... CRUD?
- Are you considering a real time data-pipeline?
- Beside synchronization is serialization involved in your current application landscape?
Thought of :
- Microservices ? more restful api's ...
- Docker, Kubernets ?
- Apache Kafka, Apache AVRO ?
Honestly a hard question to answer.