When it comes to enterprise requirements around web projects, there is always a high demand for a scalable, and secure platform within which you can provide your software solution. The classical infrastructure solutions consisting of products like Apache, Nginx, Memcache, Redis, Gearman, ActiveMQ. Using these tools is, of course, a possible approach but is always coming along with lots of configuration and a decrease in flexibility. Imagine if there would be a high flexible, scalable, performing and easy to use platform within you can install your PHP based web applications. The appserver.io platform is delivering exactly this. See how fast and easy it is to install but also understand how you can get Neos running and be inspired by possible use cases for the future.

1. Enterprise Infrastucture
the multithreading thing

2. Stefan Willkommer
Co-Founder and CTO
@
sw
illkom
m
er

3. Tiger
Sissi
me ;)
Annette

5. What is
ENTERPRISE

6. more servers more transactionmore users

8. What is the
PROBLEM

9. >1.000.000
huge imports
records

10. SERVER
multiple
setup

11. TRAFFIC
volatile
peaks

12. CACHE
increasing
dilemma

15. scale
OUT

17. What’s
WRONG?

18. think outside the
BOX

19. Java
Ruby
Python
JS

20. and now?

21. IMAGINE

22. POSSIBILITIES

23. EVENTLOOPS

24. FORKS

25. THREADS

26. What is a
THREAD

27. Process-Model
without
THREADS

28. Process-Model
with
THREADS

29. What do we
NEED

30. PHP 5.3+

31. compiled thread-safe
--enable-maintainer-zts

32. PECL extension
pthreads

33. What can we do
NOW

34. my first
THREAD

35. my first
THREAD

36. What is a
STACKABLE

37. enabling sharing and synchronizing
Data over THREADS

38. tasks which can be processed
by a WORKER

39. What can be
SHARED

40. everything which is
SERIALIZABLE

41. sharing Data
with a
Stackable

42. sharing Data
with a
Stackable

43. sharing Data
with a
Stackable

44. What is a
WORKER

45. allows stacking of
DATA

46. like a
QUEUE

47. SYNCHRONISATION
and
CONCURRENCY
HANDLING

48. waiting for Threads with
join()

49. enables waiting for one or more
THREADS

50. makes sure that result is available in
THREAD

51. synchronizing Threads with
synchronized()

52. sharing
Resources

53. What to do with all these
POSSIBILITIES

54. sure thing, building an
INFRASTRUCTURE

57. Runtime
ApplicationServer
HTTPRemoteMethodMessage
Container 1
MQ Server PC Server WebServer
Servlet
Engine
Socket
0.0.0.0:8587
Socket
0.0.0.0:8585
Socket
0.0.0.0:8586
MBeans
SBeans
TimerService
Container 2
……

58. Let’s get
STARTED

59. running
NEOS
on appserver.io

66. What’s
NEXT?

67. Version
1.1

68. Thank You
Questions?