The punch is not a solution to everything. As we just explained in the previous track(s) it claims to target data centric applications, i.e applications that process data. But this may still be vague to you though, after all virtually every application process data.
Is the punch really for you ? If the trainer was succesful you have some idea. Let us conclude this training module by a simple exercice.
You are a software architect, and you have some use case to solve (pick one, whatever it is). You have an idea of the type of architecture and technologies that would do the job:
- an entreprise bus, ERPs, mediation services
- a bunch of containerized micro-services in Kubernetes
- An hadoop big data stack
- some specific NoSql COTS : Elasticsearch, Cassandra, Clickhouse, Postgresql, InfluxDb, ..
- stream processing engines such as Flink, Spark, Storm
- a Kafka (or similar queuing) backbone
- Dataiku or similar AI-ready frameworks and tools
- Python apps deployed on GPUs
- Spark, Databrick suite and services
- Serverless frameworks
- ACID database transactions
For each would you say the Punch is (i) not relevant at all, (ii) to some extent relevant or (iii) very relevant ?
Our team members view (so may be not yours):
- (iii) 5, 6, 7, 9
- (ii) 1, 2, 3, 4, 8
- (i) 10, 11